Several Channels
Form, phone and email — some enquiries need a conversation now.
Most contact pages offer one form, no phone number and no indication of when anyone will reply. Contact page design should do the opposite: give people the channel that suits their situation, say how long a response takes, and ask for only what is needed to give a useful one.
Different enquiries want different channels, and a single form serves only one of them.
Form, phone and email — some enquiries need a conversation now.
Which improves completion and reduces chasing.
Enough to reply usefully, not a qualification interview.
Enquiries reaching the right person without a manual step.
What happens next, not "thank you for your submission".
A contact page is reached by people who have already decided to get in touch. Every failure here loses someone who was ready, which makes it the most expensive page on most sites to get wrong.
Delivery verification is the check nobody runs until something goes wrong. Forms fail silently — a changed address, an expired integration, a filter — and the symptom is a quiet period that looks like a demand problem. Submitting a real test enquiry periodically costs nothing.
Four kinds of enquiry, wanting different things from the page.
Discuss Your Contact Page →Wants a phone number, now. A form is the wrong answer.
Happy with a form, wants to know when they will hear back.
Needs support, not sales, and should not be routed to sales.
Wants an address, opening hours and how to get there.
Channels, the form, and what happens after it is sent.
For enquiry quality specifically, see lead generation website design. Enquiry quality and routing are covered by lead generation website design; delivery into your systems is CRM integration.
Start from who contacts you and what each of them needs.
Who gets in touch and about what.
What to offer, and for which situations.
Short, accessible, with clear errors.
Response time, stated on the page.
To the right team, with a useful confirmation.
How this page should work depends on who contacts the business and what has to be known before a useful reply is possible.
Where qualifying questions genuinely save time. The trade is real: every additional field reduces completions, so each one has to earn its place by preventing more wasted effort than it costs in lost enquiries.
Where volume is low and each contact matters. The form should ask for the minimum needed to reply — usually a name, a way to respond and a message — and everything else belongs in the conversation.
Where the useful action is an appointment rather than a message. This is a scheduling flow rather than a contact form, and treating it as one avoids a two-step process where one would do.
Where a meaningful share of the audience will not use a form. Making the number prominent and tappable matters more than any form improvement, and hiding it behind a form costs enquiries.
Where sales, support and recruitment arrive through the same form and get routed manually. A single routing question at the top usually serves better than several separate pages.
It is usually done to control support volume and it filters out the most motivated people.
Anyone with an urgent problem, anyone who wants to assess you by voice before committing, and anyone who has been let down by a form before.
These are frequently the highest-intent enquiries. Someone prepared to phone is further along than someone filling a form to be contacted eventually.
The support-volume concern is real, and there are better answers than concealment — hours, a routed number, or a callback option that at least acknowledges the preference.
It increases completion, because uncertainty about whether anyone will reply is a reason not to bother.
It reduces chasing messages, because someone told to expect a reply within a working day does not follow up on the same afternoon.
And it improves contact rates afterwards, because a call that was announced is a call people answer. One line above the button changes all three.
Form length and completion rate move against each other. That does not make short forms automatically correct — a field that prevents an unqualified enquiry can be worth the completions it costs. What is wrong is adding fields without deciding whether they earn it.
The test for each field is whether the reply would be materially worse without it. Company size, budget range and how they heard about you are frequently collected because they are useful to know rather than because they change the response. Those belong in the conversation, not in the barrier before it.
Fields that are genuinely necessary should be marked honestly. Marking optional fields as required to increase data capture converts some proportion of ready enquirers into people who abandon, and the data collected is worth less than the enquiries lost.
A form that submits with no confirmation leaves the sender unsure whether it worked. Some resend, some assume failure and go elsewhere, and neither is a good outcome for someone who had already decided to make contact.
The confirmation should say three things: the message was received, when a reply can be expected, and what to do if it is urgent. Response expectation is the part most often missing and the easiest to supply, and it prevents the follow-up enquiry that arrives two days later asking whether the first one arrived.
The same applies to failure. A submission that errors should preserve everything typed and say what went wrong specifically. Clearing a completed form on a validation error is the single most reliable way to lose someone at the last step.
The contact page rarely persuades anyone. By the time someone reaches it the decision is made, which means its only job is to not get in the way — and its performance is largely determined by pages upstream that did the persuading.
This matters for diagnosis. A contact page with few submissions may be working perfectly while the service pages ahead of it fail to convince anyone to arrive. Improving the form will not fix that, and it is worth checking where visitors actually stop before redesigning the last step.
It also means the page should be reachable from wherever the decision gets made. Service pages under web design and elsewhere should route to it directly rather than relying on a navigation link, since a visitor who has just been persuaded should not have to look for the next step.







Contact page design covers the channels offered, the form itself, the response expectation stated on the page, routing behind it, and a confirmation that says what happens next.
Usually. Hiding it excludes urgent and high-intent enquiries — people prepared to phone are further along than people filling a form. Control volume with hours or routing rather than concealment.
Enough to reply usefully. Name, contact method and what they need is often sufficient; qualification detail belongs on a lead generation page where it is doing routing work.
Yes. It increases completion, reduces chasing messages and improves contact rates, because a call that was announced gets answered. It costs one line.
What happens next, when, and from whom — plus what to do if nothing arrives. "Thank you for your submission" tells the sender nothing they can act on.
As few as allow a useful reply — usually a name, a way to respond, and space to describe the need. Each additional field costs some completions, so it has to save more effort than it loses. Fields collected because the information is nice to have belong in the follow-up conversation.
If the business will answer it, yes. A meaningful share of people will not use a form, particularly for urgent or complex enquiries, and hiding the number behind a form loses them. If nobody reliably answers, publishing it does more harm than omitting it.
Only if visitors come to you. For a business that operates remotely, a map occupies space and answers nothing anyone asked. Where clients do visit, the practical details — parking, access, which entrance — are more useful than the map itself.
Prefer methods that are invisible to genuine users over challenges that make everyone prove themselves. Aggressive verification blocks real enquirers as well as bots, particularly on mobile and for people using assistive technology, and the enquiries lost are usually worth more than the spam prevented.
It depends on whether that answer would change your response. For businesses receiving more enquiries than they can serve, it qualifies usefully. For businesses that would reply to almost anyone, it costs completions and gives nothing back — and it is a question many people decline to answer before a conversation has started.
Still deciding if contact page design is right for you?
Talk to UsRemoving the phone number from a contact page reliably reduces support calls. It is a real problem, the solution works, and the volume drops immediately.
What also drops, invisibly, is the set of enquiries from people who were ready to talk. Someone prepared to pick up a phone is further along than someone filling in a form to be contacted at an unspecified point.
They do not send a message explaining that they wanted to call. They go to a competitor whose number was on the page, and the reduction in support volume is recorded as a success.
Send us your contact page. We will tell you which enquiries it serves, which it turns away, and what it fails to say.
