Start from your first reply

Think about the first useful reply you'd send to a new quote request. What do you need to know to write it? That's your required list. Everything else is optional or can wait.

A typical field set for a local service business

FieldRequired?WhyInput tip
NameYesTo address themOne "Name" field is simpler than first/last
Phone or emailAt least oneTo replyLet them choose their preferred method
Service neededYesTo route and prepareShort list plus "Something else"
Postcode / areaUsuallyTo confirm you cover themShort text
TimingOptionalUrgency and planningChoices: urgent, this week, flexible
DetailsOptionalContextFree text with a helpful prompt
PhotosOptionalHelps for some tradesOnly if your tools handle uploads safely
Consent to marketingOptional, separateOnly if you send marketingUnticked checkbox

Make it work on a phone

  • Use the right input types (type="email", type="tel") so phones show the right keyboard. MDN's tel input and autocomplete references explain how.
  • Add autocomplete hints so browsers can fill name, email and phone.
  • Visible labels above fields, not placeholder text that disappears.
  • Big enough tap targets and a clear submit button.
  • Error messages that say exactly what to fix, next to the field.

The W3C's forms tutorial covers labels, instructions and error handling in an accessible way.

Fields to avoid

  • Passwords, payment details or ID numbers. Never in a quote form.
  • Sensitive details (health, legal, financial) in a general form; route those to a suitable process. See customer data in automations.
  • "How did you hear about us?" as required. Useful to you, annoying to them. Make it optional or ask later.
  • Long dropdowns that are hard to use on phones.
  • Pre-ticked marketing consent.

Help the customer write useful details

A blank "Message" box gets "Need a quote". A prompt gets better answers: "What's happening, and anything we should know? For example: the model, when it started, access notes."

After they press submit

  • Show a clear confirmation on the page with what happens next.
  • Send an acknowledgement — see inquiry acknowledgements.
  • Route it to a named owner — see form lead routing.
  • Store it somewhere besides an inbox.

On MendRev sites

Every MendRev site includes click-to-call, tap-to-email and a quote form that delivers to your inbox, tested monthly on website plans. We set up the fields with you; we don't add fields you can't use.

Questions

Should I ask for a budget?

Only if it genuinely helps you respond, and make it optional with ranges. Many customers don't know yet, and a required budget field can put them off.

Should I ask for the full address?

For on-site work, a postcode or area is usually enough to check you cover them. Ask for the full address once you're arranging a visit.

Sources and further reading

Official documentation changes. Check the current version before you rely on a rule, limit or setting.

Next step

See a site built around your real details.

Look at sample layouts (fictional previews, not client work), read published website pricing, or ask for a free concept preview.

Already happy with your site? Website Maintenance covers monitoring, a monthly form test, backups and edits.