ENQUIRY DESIGN GUIDE
Contact form or guided quote request: which does a business website need?
A short form is best when a conversation can begin with a few details. A guided quote route is better when missing information causes repeated messages, poor qualification or slow pricing.
WHEN EACH ROUTE FITS
Complexity should earn its place.
The goal is not to collect the most data. It is to collect enough information for the next responsible action.
Use a simple contact form
Best when most enquiries need the same few details, a person will call back and an early price is not expected.
Use a guided quote request
Best when service type, measurements, quantities, vehicle, location, files or timing materially change suitability or price.
Use booking instead
Best when the customer can choose a defined service, duration, provider and available slot without prior assessment.
Use a call route for urgent work
Best when safety, immediate availability or fast verbal assessment matters more than a multi-step form.
DESIGN THE QUESTIONS
Every field needs a decision behind it.
Start with the admin response: what must be known to accept, decline, price, schedule or ask one useful follow-up question?
01
Identity and reply route
Request the minimum contact details needed to respond, and explain how the information will be used.
02
Service or problem
Use customer language and reveal specialist questions only after the relevant choice.
03
Variables that affect the decision
Ask for quantity, size, vehicle, postcode, deadline or budget only when it changes fit, effort or routing.
04
Files with a defined purpose
Request photographs or documents only when someone will review them, with visible format, size and privacy rules.
05
Consent and confirmation
State what happens after submission, avoid preselected marketing consent and send a readable copy or summary.
AFTER SUBMISSION
A form is only useful when the response process works.
The customer confirmation, admin view and reply route should use the same reference and preserve the information already supplied.
Readable admin notification
Show the service, important variables, contact details and direct access to the full request in a predictable order.
Acknowledgement, not a false promise
Confirm receipt, expected next step and normal response window without presenting an indicative result as a final price.
One reply thread
Keep customer and project messages linked to the request so important decisions are not scattered across unrelated inboxes.
Measurement with context
Track successful submissions and source pages, then review request quality rather than counting form starts alone.
Abuse protection and fallback
Use rate limits, spam checks and clear errors while preserving an alternative contact route for genuine users.
COMMON QUESTIONS
A few useful things before we start.
Will a longer form always produce better leads?
No. Unnecessary fields increase effort and abandonment. Ask a question only when its answer changes qualification, price, routing or the next reply.
Should a guided form give an automatic price?
Only when the pricing rules are complete and reliably testable. Otherwise it should prepare a structured request for human review.
Can customers continue the conversation in an account?
Yes, when the request, messages and permissions share one customer identity and the account provides a simpler experience than email alone.
DESIGN FROM THE REPLY BACKWARDS
List what the business needs for one useful first response.
That list reveals whether a simple contact form, guided quote, call or booking route is the right first version.