Key Takeaways
- Write the reply first, then the form. The sentence you want to send back decides which fields exist. The rest is curiosity.
- Validation protects the reply path, not the spreadsheet. A reachable email address matters more than six tidy dropdowns nobody reads.
- A submission needs an owner before the form goes live. Without a destination and a named person, a form is an inbox filter with extra steps.
- Collect less than you want to. Completion rates and the GDPR's data minimisation rule push in the same direction, so use that as cover when someone asks for one more field.
Building the form is the easy part. Any builder gets you a name field, an email field and a message box in four minutes. What fails, reliably, is the gap between someone hitting submit and a human answering them, and field polish won't close it.
So this guide builds a customer enquiry form backwards: reply first, routing second, fields third. The worked example: a small services firm, 40 enquiries a month, two people answering them, losing about a third to vague one-liners.
Why online enquiry forms produce replies nobody sends
The standard failure is not an ugly form. It is a form whose answers cannot be acted on. Someone asks about "pricing for a project", you captured a name, an email and 11 words of free text, and answering costs a 20-minute discovery call the sender may not want.
The usual reaction makes it worse: add fields. Budget, timeline, company size, how did you hear about us. Completion drops, the enquiries that arrive are no easier to answer, and the extra answers sit in a spreadsheet nobody opens twice.
Buyers describe the same tension. In a 90-comment thread in r/Entrepreneur, someone asked for a form builder that is actually engaging rather than robotic, and the replies keep landing on conditional logic: show a short path by default, open the detailed questions only to people whose first answer earns them. That is a design instinct, not a tool feature.
The law pulls the same way. The GDPR's data minimisation principle limits collection to what is adequate, relevant and necessary for your stated purpose, and its storage limitation principle puts a clock on how long you keep it. A field you cannot justify is both a conversion cost and a liability, which makes "we do not need that yet" easier to win internally.
Step 1: Write the reply, then reverse-engineer the fields
Open a blank document and write the response a qualified enquiry should receive. For the services firm:
Thanks for getting in touch about the brand refresh. Projects in that scope usually run 8 to 12 weeks and start in the 15k range. I have time Thursday afternoon or Monday morning for a 20-minute call. Here is my calendar.
Now mark every word that depends on something only the sender knows. Scope. Rough budget band. Preferred start window. Which of two colleagues answers, based on service line.
Four pieces of information, plus a name and a contact route. Six fields, and you guessed at none of them.
That is the whole method, and almost nobody does it: form building starts from the builder's field palette instead of the answer the sender wants.
Do a second pass on the enquiry you want to decline. That one needs a field signalling out-of-scope fast: here, service line, with an "other" option routing to a polite no rather than a calendar.
Step 2: Give every field a decision to feed
Each field should earn its place against one of three jobs: it qualifies, it routes, or it is needed to reply. Fields doing none of the three are research, and research belongs in a survey someone opted into, not in the path of someone trying to buy from you. Here is the six-field form that falls out of the reply above.
| Field | Type | The decision it feeds |
|---|---|---|
Name | Short text, required | Opening line of the reply |
FieldName TypeShort text, required The decision it feedsOpening line of the reply | ||
Email | Email, required, verified | The reply path itself |
FieldEmail TypeEmail, required, verified The decision it feedsThe reply path itself | ||
Service line | Single select, required | Which colleague answers |
FieldService line TypeSingle select, required The decision it feedsWhich colleague answers | ||
Scope description | Paragraph, required, 400-character cap | Whether a call is needed at all |
FieldScope description TypeParagraph, required, 400-character cap The decision it feedsWhether a call is needed at all | ||
Budget band | Single select, 4 bands plus "not sure" | Whether to quote a range or decline |
FieldBudget band TypeSingle select, 4 bands plus "not sure" The decision it feedsWhether to quote a range or decline | ||
Preferred start | Single select, 3 windows | Whether to offer this week's slots |
FieldPreferred start TypeSingle select, 3 windows The decision it feedsWhether to offer this week's slots | ||
Two choices there do most of the work. The character cap forces a summary instead of a story, which is what makes an enquiry answerable in one read. And budget is bands rather than a free-text number, because anything you want to sort or filter later has to be a closed option set from day one; our guide to building a standardized form covers the versioning side of that.
Resist two additions. A required phone number costs completions from everyone who does not want a call, so mark it optional and label it "if you prefer a call". And "how did you hear about us" is an attribution question, not an enquiry question; it belongs in your analytics.
Label every field visibly. Placeholder text inside the box vanishes the moment someone types, which is why the W3C's guidance on form labels treats a persistent visible label as the baseline rather than a nicety.
If your volume justifies more questions, the answer is conditional logic rather than a longer page: show four fields, then open the detailed block when the service line or budget band says it is worth asking. Most builders handle show-and-hide rules with AND/OR conditions and no code, including meetergo's routing forms, which run the rules client-side so nothing reloads between questions.
Step 3: Validate the reply path first
Validation gets treated as a data-cleanliness chore. Its real job here is narrower: make sure you can answer the person. Three things in order.
Make the email field a real email field, not a text field you later regret. A typed field catches the missing @ at the one moment the sender is still around to fix it.
Check the address exists before you accept it. Format validation passes jon@gmial.com all day. This is where server-side checking earns its keep, and in most tools it is a feature rather than a setting. meetergo ships it as the Email Quality Guardian, which blocks disposable and temporary addresses and verifies that an address exists before it enters your records.
Set required flags deliberately, and no further. Required covers the fields your reply draft depends on and stops there. Every extra one is a point where a near-customer closes the tab.
Two more constraints. Cap file uploads in count and size, because an unbounded upload field invites a 60 MB deck you will not open; meetergo accepts multiple files up to 10 MB each. And put a bot check in front of a public form instead of filtering mail afterwards, which here means the Friendly Captcha integration rather than a hidden honeypot.
When validation fires, make the message say how to fix the problem, not that something is wrong. WCAG's error suggestion criterion asks for exactly that, and "enter a date as DD/MM/YYYY" rescues a submission that "invalid input" abandons. Put the privacy line next to the submit button too, because the GDPR's transparency duty attaches at the point of collection, not on a policy page two clicks away.
Be honest about the ceiling. Validation cannot tell you whether an answer is true. A verified address attached to a fabricated budget band still reaches your pipeline, so treat form data as a first filter rather than a verdict. That distinction is what separates workable lead qualification from a scoring model you stop trusting in month three.
Step 4: Publish it where the enquiry actually starts
A form has three realistic publishing routes, and most teams use one. Embedding it on the page that raises the question is the default, pre-filled with the service line, rather than a /contact detour. A standalone link is for anything you send instead of host: an email signature, a proposal footer, a printed QR code. Keep the two separate so you can tell them apart.
The third route is underrated. Sending a form to one named person by email or SMS turns intake into a tracked step rather than a hopeful attachment. On meetergo that sits on the higher tiers and carries open and completion tracking, so you can see the client opened Tuesday's form and never finished it.
Decide one thing before shipping: thank-you page, or booking. If your reply is "here is my calendar" anyway, cut the round trip and put slots on the confirmation step. meetergo's lead capture mode runs that order deliberately, contact details and qualification first, times second, so the lead survives even when nobody books.
Step 5: Route the submission before you switch the form on
This step gets skipped, and it decides whether the form was worth building. Four questions need answers before it goes live: where the submission lands as a record, who owns the reply by name, how fast as a number, and what the sender sees meanwhile.
A form that emails you is not a system. A submission should create or update a contact record so the enquiry has a history, which on meetergo means it lands in the built-in CRM and exports to PDF. If your pipeline lives elsewhere, webhooks fire on submission and the REST API is on every plan including the free one, so pushing into an existing system is not upgrade-gated. Zapier and Make cover the no-code route.
For ownership, write the rule down: service line routes to a person, everything else to whoever is on duty. The mechanics match what sales teams use for lead routing, and a two-person firm needs it as much as a 20-person team, because "we will both see it" is how enquiries sit untouched for three days.
For the acknowledgement, state the reply window you really hit. Not "we will be in touch shortly". A specific "you will hear from Anna within one working day" sets the clock honestly, and an automated workflow can send it plus a nudge to the owner if the submission is still unanswered. If the enquiry ends in a signed document, that step can sit on the same record through meetergo's e-signatures app rather than in a separate tool.
Tools that help
Any mainstream builder produces the six-field form above. The real choice is what happens after submission, so the shortlist splits on that, not on field types.
Google Forms is right for an internal form with no reply obligation: free, instant, responses in a spreadsheet you know. It fits customer enquiries poorly, because the output is a row rather than a contact record. Our Google Forms alternative comparison covers that ceiling.
Typeform and Jotform are the common paid choices. Typeform wins on feel, one question at a time and a design people finish; Jotform wins on volume and field variety. Both treat the booking, the contact record and the signature as something you connect elsewhere, and both cap free-tier submissions, with current figures in our side-by-side of seven online form creators.
meetergo fits when the form is the front of a process rather than the whole of it. It covers more than 20 field types, including rating, NPS, file upload, signature and payment fields, with conditional logic and lead scoring on the answers. You can describe a form in plain language and get a working draft, import existing Typeform forms including the Scale field, or start from a marketplace template. Forms run on servers in Germany with no US CLOUD Act exposure, which matters if the enquiry collects anything you would rather keep under EU law. The free plan allows unlimited forms with 100 submissions a month; Suite at €29.90/month lifts that cap and adds multi-step funnels and lead capture; Premium at €49.90/month adds premium data fields.
Honest limitations. The 100-submission ceiling on Free and Light is tight for a public enquiry form on a site with real traffic, so budget for Suite if volume is the point. Multi-step funnels and lead capture sit on Suite and above, so the free tier gives a single-page form, and PDF templates with the fortified e-signature sit higher still (see current pricing for today's split). It is also not a survey platform: for 2,000 responses and cross-tabs rather than enquiries that become meetings, a dedicated survey tool fits better. For a one-off form with no follow-up, free Google Forms is fine.
If your enquiry form is meant to end in a booked call, a contact record and eventually a signature, test that in one place. Build your first form free with meetergo and wire the Step 5 routing rule while you are there; no credit card required.
Common mistakes
Making phone number required. It reads as a small ask and behaves like a filter against everyone who does not want to be called. Optional and labelled, it still gets filled by people who prefer a call.
Using free text where you will later want a filter. Budget as an open number cannot be banded; service line as open text cannot route. Retrofitting either means re-reading every submission by hand.
Letting the confirmation page promise what nobody delivers. "We will get back to you shortly" is the most broken sentence on the internet. Name the window you hit on a bad week, even if that is three working days.
Treating an enquiry form as anonymous. It is not, and the platform keeps more than the answers. If genuine anonymity is the requirement, that is a different build with different checks, covered in our guide to anonymous forms.
Shipping without submitting it yourself. Fill in your own form from a phone, on mobile data, with a typo in the email field, then check what arrived, who got notified and what the sender saw. Half the problems above surface in that four-minute test.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
FAQs
How many fields should a customer enquiry form have?
As many as your reply needs, which in practice is four to seven. The six-field version in Step 2 covers name, contact route, routing, scope, budget band and timing. Past that, use conditional logic.
Can I build an online form for free?
Yes, on every mainstream builder. Free tiers differ in where they cap you rather than in features: Google Forms is uncapped on responses but weak on follow-up, meetergo's free plan allows unlimited forms with 100 submissions a month plus webhooks and the REST API, and Typeform and Jotform cap responses harder.
What validation does an enquiry form need?
A typed email field, server-side verification that the address exists, visible labels, error messages that say how to fix the problem, required flags only on fields your reply depends on, and caps on file uploads.
How do I stop spam submissions without annoying real senders?
Put a privacy-friendly bot check in front of the form instead of filtering mail afterwards, and block disposable addresses at submission. Both run invisibly for a human sender. Avoid puzzle captchas, which cost genuine enquiries along with the bots.
Can an online form connect to my CRM automatically?
Yes, through a native integration, a webhook on submission, or an automation platform. Check which tier your builder puts webhooks behind first; several gate the API behind a business plan.
