How fast do you have to reply to a quote request?

A homeowner with a leaking water heater does not shop around. They open a map, tap three contractors in a row, fill in three quote forms, and hire whichever one talks to them first. That is the honest description of how most inbound trade work gets awarded, and it means a quote request is not a lead to be worked later in the week. It is a race, and it is usually decided inside the first ten minutes. So the question is not whether you should reply quickly. It is how quickly, what the reply has to contain, and how you do it reliably at 9pm on a Saturday when nobody is at a desk.

How fast is fast enough?

The useful answer is not a number from a study. It is a comparison: your reply has to land before the other two contractors reply. In practice that means seconds, not minutes, for the first touch, with a real human conversation starting inside a few minutes during business hours.

Think of it as two separate clocks and hold yourself to both:

1. Time to first response. Measured in seconds from the form submission, the missed call or the chat message. This should be effectively instant, because nothing about it needs a person.
2. Time to a real conversation. Measured in minutes. This is when a human, or an assistant working from your own published information, starts collecting what you need in order to price the job.

The reason the first clock matters more than it looks is positional. The homeowner submitted three forms in a row and is now sitting with their phone in their hand. Whoever answers first is the one they talk to, and the conversation that starts first tends to be the one that continues. Everyone who replies after that is replying into a conversation already in progress with somebody else.

Why most trades businesses lose this race

Not because they do not care. Because of where the request lands and what the reply says.

The request arrives in a shared inbox while the owner is under a sink and the office manager is on the phone with a supplier. Nobody is ignoring it. There is simply no mechanism that notices it and acts in the absence of a free pair of hands.

Then there is the content problem. The replies that do go out tend to be acknowledgements rather than next steps. "Thanks for reaching out, someone will be in touch shortly" gives the homeowner nothing to act on and nothing to hold onto. It does not confirm the job address, it does not establish whether this is a burst pipe or a kitchen remodel being planned for spring, and it does not get you a photo of the actual failure. So the first real conversation happens hours later, starts from zero, and often starts with the homeowner saying they already booked someone else.

The money leaks in three specific places:

• After-hours requests get a next-business-day reply. For an emergency job that is the same as no reply, and evening and weekend requests are frequently the highest-intent ones you get.
• Requests with no scope attached get triaged by guesswork. A technician drives out to a job that was never worth the trip while a high-value replacement sits unanswered in the same inbox.
• Nobody can see where the leak is. First-response time is not recorded anywhere, so you cannot tell whether you are losing leads at the reply, at the scoping conversation, or at the estimate.

What your first reply actually has to do

Speed on its own is not worth much. A fast message that says nothing is still a message that says nothing. A first reply that earns the job does four things:

1. Names you and names their problem back to them. "We have your request about the water heater at 14 Mill Lane" proves a human system received it, not a form confirmation page.
2. Asks exactly one question, answerable in one tap. The best first question is urgency: is this an emergency today, something for this week, or are you planning ahead? Nothing else you can ask changes your next action as much.
3. Arrives on the channel they used, from a local number, in the same thread any later message will come from.
4. Gives them a real next step, not a promise that someone will call. Either a time, a link to pick one, or a straight statement of what happens next and when.

That urgency answer is the whole triage. Emergency today routes straight to an on-call technician's ringing phone. This week goes into scoping. Planning ahead gets collected properly and stops consuming emergency attention. One question, three completely different operational paths.

How to reply in seconds without living on your phone

Step 1: Shorten the form to five fields

Name, mobile, service needed, job address, what is happening. That is it. Every additional field costs you completions, and the rest can be collected conversationally once the thread is open. Put the same five-field form on every service page and in your map listing so you can compare sources honestly.

Step 2: Make the instant reply a workflow, not a task

The reply fires on form submission, inbound chat, an inbound text to the business number with no open conversation, or a missed call on that number. Missed-call text-back matters more than people expect: an unanswered ring becomes a conversation instead of a voicemail nobody checks. There should be no wait step at the front of this. Every second is the product.

Step 3: Write a separate after-hours version

Do not send the business-hours message at 11pm. Send one that is honest about the hour and still gives them something: the office opens at a stated time, they are first in the queue, and if it is an emergency right now there is a keyword that pages the on-call technician. Only launch that message once somebody has actually committed to honouring the queue position it promises.

Step 4: Let an assistant collect the scope

BO, the assistant on the platform, picks up the reply and collects the four things a human needs before pricing: confirmed job address, service type, urgency, and a photo or a written description. It checks the ZIP code against your service area and tells out-of-area homeowners immediately and politely rather than letting them absorb two phone calls and a wasted drive.

The guardrails matter as much as the capability. BO never states a price, a range, an hourly rate or a call-out fee. It never promises an arrival time, because it cannot commit a truck. It never diagnoses. And it hands off to a person immediately on any mention of gas, smoke, sparking or flooding, on any explicit request to speak to a human, and after a third unanswered question. Pricing and diagnosis are the technician's job.

Step 5: Ask for a photo, with a link that works on a phone

A single-field mobile upload page, sent as a short link, is worth more to your triage than any extra form field. A photo of the data plate and the failure lets you decide between a site visit and a phone quote before anyone turns a key. If no photo arrives after a couple of nudges, mark the job as priced without one so the estimator knows to pad the contingency, and move on.

