Website · How-to
Website quote request forms that homeowners actually finish
Ask for as little as you can: name, mobile number, address, the service, and an optional box and photo upload. Stop bots with a hidden honeypot field before you reach for a CAPTCHA, send every request to a phone as well as email, and reply within the hour. Then show a thank-you page that says exactly who will call and when.
What to ask: the fields that earn their place
Every field you add is one more reason to quit halfway. web.dev’s form guidance puts it bluntly: don’t ask for data you don’t need, because removing fields is the simplest way to make a form easier [1]. Baymard Institute, which tests checkout forms, found people get intimidated by forms with 10 to 15 or more fields, and 18% of users it surveyed had abandoned a cart in the previous quarter because the checkout form felt too long or complicated [2]. A quote request isn’t a checkout, but the person filling it out on a phone feels the same friction.
For most home-service companies, six fields cover it:
| Field | Required? | Why and how |
|---|---|---|
| Name | Required | One box for the full name, as web.dev recommends [1]. Splitting first and last adds a field for no gain. |
| Mobile phone | Required | Use a phone-type field so phones show the number pad [1]. This is how you’ll actually reach them. |
| Service address or ZIP | Required | Tells you whether they’re in your area and how far the drive is. |
| What do you need? | Required | A short dropdown of your main services plus “Something else.” |
| Tell us about it | Optional | One open box. Prompt with an example: “Water heater is 12 years old and leaking from the bottom.” |
| Photos | Optional | See the next section. Often the most useful thing on the form. |
Email can be optional; many homeowners would rather get a text. If you add “How did you hear about us?” keep it optional and short. Leave out budget, timeline grids, and “best time to call” matrices on the first form. You’ll get those on the phone.
Mark both kinds of fields. Baymard’s testing found only 14% of sites marked both required and optional fields, and on sites that marked only the optional ones, 32% of test users hit validation errors because they skipped required fields [3]. Put “(required)” and “(optional)” right in the labels.
Let them send photos
A photo answers questions you’d otherwise spend a site visit on. A roofer can see whether it’s a few missing shingles or a whole slope. An electrician can read a panel label. A landscaper can see the slope of a yard and where the gate is. Keep the upload optional so nobody gets stuck, and tell people what to shoot.
Upload prompt (plumbing example): Optional: add up to 5 photos. Helpful ones: the whole fixture, the label or model plate, and where the water is coming from.
Upload prompt (remodeling example): Optional: add photos of the room from each corner, plus anything you want changed. Phone photos are perfect.
- Accept photos straight from a phone. Make sure the upload button opens the camera or photo library on both iPhone and Android.
- Check your form tool’s file size limit. Modern phone photos are large, and a form that silently rejects them loses the lead.
- Make sure photos arrive with the submission, either attached or as a link that works on your phone.
- Delete customer photos you no longer need, the same way you’d shred paper estimates.
Address fields and autocomplete
There are two kinds of “autocomplete,” and one of them costs nothing.
Browser autofill (no cost)
Tag your fields with the standard autocomplete values (name, tel, email, street-address, postal-code) and the visitor’s phone can fill them in with one tap. web.dev recommends using these values whenever one fits, and suggests a single address box tagged street-address because it fits any format and is easy to paste into [1].
Google address suggestions (paid)
Google Maps Platform’s Place Autocomplete shows address predictions as someone types, like the Maps search box. It needs an API key and is billed by use [6]. Worth it for high-volume forms where bad addresses cost you trips; overkill for most small shops.
Either way, use the address to screen service area. If you only work in certain ZIP codes, a friendly line under the field (“We serve Ramsey, Washington and Dakota counties”) saves both of you a call. Don’t hard-block out-of-area addresses; a landlord might live across the state but own a rental in your town.
Stopping spam without blocking customers
Any form on the open web gets spam within days. Layer your protection so bots get stopped and people don’t notice it’s there.
- A honeypot field. A hidden field humans never see. Bots fill in every box, so anything that fills this one gets thrown out. Netlify’s documentation, for example, shows a hidden field that silently rejects any submission with a value in it [5]. Most form plugins have a honeypot setting.
- An automatic spam filter. Many form services run submissions through a filter. Netlify, for one, checks every submission with Akismet and puts flagged ones in a separate spam list [5]. Check that list weekly at first; real leads sometimes land there.
- A CAPTCHA only if you still need it. reCAPTCHA is available in most form tools [5]. Prefer the invisible kind over puzzles. Making a homeowner click on crosswalks with wet hands is a good way to lose them.
Spam calls are their own problem; see how to stop spam calls on a business phone.
Where submissions go
A form that emails an inbox nobody checks on Saturday is worse than no form, because the customer thinks they’ve reached you. Set it up so a new request reaches a person within minutes:
- Text plus email. Send every submission to a phone as a text or push alert, and to email as the record. Many form tools and job software apps can do both.
- More than one person. The owner and whoever schedules. If you’re a one-person shop, add a backup who can at least send a reply on your vacation days.
- Into your job software if you have it. Jobber, Housecall Pro and similar tools can take web requests directly, so the customer record exists before you call.
- Whitelisted in email. Send yourself a test and mark it “not spam.” Form emails often land in junk folders.
- Readable on a phone. Name, phone, address and service at the top, so you can tap the number and call from a truck.
Reply fast: the hour that matters
The best form in the world doesn’t help if the reply comes tomorrow. In research published in Harvard Business Review in 2011, firms that tried to reach a web lead within an hour were nearly seven times as likely to qualify it as firms that responded later, and the same audit of 2,241 U.S. companies found 23% never responded at all, and those that did reply within 30 days took 42 hours on average [7]. Our guide on how fast to call back leads goes deeper.
Set up an automatic text the moment the form comes in, then follow with a real call:
Auto-text: Hi [Name], this is [Your name] at [Company]. Got your request about [service]. I’ll call you by [time window you can keep]. If it’s urgent, call [number].
If no answer on the first call: Hi [Name], tried you just now about the [service] at [street]. When’s a good time today or tomorrow? You can also reply with a time and I’ll call then.
Only promise a time you can hit. Texting rules and consent apply to these messages too; our missed-call text-back guide covers the basics.
The thank-you page: tell them what happens next
After someone hits submit, they should land on a page (not just a small “sent” line) that answers “now what?” It’s also the page you can count in Google Analytics or your ad platform as a lead. Give the submit button a label that says what it does, like “Send my request” rather than “Submit”; web.dev makes the same recommendation for form buttons [1].
Thank-you page copy: Thanks, we’ve got it. [Name or “Someone from our office”] will call or text you from [number] within [time you can keep, during business hours]. Requests after [time] get a call the next morning. If water is actively leaking or you have no heat, call us now at [number]. While you wait: [link to a relevant page, such as your reviews or a project gallery].
Keep the phone number tappable, keep your logo and menu on the page, and don’t pile on upsells. One clear next step.
Test it like a customer, every month
In a 2014 eye-tracking study presented at the CHI conference, researchers applied 20 usability guidelines to forms taken from real company websites; with 65 participants, the improved forms were finished faster, needed fewer submission attempts and left users more satisfied [4]. You don’t need a lab to get most of that benefit. Run this check on your own phone:
- Fill out the form on an iPhone and an Android, on cellular data, not office Wi-Fi.
- Watch the keyboard: number pad for phone, @ key for email.
- Leave a required field empty and submit. Is the error clear, next to the field, and does it keep everything else you typed?
- Attach two phone photos. Do they arrive?
- Time how long it takes from submit to the text on your phone.
- Check that the auto-text arrives and the thank-you page loads.
- Look in the spam folder and in your form tool’s spam list.
- Try the form from a page deep in the site, not just the contact page. Every service page should have a link to it.
If your form works but the page around it loads slowly, see contractor website speed. The form is one stage of eight in the contractor website guide.
Common questions
Prefer a site that’s already set up?
Our builder makes a site for a trade business in roughly five minutes; it lives at getoutfitter.ai/site/your-name with a small banner, costs nothing, and changes whenever you text the AI assistant. Professional is $79 a month: the web address of your choice, no banner, hosting and SSL, your logo and images, and automated Google review requests and posts. You get 30 days free and there’s no contract.
See how the website worksSources and how we compared
Form design advice comes from web.dev, Baymard Institute’s published research and a peer-reviewed form-usability study; spam and autocomplete details from Netlify’s and Google Maps Platform’s documentation; response-time figures from the Harvard Business Review study as quoted by Venture Harbour; all opened October 4, 2026, and the text templates are examples.
- web.dev: Payment and address form best practices (Sam Dutton)
- Baymard Institute: Form Design — 6 best practices (Christian Holst) — December 2021; ecommerce checkout research
- Baymard Institute: Mark both required and optional form fields — October 2018
- Seckler, Heinz, Bargas-Avila, Opwis & Tuch: Designing usable web forms — empirical evaluation of web form improvement guidelines (CHI 2014)
- Netlify Docs: Spam filters for forms — last updated July 2025
- Google Maps Platform: Place Autocomplete (Maps JavaScript API)
- Venture Harbour: How fast do marketing leads turn cold? (quotes Oldroyd, McElheran & Elkington, Harvard Business Review, 2011)
Last updated October 4, 2026. Prices change; if something here is out of date, call or text (507) 628-0400 and we’ll fix it.