What should you ask on a “request a quote” form?

Think of the form as the start of a conversation

A potential customer wants a price, but you need to know more before you can give one. A request form can collect a few useful details while you are busy.

It does not have to replace the conversation. Its job may simply be to help you decide whether you can take the work and what to ask next.

Imagine a mobile detailer in Clermont. Before calling back, they may need a name, a contact method, a general location and the type of service requested. A detailed condition assessment can wait until it is useful.

Give every question a reason to be there

For each box, ask: will this answer change what we do next? If not, consider leaving it out or making it optional.

• Name: so you know how to address the person.
• Contact method: so you can reply in a practical way.
• Service needed: so the request reaches the right person.
• Location: when it is needed to check your service area.
• A short description: so the customer can explain anything the choices missed.

A preferred date can help with planning, but label it as a preference unless you are actually offering a confirmed appointment. Explain why you need an exact address if a town or postal code would not be enough at this stage.

Use the words a customer would use

A customer may not know your internal names for services. Offer plain choices and an “I’m not sure” option when that makes sense. Avoid making someone guess just to submit the form.

Put clear labels beside the boxes. Explain which answers are required, and show a useful message if something needs fixing. The W3C forms guide describes why labels, instructions and feedback matter.

If you ask for photos, say what would be useful and let people know how to avoid including private details. Do not add uploads merely because the website can support them.

Explain what happens after “send”

A confirmation should tell the customer that the request arrived and what happens next. If you need to review the details before quoting, say that plainly.

Only state a reply time your team can reasonably meet. Give another way to contact you if the request needs a conversation. Do not describe the job as booked just because someone submitted a form.

On your side, decide who reads new requests and who covers absences. Keep the message in a place the team checks rather than relying on one person remembering to forward it.

Test it with a made-up request

Ask someone outside the business to try it too. Notice where they hesitate. Removing one unnecessary question or explaining one choice can be a useful improvement.

Praxen helps build websites and enquiry forms around the details a business actually needs. For the next step, read how to keep customer requests organized.