Step 6: Build an alert for when the reply does not fire

Five minutes after a request is created, if nothing has gone out, the owner gets a text and a task. This is the workflow that keeps the rest honest. Without it, a broken integration looks exactly like a quiet week.

Step 7: Put the follow-up ladder on a timer, not on memory

Once a human has priced and sent the quote, the chase runs by itself: a next-day text offering to walk through anything unclear, a plain-language restatement of scope two days later, and a decision prompt that asks for a yes, a no, or a not-yet and says that any of the three is a useful answer. Non-answers land in a named lost stage with a reason attached instead of evaporating.

The full build, including the field list, the stage definitions and every message, is documented in the instant quote request response build guide.

Mistakes that make a fast reply worthless

Mistake 1: Replying fast with an acknowledgement

"We will be in touch" is a slow reply wearing a fast reply's clothes. If the message does not advance the job, the clock has not really stopped. Put a question or a next step in every first message.

Mistake 2: Texting from a number they do not recognize

Use one local business number for everything inbound and outbound, in the same thread. A reply from a different number than the confirmation reads as spam, and homeowners answer local numbers and ignore toll-free ones.

Mistake 3: Skipping sender registration

Unregistered application-to-person messaging traffic gets filtered silently, which looks exactly like a broken build. Complete brand and campaign registration before launch, register the traffic honestly as customer care and conversational, and submit sample messages that match what you actually send. Allow a week or more for approval. The same applies to your email sending domain: publish authentication records before the first send, or your instant email lands in spam, which is worse than not sending it.

Mistake 4: Letting the assistant quote

The fastest route to a lost job and an unhappy customer is an automated number that the technician then has to walk back on site. Have the assistant say that pricing depends on what the technician finds, and that it will get a real figure from the team. Then make sure somebody has committed to a pricing turnaround, because that promise gets made in writing.

Mistake 5: No on-call rotation behind the emergency path

If nobody owns emergencies, the emergency path is decoration. Name the rotation, with real cell numbers and agreed hours, and build escalation into it: if the first technician does not answer within a few rings, move to the next; if nobody has replied in the thread within five minutes, call and text the owner.

Mistake 6: Treating a planning-ahead lead like an emergency

Someone replacing a water heater before winter does not need a technician paged. They need their scope collected properly and a quote when you said it would arrive. Mixing the two paths is how emergency capacity gets consumed by jobs that could have waited a week.

How to measure your response speed

Record the first-response time in seconds on every request, as a field, automatically. If it is not a field, it is an opinion. Then watch:

• Median first response in seconds, by source and by hour of day. Use the median, not the average. One slow outlier should not hide a fast system, and one fast outlier should not hide a slow one.
• Reply rate to the instant message, split between inside hours and after hours. If the after-hours reply rate collapses, the after-hours copy needs work, not the timing.
• Share of requests reaching a confirmed scope, and how long that takes from first contact. This tells you whether your question order is working.
• Photo attach rate. A low rate usually means the upload link is buried too deep in the message.
• Time from scope confirmed to quote sent. This one is a human bottleneck rather than an automation one, and it is usually the first thing the data exposes.
• Emergency claim time, in minutes, from the emergency flag to a team member's first message. Anything above five minutes means the rotation is wrong.
• Out-of-area rate by source. A spike here usually means an ad radius or map listing needs tightening, which is the cheapest fix on this list.
• Opt-out rate on your business number. A rising rate means frequency or relevance has drifted, and your deliverability depends on it.

Before you build any of this, settle four things: your service area as an explicit ZIP code list, a named on-call rotation with agreed hours, your business hours and the after-hours promise you will keep, and who prices jobs with what turnaround. Messaging consent, opt-out handling and quiet-hour rules vary by jurisdiction and change often, so have your own counsel review your consent language and privacy terms before launch rather than after the first complaint.

If you want this running on your existing number and forms rather than assembled from scratch, book a call and we will scope it against your actual inbound volume. If your problem is further down the chain and quotes are going out but not closing, the estimate to signed job build covers delivery speed, follow-up and the close.

Frequently Asked Questions

Is an instant automated text worse than a slower personal call?

Not if the text is written like a person and asks a real question. The two are not alternatives anyway: the point of the instant message is to hold the conversation open until the call can happen. The sequence that works is an instant text that asks about urgency, then a human call within minutes during business hours. What loses jobs is making the homeowner wait for the call with nothing in between.

What should the after-hours message say?

Name the business, name what they asked about, state when the office opens, tell them they are first in the queue, and give them a keyword that pages the on-call technician if it cannot wait. Do not pretend to be staffed, and do not promise a callback time nobody has agreed to honor.

Do I need a separate number for this?

You need one local number that handles all inbound and outbound messaging for quote requests, and it should be the same number your confirmations come from. Separate tracking numbers per lead source are worth adding so the source is set by the number that called rather than by what somebody remembers to ask. What you should avoid is messaging from a number the homeowner has never seen.

How do I know the instant reply is actually firing?

Build the breach alert, and test it. Submit your own form from a phone that is not on your network, once a week, and check the recorded response time. Also watch for requests that sit in the first stage past five minutes, which is the signature of a form or integration that has quietly broken.