Quote Request Forms: The Questions That Get One Answered

Short answer: a quote request form needs five or six questions — how to reach them, what the job is, where it is, when they need it, and the one thing your pricing actually turns on — asked in that order, with a range shown rather than hidden. Most forms in this category collect more than that and still cannot produce a quote from it. Here is why, and what to ask instead.

The test every question has to pass

A quote request form has exactly one job: collect enough that you can send a real number, or know why you cannot.

That gives you a hard test for any field. Can you price differently depending on the answer? If two different answers produce the same quote and the same next action, the field is not helping you price — it is reporting, and reporting belongs in analytics rather than on the critical path of somebody's first contact with you.

Run that test over an existing quote form and it usually removes a third of the fields. "How did you hear about us" fails it. "Company name" fails it for most residential work. "Preferred contact time" fails it unless you genuinely schedule callbacks around it, which almost nobody does.

The six that pass

1. How to reach you. One required field, the channel you will actually respond on. For urgent work that is a phone number, because emailing someone standing beside a broken machine is not a response. Make the second channel optional. Requiring both is the most common reason a short quote form still underperforms.

2. What is the job. Free text beats a dropdown here more often than expected. A dropdown forces you to have anticipated the category, and the enquiries that do not fit pick "Other" and tell you nothing. Free text with a short prompt — "what needs doing, and anything you already know about it" — produces the sentence you will quote from.

3. Where. A service-area check before you promise anything. This is the highest-value qualifying question for any mobile business and it never feels intrusive, because the customer already understands why you are asking.

4. When. Urgency changes both the price and the queue. Three options are enough: as soon as possible, within a few days, planning ahead. The middle option is the one people actually pick, and knowing they are not standing in the rain changes how you sequence the callback.

5. The pricing question. One question, specific to your trade, that moves the number more than anything else. A locksmith needs to know whether any working key exists. A roofer needs the approximate area. An electrician needs whether the panel is being replaced or extended. You know yours; it is the first thing you ask on the phone.

6. Anything else — optional. A catch-all box and an optional photo upload. The useful detail lands here more often than in any structured field, because people describe their own problem better than your categories do.

The order matters as much as the list

Position	Question	Required	Effect if moved earlier
1	Name	No	—
2	Phone or email	Yes	—
3	What is the job	No	—
4	Where	No	Reads as a filter before you have understood the job
5	When	No	Fine, but less informative before scope is known
6	The pricing question	No	Feels like an interrogation; abandonment rises
7	Photos and notes	No	Blocks people who are not on site

Two deliberate choices. Only the contact method is required, and the hardest question sits near the end.

Both follow from the same fact: people abandon at the first question they do not want to answer, and everything above that point is still worth having. A partial request with a name and a number is a lead you can call. A complete request you never received is nothing. The wider mechanics are in reducing form abandonment.

The budget question

Sales advice says to qualify on budget early. For inbound quote requests from consumers and small businesses, that advice is usually wrong.

Most customers genuinely do not know what the work costs — that is why they are asking you. Being asked for a budget before anyone has understood the job reads as being sized up, and the honest answer ("no idea") does not fit the dropdown, so they leave.

The exception is work with a legitimately enormous range, where a rough band saves both sides a wasted conversation. Even then: make it optional, offer wide bands, and include "not sure yet" as a real option rather than a trap.

Show a range instead

The higher-leverage version of the budget question is to answer it yourself, on the page, before the form.

"Most jobs of this type run between X and Y, depending on Z" does three things at once. It filters out the enquiries that were never going to convert, so you stop paying for those calls. It raises the quality of the ones that do arrive, because everyone submitting has accepted the order of magnitude. And it builds trust with the majority who have been quoted evasively by everyone else they contacted.

The objection is always that the range is too wide to be meaningful. Usually the range is wide because it depends on two or three specific conditions — so state the conditions. "£X for a standard replacement; £Y if the unit needs relocating" is more useful than any single number and more honest than silence.

Photos, and why optional matters

For anything visual, an upload field turns quotes that needed a site visit into quotes you can send from the office. A photo of the damage, the model plate, the serial number, the panel — each removes a round trip.

It must be optional. A required upload blocks the person standing in the wrong place with the wrong phone at the worst moment, and that person is frequently the most urgent enquiry of the day. Make it optional, say what a useful photo would show, and a surprising share of people will provide one.

If your technicians are the ones capturing photos and details on site, that is a different flow with a different problem — you generally do not want to give every field worker a full account. The pattern for that is in field team form collection without account access.

What has to happen after submit

A quote request that only lands in a database is a lost quote. Two messages fire automatically or the form is not finished.

To you: fast enough to act on. The person requesting a quote almost certainly requested two or three others in the same sitting, and response speed is one of the few variables in that race you control entirely. Email is fine at a desk and poor in the field; SMS costs more and gets read. The tradeoff is in speed to lead: SMS versus email notifications.

To them: a confirmation naming what you received and when you will reply. "We've got your request about the garage door — an estimator will call you before 5pm today" holds your position in the queue while the competitor who sent nothing loses theirs. On BotForms this automatic reply is configured on the form itself, and it can carry an attachment, which is the same mechanism used for lead magnet delivery.

Turning the request into the quote document

Once the details are structured, the quote itself becomes mostly mechanical. A submission can generate a branded PDF automatically — the customer's details, the scope as described, your terms and your branding — which removes the retyping step that usually sits between an enquiry and a document. That is covered in generating a branded PDF from every submission; white-label PDFs are on the Business plan, and standard PDF generation is on every plan including Starter.

If you already have a paper estimate sheet your estimators trust, rebuilding it digitally is usually a better starting point than designing a new form from scratch, because the document already encodes years of knowledge about what you need to ask. That path is converting a PDF to an online form.

Keeping the junk out

Quote forms attract automated submissions like any other public endpoint, and the real cost is not the nuisance — it is that bot volume inflates your conversion numbers, so a page that is genuinely underperforming reads as fine.

A hidden honeypot, a minimum time-to-submit threshold and server-side content filtering catch most of it and cost real visitors nothing. A visible CAPTCHA belongs last, because it measurably reduces genuine submissions on exactly the form where each one is worth the most. The full ordering is in stopping contact form spam without a CAPTCHA, and spam protection is included on every BotForms plan rather than sold as an add-on.

What it costs to run

As of August 2026: Starter $29/month ($23 annually) with unlimited forms, 1,000 submissions, 100 AI-builder runs, PDF generation and an automatic welcome email; Pro $79 ($63 annually, $49 founder) with 10,000 submissions, unlimited PDF tracking, five team collectors and API access; Business $199 ($159 annually) with 50,000 submissions, unlimited collectors and white-label PDFs. Thirty-day trial on every plan, no free tier, SMS as a separate add-on from $29/month.

For a business quoting jobs worth hundreds or thousands, the arithmetic is not really about the subscription. It is that one recovered quote a month — the one that would have gone to whoever replied first — covers the whole thing several times over.

Start a 30-day trial and generate a quote form from a description of your trade, or read the feature list and published plans first.