Service Enquiry Form Template: What to Ask and What to Leave Out

The short form specification

Copy these labels into your brief. Decide whether email or telephone is your response route; requiring both needs a reason.

• Your name: required so the reply can address the requester.
• Email address: required when the team replies by email; explain that purpose.
• What do you need help with? required short description, with a service example rather than a vague “Message” label.
• Town or service area: required only when coverage determines whether you can help; an exact address can wait.
• Telephone: optional unless the agreed response route requires a call.

For each field record: label | reason | required when | who uses it | next decision. If nobody uses an answer, remove the field.

Add questions that change the next action

A detailed version can add preferred timing, service type and existing-customer status. Explain that a preferred date is a request, not a confirmed appointment. Offer “Not sure yet” when uncertainty is a valid answer.

Budget can help discuss fit, but do not force an invented amount. Photographs may help later; do not make an upload mandatory just because the form supports it. Explain which files are useful and avoid asking for sensitive details you do not need.

Two fictional completed examples

Renovation: “Kitchen refurbishment in Riverside; planning for spring; unsure whether a visit is needed.” The next decision is service coverage and whether an assessment is appropriate, not a remote diagnosis or binding quote.

Regular cleaning: “Small office in Riverside; twice a week; access after 18:00.” Frequency and access restrictions matter more initially than a mandatory photograph. Ask follow-up questions after confirming the type of work.

Specify errors and the confirmation

Use visible labels, clear instructions and errors that identify what to correct. Preserve valid answers after a failed submission. A suitable confirmation says the request was received and explains the actual next step; it must not announce an appointment nobody confirmed.

Test keyboard entry, an invalid email, an empty required field and a failed delivery. Check that the team actually receives the request. The W3C forms tutorial explains accessible labels, instructions and feedback. This specification is an editorial starting point, not proof of accessibility compliance.