The contact page is the last step before someone becomes a lead, and it is routinely the least considered page on the site. Small failures here cost more than anything you fix elsewhere.
A contact page should offer more than one way to get in touch, keep the form short, set expectations about response time, and confirm clearly when a message is sent. Every additional form field reduces completions, so ask only for what you need to respond usefully.
Offer more than one route
People differ. Some will only call, some will never call, some want email so there is a record.
- Phone number, tappable on mobile.
- Email address, or a form.
- Physical address if you have premises, with a map.
- Opening hours, so people know when to expect a reply.
- WhatsApp or messaging if your audience uses it.
A contact page offering only a form loses everyone who wanted to call, and you never find out they existed.
Form length
| Fields | Effect |
|---|---|
| Name, email, message | Highest completion, sometimes underqualified |
| Plus phone | Small drop, considerably easier follow-up |
| Plus company and service | Moderate drop, better qualification |
| Plus budget | Noticeable drop, filters out mismatches |
| Eight or more | Substantial drop, rarely worth it |
There is a genuine trade-off between volume and qualification. What is rarely worth it is asking for information you will not use, which costs completions for nothing.
Set expectations
Say when you will reply. We respond within one working day is a small sentence that measurably reduces abandonment, because it removes the fear of shouting into a void.
Then meet it. A stated response time you miss is worse than none at all.
The failures that cost real money
- The form silently fails. The most expensive bug on the internet. Test it monthly and log every submission server-side so a mail failure cannot lose a lead.
- No confirmation after sending. People submit again, or assume it failed and go elsewhere.
- Replies go to spam. Set up SPF, DKIM and DMARC so your notifications arrive.
- Required fields that should not be. Making a website URL mandatory blocks anyone without one.
- Validation that rejects valid input, such as phone numbers with spaces or international formats.
- No visible phone number, for a business whose customers prefer to call.
After submission
Send them somewhere that confirms what happened and what comes next. Thanks, we have your enquiry and will reply within one working day is enough. Vagueness at this moment reads as a system that may not have worked.
A thank-you page also gives you a conversion event to track, which a message replacing the form in place does not.
Frequently asked questions
How many fields should a contact form have?
As few as let you respond usefully. Name, email and message is the baseline; adding phone and service is usually worth the small drop in completions. Every field beyond that costs submissions, so each one needs to earn its place.
Should I show my phone number?
If any of your customers prefer to call, yes, and make it tappable on mobile. Hiding it to force form submissions loses the people who were never going to fill in a form, and you never learn they existed.
Why am I not getting form submissions?
Test the form yourself first. Silent failures are extremely common: broken mail configuration, missing SPF records, or notifications landing in spam. Log submissions server-side so you can tell the difference between no enquiries and lost ones.
Should the contact form be on the contact page only?
No. Put a short form or a clear call to action on service pages too, at the point where someone has just decided. Making people navigate to a separate page adds a step that loses some of them.
What should happen after someone submits?
Show a clear confirmation stating that the message was received and when they will hear back, ideally on a separate thank-you page so you can track it as a conversion. Ambiguity here makes people resubmit or leave.