Your intake form is not admin, it is the funnel
Almost every business treats its enquiry form as an administrative detail. Somebody built it once, in an afternoon, using whatever fields seemed sensible, and nobody has looked at it since. Meanwhile it is doing more work than any other object the business owns. It decides who gets in touch, what you know when they do, how fast you can respond, and whether the enquiry reaches the right person. Change one field and all four change with it.
Every field is a toll gate
A form is not a neutral container for information. It is a request for effort, made to somebody who has not yet decided to work with you, usually on a phone, usually while doing something else.
Each additional field costs you some proportion of the people who would otherwise have got in touch. That cost is invisible, because the people who abandon leave no trace, and there is no line in any report labelled enquiries that did not happen. Meanwhile every field you removed is a question somebody has to ask later, which costs a round trip and a day.
So the real design problem is not what you want to know. It is which questions earn their place at the moment of first contact, and which can wait until somebody is already talking to you.
The three jobs a form actually does
Forms get designed as though they have one job, which is collecting information. They have three, and the other two are worth more.
- Capture. Getting a way to contact the person. This is the only part that is genuinely essential, and it is one field plus a name.
- Qualify. Establishing whether this is work you do and roughly what shape it is. Done well, this saves both sides a wasted call. Done badly, it filters out good customers who did not know how to answer.
- Route. Getting the enquiry to the right person or place immediately. This is the job most forms do not do at all, and it is the one that decides response time in any business with more than one person or more than one location.
What to ask now, and what to ask next
The split below holds up across almost every industry we build for. The specifics change, the principle does not: ask what changes the next hour, defer everything else.
- One free text box beats five dropdowns. People describe their own problem better than your categories do, and a system reading that text can route on it. Dropdowns are for you, prose is for them.
- Required fields should be genuinely required. Every unnecessary asterisk is a small abandonment risk for no gain.
- Never ask twice. A form that asks for something a returning customer already gave you is telling them you did not keep it.
| Question | On the first form | Why |
|---|---|---|
| Name and one contact method | Yes | Without it there is no enquiry. One method, chosen by them, not both. |
| What they want, in their own words | Yes | One free text box. It is the most useful field on any form and the first one people cut. |
| Where the work is | Yes, if you have service areas | It changes who it routes to and whether you can help at all. |
| When they need it | Usually | Urgency changes the order you call people back in, which is the highest value thing you can know. |
| Which service they think they need | Sometimes | Useful for routing, risky as a required field: customers often pick wrong and some will abandon rather than guess. |
| Budget | No | Almost nobody answers it honestly on a form, and asking it early reads as a filter rather than a question. |
| How they heard about you | No | Ask it after the enquiry is captured, or in the confirmation. Useful to you, worth nothing to them. |
| Address, postcode, full details | No | Collect at booking, when they have already decided and the effort feels justified. |
| Anything you could look up | No | If your system can derive it, do not ask a customer for it. |
The order is not neutral either
Sequence changes completion rates more than length does, which is why a long form that starts easily often outperforms a short one that starts by asking for a phone number.
- Start with the question they came to answer. What do you need, in your words. It is the one field where somebody is motivated, and starting there is the difference between a form and an interrogation.
- Then the thing that scopes it. Where, or when, or which. One question, not four.
- Then contact details, last. By this point they have invested effort, and the well-documented effect is that people finish what they have started. Asking first inverts that.
- Then submit, and mean it. No second page of optional questions after the button. That is where a good completion rate goes to die.
The form is only half of it
Here is the part that makes the whole argument worth taking seriously. A perfectly designed form attached to a slow response is worth less than a mediocre form attached to a fast one.
What happens in the sixty seconds after somebody presses submit determines most of the outcome. Does anything acknowledge them, does it say what happens next and when, does the enquiry reach the person who can act on it, and does anything happen if that person does not act.
- Acknowledge instantly, with substance. Not "thanks, we got your message" but what happens next and roughly when. This is the cheapest trust you will ever buy.
- Route by content, not by inbox. A shared inbox is where enquiries go to wait for whoever opens it first, which in most businesses is nobody until the evening.
- Escalate on silence. If nothing has happened in an hour, something should notice. The absence of this rule is why enquiries sit unworked in a system somebody paid for.
- Answer at the hour they wrote. Most web forms are submitted in the evening. A business that only answers between nine and five is answering a meaningful share of its enquiries the following day, which is after the decision was made.
What we see go wrong most
In roughly descending order of how much it costs and how easy it is to fix.
- The form asks eleven things. Usually because every department added one question over five years and nobody ever removed any.
- There is no free text box. The customer had something specific to say and the form would not let them say it, so they either abandoned or picked the nearest wrong option.
- The confirmation says nothing. A generic thank you page tells somebody who was already unsure that they may have shouted into a void.
- Nobody tested it on a phone. Most submissions are from phones. Test yours on one, in the evening, with one thumb.
- It goes to an inbox nobody owns. Ask who is responsible for enquiries arriving on a Saturday. If the answer takes more than a second, that is the finding.
- It is the only door. Some people will never fill in a form and would happily text. A form is a channel, not a strategy.
- Nothing is measured. How many people started it and did not finish is knowable and almost nobody knows it. That single number tells you whether the form is the problem or the traffic is.
Where to start if you only change one thing
Cut the form to the smallest set of questions that lets somebody do useful work in the next hour, put the free text box first, and make the confirmation say what happens next.
That is an afternoon of work and it does not require a system, a rebuild or a vendor. It is also the prerequisite for everything else: automating a response is straightforward, and automating a response to a form nobody finishes is not.
Once the form is right, the response side is the next piece, and the argument for why the speed matters as much as the content is in the speed-to-lead guide. The seven day sequence for what happens after that first reply is in the seven day enquiry plan. And if you want to know what your current page does to a first-time visitor before they ever reach the form, the website test scores it.