Most contact pages fail because they ask for more than the visitor is ready to give. Someone who is curious about working with you gets a ten field form, no phone number, and no idea when anyone will reply. So they close the tab. The page did not convert because it never earned the click.
This is the page we find neglected most often. Teams pour weeks into a homepage and then throw a default form onto a blank page at the end of the funnel. It is the last thing a serious prospect touches before they become a lead, and it is usually the least considered page on the site.
The fix is not clever. It is mostly removing things and being specific about what happens next.
It needs the ways to reach you, a short form, and a clear statement of what happens after someone gets in touch. Nielsen Norman Group research on contact pages, published by Anna Kaley in August 2019, found that users still expect traditional contact details and get frustrated when a company hides them.
That study tested 20 business professionals and the complaints were blunt. One participant, looking at a page that offered no actual contact methods, said "This page called Contact Us and then the content is just more paragraphs, they don't seem to be offering methods of contact". That is a design failure, not a user failure.
So the baseline is unglamorous. Phone number, email address, physical address if you have one, hours, and a form. Nielsen Norman Group also recommends putting the contact link in both the main navigation and the footer, because that is where people instinctively look first.
Everything else on the page is optional. Get the baseline right before you get creative.
Between three and five. That is the range Nielsen Norman Group recommends, and it matches what we see in practice. Name, email, and a message box will carry almost any enquiry. Every field past that trades a real percentage of submissions for information you could have asked for in your reply.
The evidence on field count from adjacent research is stark. Baymard Institute measured ecommerce checkouts and found the average site ran 12.8 form fields in late 2019, down from 14.88 in 2016, while sites can complete a guest checkout in as few as 6 to 8 fields. That is checkout, not contact, and the comparison is worth making carefully. If a buyer with a credit card in hand struggles past a dozen fields, a stranger with a vague question certainly will.
Baymard also reports that 26% of users abandoned a purchase during checkout solely because the flow was too long or too complex. Again, that is buying behaviour rather than enquiry behaviour. But the direction of the effect is not in dispute, and enquiry forms have far less motivation behind them.
Our rule is simple. Ask for what you need to reply, nothing more. Budget, company size, and timeline are qualification questions, and qualification is what the first conversation is for. If you genuinely must qualify at the form, make those fields optional and say why you are asking. The mechanics of that trade off are covered further in our guide to form design and UX.
Yes, both, and prominently. Nielsen Norman Group is direct about this in guideline three of that study, recommending you never hide or remove your phone number. Hiding it costs you more than the calls you avoid, because it makes the business look evasive to the people evaluating you.
The quote from their research says it better than we can. A participant noted that "There are companies that don't even give you a phone number anymore. It makes them seem suspicious". Trust is the actual product on a contact page.
The same study recommends treating forms as a supplement rather than a replacement for direct contact, and warns against requiring account creation before someone can reach you. Both are worth checking on your own site today.
If you do not want inbound calls, our honest advice is to publish the number anyway and set expectations around it. A line saying you answer calls between certain hours does far less damage than no number at all.
State a specific window and then meet it. The Nielsen Norman Group guidance includes setting expectations for availability, wait times, and response windows on each channel. A vague promise to reply as soon as possible tells the visitor nothing and gives you nothing to be held to.
We put our own commitment on the page. We respond to new enquiries in under 48 hours. That number is useful precisely because it is checkable. It tells a founder deciding between three studios that they will hear from us before the week gets away from them.
Pick a window you can actually hit on your worst week, not your best one. A studio that promises two hours and takes three days has done more damage than one that promised three days.
Then say what the reply will contain. Telling someone you will come back with questions about scope sets a very different expectation than telling them you will send a quote, and the right one depends on how you actually work.
Write it like a person, and write it for the specific visitor who is about to fill in the form. A heading that says "Contact" is a label. A heading that says "Tell us about your project" is an instruction, and instructions get followed more often than labels do.
The most valuable sentence on most contact pages is the one that lowers the stakes. Something like "You do not need a finished brief. A rough idea is enough to start." A lot of people hesitate because they think they are not prepared enough to make contact, and one sentence removes that.
Cut anything that reads like legal boilerplate or corporate throat clearing. If a paragraph does not help someone reach you or decide to reach you, it is taking up space near your only conversion point on the page.
Keep the tone consistent with the rest of the site. A contact page that suddenly turns formal makes people wonder who they are actually going to talk to. The same consistency argument applies to your about page, which many visitors read immediately before this one.
Because an inaccessible form is a broken form for everyone, not just for people using assistive technology. The W3C Web Accessibility Initiative states that a label and a form control must be associated with each other, either implicitly or explicitly, with the for attribute on the label exactly matching the id of the control.
That association does something useful for every visitor. The W3C notes it gives browsers a larger clickable area, which matters enormously on a phone where a mistimed tap means a missed field.
The W3C tutorial also pushes back on a pattern we see constantly, which is using placeholder text instead of a visible label. It states that most users prefer or even need visible labels to understand the form, and highlights mobile users and people with low vision specifically. Placeholder only forms also lose the label the moment someone starts typing, so anyone who gets distracted has to clear the field to remember what it wanted.
Use real labels above the field, keep them visible, and make the error messages say what to do rather than what went wrong. None of this is expensive, and all of it lifts completion.
Show a real confirmation on a real page, not a small green flash that disappears. Tell them what you received, when they will hear back, and what to do if they need something sooner. The moments right after submission are when people decide whether the enquiry actually landed.
Send an immediate automatic acknowledgement by email too, and make it useful rather than a receipt. Restate the response window, include a direct email address in case they want to add something, and sign it from the team rather than from a no reply address.
Do not redirect to the homepage. It is a surprisingly common pattern and it quietly erases the confirmation, leaving people unsure whether anything happened at all.
One thing we always check on a build is whether form submissions are actually arriving. Spam filters, changed inboxes, and broken integrations kill more enquiries than bad design does, and nobody notices because a silent failure looks exactly like a quiet week.
A little, placed carefully. One or two short testimonials or a row of client logos near the form reassures someone at the exact moment they hesitate. A full case study section turns the page into another marketing page and pushes the form below the fold.
The most effective proof on a contact page is specific to the doubt the visitor has right now, which is usually about responsiveness or reliability rather than quality. A quote saying the team replied quickly and explained things clearly does more work here than one praising the visual design.
Keep it to a strip. The form is the point of the page, and everything competing for attention beside it needs to justify itself. We go deeper on choosing and placing this kind of evidence in our guide to social proof in web design.
Open your contact page right now and count the fields. If there are more than five, cut it back to name, email, and message. Then add your phone number and a specific response window. Those three changes take under an hour and will do more than any redesign.
After that, submit your own form from a phone on mobile data and see what happens. Most teams have never done this, and it is where the broken confirmations and missing notification emails turn up.
If you want another set of eyes on the page where your leads actually come from, we are happy to take a look and tell you what we would change. Come say hello at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.