Skip to content
Interface language: English
Design / Signal

B2B contact forms: from purposeful fields to real delivery

Design a useful B2B contact form, validate it on client and server, and test the real journey from submission to the agreed inbox.

Article language: English

A woman beside a cup and folded red fabric by the water.
In this article

A contact form should open a conversation, not make people pass a test before they can ask a question. Keep the fields needed for a useful response, write clear labels and check errors. Then go one step further: confirm that the message actually reaches someone who will handle it. A green “sent” message looks pleasant, but it will not answer the phone or find a lost email.

A short form can be effective, and length alone does not make a form professional. The purpose of each field matters. Someone who is only exploring a possible collaboration should not have to prepare a complete order specification just to ask a first question. Use these steps to design the contact journey and check it from the first click through to the inbox or another agreed system.

Define what should begin after submission

Record one main function: an initial project enquiry, a request for a conversation or delivery of a finished brief. Those are different stages. If you try to combine them in one long form, add a simple choice of context or separate the routes. Someone without a document should still be able to describe their need clearly.

Decide who will handle enquiries, where they will arrive and who will take over when that person is away. A field collecting an urgent deadline serves no purpose without a procedure for assessing it. State a response time only after agreeing how enquiries will actually be handled. Do not use it as a decorative promise beside a button.

Carry these decisions into the premium website brief (in Polish). If contact comes at the end of a B2B service page (in Polish), the offer should explain what happens next. The form should not suddenly require a different kind of collaboration from the one described a few paragraphs earlier.

Every field needs a reason

List proposed fields and record who will use each answer before the first conversation. A name, contact address and description of the situation may be enough for many enquiries. Company name, phone number, budget or deadline should follow from the process. Do not require everything at once simply to make the form look serious.

W3C recommends asking for information needed for the process. Distinguish required fields from optional ones and mark the difference consistently. If a phone number is needed only when someone chooses a phone conversation, it can appear in that context. Conditional fields still need keyboard testing.

Consider attachments. They make it easier to send prepared material, but require size limits, file-type handling and someone responsible for receiving them. If you add one, map the states of individual attachments and file correction, so a selected file is not mistaken for a successfully uploaded one. For a first contact, a description and a secure way to pass documents later may often be enough. Do not encourage people to provide confidential material unless it is needed and a handling procedure is in place. For more detail, see the guide to attachment states and corrections (in Polish).

Write labels and instructions before styling

A label should stay understandable after someone starts typing. Text inside an empty field does not replace a persistent name. Help text should explain the required format or scope. For example: “Describe what you want to change and where you are in the process.” Do not ask customers to use the language of a technical specification.

A required-field indicator cannot depend on colour alone. Agree on useful examples without using real data. For a budget, do not offer ranges the company does not use in conversation. “I do not know yet” may be more honest than forcing a random choice if a missing amount does not prevent diagnosis.

Write button text that matches the action. “Send enquiry” is clearer than a general “Next” if there is no next form step. You also need text for success and error states. These belong to writing a service page (in Polish), not just the final implementation edit.

Validate in the browser and on the server

Validation checks whether data has the required format and scope. A browser can quickly flag a missing address or text that exceeds a length limit. MDN clearly distinguishes that assistance from server-side checking. Client-side checks can be bypassed, so the server-side part, called the backend, must also assess received data.

Do not treat valid email syntax as proof that an inbox exists or that the sender’s identity is verified. Do not impose arbitrary restrictions on surnames or company names. Real data can be long and contain spaces and characters outside the basic alphabet. Tests should cover it, not just short English examples.

Choose abuse protections for the real risk and operating process. Limits and duplicate rejection should not create an unexplained dead end for an ordinary user. If a request is blocked, the message and available alternative must match what the site can actually offer.

Aeneia conceptual photography

Design errors that help finish the task

An error should identify the field and the correction needed. W3C describes clear form notifications, including information near the control and a summary of problems. “Invalid data” without a location forces the reader to inspect the whole form again. Preserve the brand voice in interface messages, but first check that the person understands the cause and next action after an error. This is discussed in the article on brand voice in interface messages (in Polish).

After an unsuccessful attempt, retain the entered content where the chosen design and handling rules allow it. Do not make someone rewrite a project description because of a typo in an address. In a longer form, allow movement from the error summary to the relevant field. The change should also be understandable to assistive technology.

Check errors on a phone, at increased zoom and with a keyboard alone. An on-screen keyboard must not cover the only information explaining the correction. General acceptance principles are covered in business website accessibility. One successful mouse test does not confirm every route. For related guidance, see the guide to business website accessibility (in Polish).

Connect the success message to a confirmed operation

The frontend, the visible site interface, displays fields and responses. The backend receives the request and starts the agreed process. A “sent” animation after two seconds does not prove any recipient exists. If the site merely opens an email application, name that action directly and do not present it as a message sent by the website.

With fetch(), check the response, not just the fact that the call ended. MDN explains that an HTTP error response does not necessarily reject the `fetch()` promise. The status and agreed response content must be assessed. This matters when the interface treats data acceptance differently from temporary service unavailability.

Distinguish server acceptance from delivery to an inbox. If the system confirms that a request was placed in a queue, the message should say it was received for processing. Delivery needs separate observation. Likewise, a button saying “Sending” should return to a usable state after an error rather than remaining disabled forever.

Test the entire journey on the actual domain

Send an identifiable test enquiry and check where it arrives. Compare every field, Polish characters, a long description and the message subject. Confirm that the responsible person can reply to the correct address. A screenshot of a green message or a developer-console entry alone is not enough.

Then test failure scenarios: a missing required field, invalid format, unavailable receiving service and interrupted connection. Check retrying and a rapid double-click. Establish whether a repeated attempt can create two enquiries and how support will recognise them. Do not solve everything by disabling the button indefinitely.

Post-publication acceptance matters especially after a website migration (in Polish). A different domain or configuration can change the request’s route. Check both direct entry to contact and the path from the offer. Review movement and confirmations alongside microinteractions (in Polish), but do not let them replace the actual result.

In the test record, use an easily recognised identifier, date and expected recipient. The person checking the inbox can then connect the message to a specific attempt. After confirmation, remove unnecessary test material according to the agreed procedure. Do not keep full contents of real enquiries in public screenshots or reports merely to prove that the form works.

The message after submission is part of the same process. Design a thank-you page and next step, then compare its promise with the server’s actual confirmation. “Thank you” should not pretend to prove receipt of a case if the system is still processing it. You can also consult the article on thank-you pages and next steps (in Polish).

Hand over the contact process for maintenance, not just launch

Record the destination, support owner, failure-checking method and procedure for changing the recipient address. Transfer technical information and access details through the proper channel, outside public documentation. Establish who confirms operation after changing the email provider or editing the form.

If no backend is ready, choose an honest working alternative, such as an explicit email link or a real calendar. Do not leave a simulation pretending to accept a message. The client should know which option is live and what its limits are before directing visitors to the page.

  • Every field has a justified purpose and a clear label.
  • Validation covers the client and server.
  • An error allows correction and another attempt.
  • Confirmation matches the operation’s actual state.
  • A test reached the agreed handling destination.
  • Responsibility after publication is recorded.

Finally, check how someone responds to the test enquiry. Does the reply reach the sender, have an understandable subject and identify the matter without requiring another explanation? Even a form that passes technical checks needs someone to handle enquiries well. Not every stage needs automation, but the responsible person should be able to find the enquiry, take it over and clearly communicate the next step.

Include the results in the website handover checklist. Want to make B2B enquiries easier to manage? Explore Aeneia Design. The topic is explored in the website acceptance checklist article (in Polish).

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear