Good customer inquiries don't need to be long. This check shows which details you really need to cut down on back-and-forth – without scaring customers off with a long form.
1. Start with the follow-up questions you actually ask
Look at ten inquiries you handled recently. Note only the type of missing information, not the sender's personal details. Was it the ZIP code, the service needed, or how urgent it was?
Count which follow-up question came up again and again. That is a better basis than assuming a longer form automatically brings better leads. If your inquiries are already complete, you don't need a new feature.
- Recurring follow-up question identified
- Your current contact route tested yourself
- No customer documents pasted into a public AI tool
2. Every extra field has to change a decision
For each field, ask: what will I do differently with this answer? For a local service business, the ZIP code can matter for checking your service area. A full street address may be unnecessary at first contact. For a quote, a short description of the job is often more useful than a required phone field.
Fictional example: a repair business first needs to know whether it serves the location and what work is wanted. The hint could read: “Please tell us your ZIP code and briefly describe what needs fixing.” That is neither an instant commitment nor a fixed price.
- Required fields limited to the first processing step
- Optional fields clearly marked
- Reason given for any unusual question
3. Explain what happens after the inquiry
“Submit” is an action, not an explanation. Say in one sentence whether you will ask follow-up questions, schedule a visit or prepare a quote. Only promise a fixed response time if your team can keep it on a busy day.
A suitable confirmation: “We've received your request. We'll check whether we can take on the job and get back to you using the contact details you gave.”
An inquiry is not a confirmed booking. That difference shouldn't only be in the fine print.
4. Test on a real smartphone
Read the page as if you'd never seen it. Can you find the service and the contact option? Do field labels stay visible while you type? Is each error message tied to the specific field? A placeholder doesn't replace a permanent label – the W3C's forms tutorial explains labels, instructions and error messages in detail. [1]
Send a clearly marked internal test inquiry. Check that it arrives, that the confirmation is sent and that it reaches the right person. A button that looks fine doesn't prove a working inquiry route.
- Works with a keyboard, with a visible focus
- No unnecessary required fields
- Errors understandable and fixable
- Test inquiry and confirmation actually received
5. Change one thing at a time
Note the date and the exact change. Afterwards, check how often the chosen follow-up question is still needed. Compare similar periods and allow for a different mix of inquiries. A handful of inquiries isn't enough for a reliable success rate.
Your task for today: pick one recurring follow-up question, write a short hint for it, test on your phone and check the existing delivery route. You don't automatically need a new form or an AI assistant for this.
The examples are illustrations, not customer case studies. This checklist supports your own review; it doesn't promise a business result.
Frequently asked questions
How many fields should a contact form have?
There's no universal number. Keep the required fields to what you need for the first step – often name, a way to reach the person, ZIP code and a short description – and mark everything else as optional.
Should I promise to reply within an hour?
Only if your team can keep that promise every day. Otherwise describe what happens next without a fixed time.
Your next step
Want someone else to look at your contact page? Request the free website audit – practical suggestions by email, no obligation. If you want to know whether your forms work for everyone, the Accessibility Check (WCAG) tests your homepage and up to ten subpages in a real browser and explains the main issues in plain English.
General information, not legal advice. Google, Microsoft, OpenAI and Perplexity change their products and help pages; the linked sources in their current version take precedence.
Sources
- W3C Web Accessibility Initiative, “Forms Tutorial.” https://www.w3.org/WAI/tutorials/forms/ — Accessed November 3, 2026.