How Do You Design a Contact Page That Gets Fewer Useless Messages?

Why does your contact page attract the wrong enquiries?

Because it asks for contact rather than for context. A page whose only message is get in touch will be used by everyone who wants something from you, including people you cannot help. The page is doing exactly what it asked for, and what it asked for was undifferentiated attention.

I hear the complaint constantly from founders and solo practitioners. The inbox fills with enquiries that were never going to become work, each one costing a reply, and the good ones get slower responses because of it.

The fix is not a longer form. It is a page that tells people plainly who it is for, and asks the two or three questions that separate a real enquiry from a hopeful one.

What is a contact page actually supposed to do?

Route people correctly. That is the whole job. Some visitors should reach you, some should reach your documentation or your pricing page, and some should leave having learned that you are not the right fit. A page that only knows how to do the first of those is not filtering anything.

Thinking in terms of routing rather than conversion changes what you put on it. You stop measuring the page by submissions and start measuring it by the proportion of submissions worth answering. Those two numbers usually move in opposite directions, and the second one is the one that determines your week.

It also means the page needs somewhere for the wrong person to go. If your only exit is the form, people who should not use it will use it anyway, because you gave them no alternative and they still have a question. Your pricing page, your documentation, and a booking link such as Calendly for the people who genuinely should book are all exits.

Should you filter before the form or inside it?

Before it, mostly. A short paragraph above the form saying who you work with and what a typical engagement looks like removes more bad-fit enquiries than any field arrangement, because it lets people disqualify themselves before they have invested any effort in typing.

Filtering inside the form arrives too late in the process. Someone who has already written three sentences about their project is committed, and a dropdown that quietly signals they do not qualify will mostly be answered optimistically rather than honestly. People round themselves up when they have started.

The most effective single sentence I have seen on these pages is a plain statement of scope, including price shape. Saying that most engagements are fixed fee in a particular range is not rude. It is the most respectful thing you can do for someone whose budget is a tenth of that, and it is the same logic behind a services page that filters out bad-fit leads.

Which fields actually reduce bad-fit enquiries?

The ones that require a decision rather than a fact. Name and email are facts and filter nothing. What are you trying to achieve, what have you already tried, and when do you need this by are decisions, and a person who cannot answer them is usually not ready to buy anything.

Timeline is the most underrated of those. Someone with a real deadline answers immediately and specifically. Someone exploring writes something vague, and that vagueness is genuinely useful information rather than a failure of the form. You are not trying to force a good answer, you are trying to see which kind you get.

I would cap the whole thing at about five fields. Beyond that you are not filtering, you are taxing, and the people most likely to abandon a long form are busy senior people with real budgets. The goal is a form that is slightly harder to complete thoughtlessly and no harder to complete honestly.

How much instruction should you put on a form?

Enough to make each field unambiguous and no more. The W3C's guidance on WCAG success criterion 3.3.2, Labels or Instructions, is a Level A requirement stating that labels or instructions are provided when content requires user input, with the intent that users know what input data is expected.

The W3C is also explicit that this is not a licence to explain everything. Its guidance says the intent is not to clutter the page with unnecessary information but to provide important cues and instructions, and that too much information or instruction can be just as harmful as too little. That is a useful sentence to quote at anyone who wants helper text under every field.

One more detail from the same guidance is worth knowing, because it corrects a common misreading. The W3C says the use of requires in the criterion's wording does not mean it applies only to required form fields, and that the criterion applies to all form fields, whether they are required or optional. Optional fields need clear labels too, and this is part of why visible labels beat placeholder text.

What should the page say about what happens next?

Your actual response behaviour, stated plainly. If you reply within two working days, say so. If you only reply to enquiries that match your scope, say that too. Setting the expectation on the page prevents the follow-up email three days later asking whether you received anything.

This is the part almost every contact page skips, and it does more for the quality of your inbox than any field. An enquiry sent by someone who knows what to expect is calmer, more detailed, and far less likely to be duplicated across three channels because they were not sure it had gone through.

Be honest rather than generous. Promising a same-day reply you cannot hold turns a good first impression into a broken one within a day. I have written about why I stopped replying to every enquiry immediately, and the page should describe whatever you actually do rather than the most impressive version of it.

How should the form behave when something goes wrong?

It should tell the person how to fix it. The W3C's guidance on success criterion 3.3.3, Error Suggestion, is a Level AA requirement stating that if an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless that would jeopardise the security or purpose of the content.

In practice that means naming the field and the problem rather than colouring a border red. An error message that says which field failed and what an acceptable value looks like resolves the issue in one attempt. A generic failure notice at the top of the form sends people hunting, and a meaningful number of them simply leave instead.

The same thinking applies to success. Whether the form is built in Webflow, HubSpot or anything else, one that clears itself with no confirmation is indistinguishable from one that silently failed, and the person will either give up or send the same enquiry again through another channel. Neither outcome is one you want.

What should you never do to filter enquiries?

Never make the form deliberately annoying, never hide your contact route behind a maze, and never use accessibility barriers as a filter. A form that is hard to complete filters for persistence, not for fit, and persistence is uncorrelated with whether someone is a good client.

Hiding the email address is the version of this I see most often. It reliably stops the wrong people and it also stops a percentage of the right ones, including anyone whose first instinct is to forward your details to a colleague. Make the route obvious and make the qualification honest instead.

Using a challenge, a required phone number, or an unlabelled field to discourage enquiries is worse still, because it pushes the cost onto exactly the people least able to absorb it. If you want fewer enquiries, say who you are for. Do not build friction and call it selectivity.

What should you do next?

Read your own contact page as somebody you cannot help. Does it tell them, within the first two sentences, that this is not for them? If it does not, that is one paragraph of writing and it will do more than any redesign you were considering.

Then look at your last twenty enquiries and work out which single question would have told you the answer fastest. It is usually budget shape, timeline, or what they have already tried. Add that one question, remove any field that has never changed what you did next, and leave the rest alone.

Finally, write down what actually happens after somebody submits, and put it on the page. If you want a second opinion on a contact page that is producing the wrong inbox, reach out and send me the link.