Contact Page Design

Contact Page Design With a Real Choice and a Stated Response Time

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.

Why Choose Us

We Give People a Choice of Route

Different enquiries want different channels, and a single form serves only one of them.

Several Channels

Form, phone and email — some enquiries need a conversation now.

Response Time Stated

Which improves completion and reduces chasing.

Short Form

Enough to reply usefully, not a qualification interview.

Routing Behind It

Enquiries reaching the right person without a manual step.

Real Confirmation

What happens next, not "thank you for your submission".

What We Check

Where contact pages lose enquiries

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.

Field necessityWhether each field is needed now or could be asked later
Validation behaviourWhether errors appear helpfully or only after submission
Input types on mobileWhether the right keyboard appears for phone, email and number fields
Entry preservationWhether a failed submission keeps what was typed
Success confirmationWhether the sender knows the message actually went
Response expectationWhether the page says when someone will reply
Alternative channelsWhether phone or email is available for people who will not use a form
Required-field honestyWhether anything marked required genuinely is
Spam handlingWhether the protection blocks real people as well as bots
AccessibilityLabel association, focus order, error announcement to screen readers
Delivery verificationWhether submissions actually arrive, tested end to end
Qualification balanceWhether qualifying questions cost more enquiries than they save

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.

Contact Design, Explained

Who Is Contacting You?

Four kinds of enquiry, wanting different things from the page.

Discuss Your Contact Page →
  1. 1

    The Urgent One

    Wants a phone number, now. A form is the wrong answer.

  2. 2

    The Researcher

    Happy with a form, wants to know when they will hear back.

  3. 3

    The Existing Customer

    Needs support, not sales, and should not be routed to sales.

  4. 4

    The Visitor

    Wants an address, opening hours and how to get there.

Our Process

How We Design Contact Pages

Start from who contacts you and what each of them needs.

  1. Map the Enquiries

    Who gets in touch and about what.

  2. Choose the Channels

    What to offer, and for which situations.

  3. Design the Form

    Short, accessible, with clear errors.

  4. Set Expectations

    Response time, stated on the page.

  5. Route and Confirm

    To the right team, with a useful confirmation.

Who This Is For

What the contact page has to accommodate

How this page should work depends on who contacts the business and what has to be known before a useful reply is possible.

Businesses handling high enquiry volume

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.

Businesses where any enquiry is worth having

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.

Services with a booking or scheduling step

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.

Businesses whose buyers prefer phone

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.

Businesses with multiple contact reasons

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.

Trust

Why Hiding the Phone Number Costs Enquiries

It is usually done to control support volume and it filters out the most motivated people.

Who does a form-only page exclude?

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.

What does a stated response time do?

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.

Every field is a decision to lose some people

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.

What happens after submission is part of the design

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.

Where the contact page sits in the journey

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.

Nekchat messaging app UI on iPad
VPN app UI on iPhone
NextSpace workspace UI on iPad
Mobile wallet app UI on iPhone
TravelGo booking UI on iPad
Plate restaurant app UI on iPhone
Triply travel planner UI on iPad
FAQ

Questions, answered.

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.

Still deciding if contact page design is right for you?

Talk to Us

The Ones Who Would Have Phoned

Removing 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.

Free Contact Page Review

Find Out What Your Contact Page Is Costing

Send us your contact page. We will tell you which enquiries it serves, which it turns away, and what it fails to say.

Claim Your Free Marketing Audit

Enhance Your Brand Potential At No Cost!

  • Expect a response within 24 hours
  • NDA available upon request
  • Dedicated product specialists
Project Budget

We reply within 24 hours. Your details are never shared or sold.