Define the decision before choosing fields
What will you do with the submission: offer a rough estimate, arrange a visit or decide whether the job is in scope? Write that decision at the top of your draft. Our recommendation is to require a field only when its absence prevents that next decision or makes it impossible to respond. Information that is useful eventually is not automatically necessary now.
A basic enquiry might need a name, one reliable contact method, service type, city or ZIP code and a short description. A full street address may be necessary for a scheduled visit but premature for a general question. Do not collect payment information, access codes or sensitive documents through an ordinary quote form merely because the form builder offers the option.
Ask for observations instead of technical diagnoses
Illustrative before: “Specify substrate failure and required remediation method.” Illustrative after: “What are you seeing? For example, peeling paint, a stain or a crack.” A customer can describe a symptom without choosing the work your professional assessment will determine. Include “Not sure” when a dropdown otherwise forces a guess.
For a cleaning quote, rooms, approximate size and whether the property is occupied may help. For a garden project, access and a brief description may matter more than exact measurements. Photographs can be optional supporting information. Explain what to photograph and remind customers to leave personal documents and people out of images when those details are unnecessary.
Make the fields understandable on a phone
W3C’s form-instructions guidance recommends identifying required and optional information and explaining formats. Put a visible label above each field and add short help where people are likely to hesitate. “Preferred date, if you have one” is more informative than a required calendar with no explanation of whether availability is guaranteed.
MDN documents input types that provide different controls for email addresses, telephone numbers and other data. Use suitable types and autocomplete settings where appropriate, then test their actual behaviour on common devices. Do not assume an email-format check verifies that the address exists. Avoid rigid phone formatting that rejects a legitimate number because of spaces or punctuation.
Use real enquiries to improve the form
Start with a small field set and review the first useful submissions. Keep a note of follow-up questions. If almost every in-scope enquiry requires one missing fact before you can act, consider adding that field with a clear reason. If a field is mostly blank, guessed or ignored by your team, remove it or make it optional.
Test the awkward cases: a customer who does not know the service name, an out-of-area request and someone who prefers email to telephone. Ensure error messages preserve the details already entered. A quote request should end with an explanation of review and response, not imply a binding price or confirmed appointment before your business has assessed the information.
Your practical checklist
- Define the decision the form supports.
- Require only information needed for that decision.
- Use words a customer would naturally use.
- Allow “Not sure” where uncertainty is normal.
- Mark optional fields and explain unusual formats.
- Review whether staff actually use every field.
Written with AI-assisted research and drafting, with source checks and editorial review for this guidebook. Platform facts link to official documentation. Examples and recommendations are our own; no client results are implied. Sources reviewed October 8, 2026. About Getting Found Local