Funnels · 5 min read
What to ask in a quote-request flow without scaring people off
Light screen one, heavy details later, mobile-first labels—so dispatch gets enough without tax-form vibes.
May 20, 2026
Most homeowners will not read your "how we work" PDF before they tap "Get a quote." They are on a phone, halfway through dinner, comparing two tabs. Your job is to collect enough to dispatch and price—without feeling like a background check. The right flow sounds like a short conversation, not a tax form.
1. Ask for the smallest useful slice first
Screen one should be name, phone or email (one is enough to start), ZIP or town, and what they need in plain language—dropdown or 2–3 chips, not a 40-field survey. If they bounce there, nothing downstream saves you.
Save property address, gate codes, photos, and "how did you hear about us" for step two after they have momentum. Every extra required field on screen one cuts completions more than owners expect.
2. Separate "must know today" from "nice for CRM"
Dispatch truly needs: what broke or what they want installed, rough timeline (today / this week / flexible), and whether anyone is home. Scheduling loves photos of model plates, water stains, or breaker panels—make uploads optional but visible ("Add a photo (optional)—helps us bring the right parts").
Marketing wants demographics, budget, and competitor names. Collect that after the lead is captured—follow-up text or a second email link—so the first submit stays light.
3. Write labels the way customers talk
Say "Water heater leaking?" not "Select appliance subsystem." Say "Best time to call you" not "Preferred communication modality." If your office uses internal SKU names, keep them off the public form—map customer language to your dispatch codes on the back end.
4. Make urgency obvious without panic buttons
A simple triage line works: "Is anything unsafe right now? (Gas smell, sparking, major water)" with yes/no. Yes routes to a bold call-911-or-us-now line; no keeps them in the standard queue. You filter real emergencies without turning every form into a red-alert wall.
5. Mobile layout is the real product
Stack fields single-column, 44px-tap targets, numeric keyboards for ZIP and phone, keep submit visible. If a chat widget covers the submit button on iOS Safari, you are silently paying for ads you never see convert.
6. Tell them what happens after Send
One sentence beats silence: "We reply within one business day—sooner for urgent calls." If you auto-text a confirmation, say so. Uncertainty is where people invent reasons to call someone else.
7. Office-side: route answers to action
Every field should map to a column someone reads or an automation you actually run. If nobody uses "Promo code" for two years, delete it. Stale fields train staff to ignore the whole submission.
Starter field order (copy/paste starting point)
- 1. Name + mobile (SMS-capable if you text ETA)
- 2. Town or ZIP
- 3. Service type (short list aligned to how you schedule crews)
- 4. Preferred callback window
- 5. Optional: photo upload, gate/access notes
- 6. Consent line if you text or email promos—default-checked only where the law allows
When to rebuild instead of tweaking
If half your leads say "I filled it out but nothing happened," fix notifications first. If the right jobs never come through, your questions are misaligned with how buyers search—reorder and relabel before you buy more traffic.