Lead response time: what good looks like for a service business

For a service business, good lead response looks like this: a useful first reply within one minute on any channel, at any hour; a reply to the customer's reply within one minute during the conversation; and, where a person needs to call, a callback within the hour during business hours, at a time the customer agreed to. These are targets you can actually measure from your own inbox. They are not industry statistics.

Three different clocks

People talk about "response time" as one number. It is three.

Time to first reply. From the lead's first message (form, call, DM) to your first useful reply. This is the one automation fixes completely, because the AI does not have to notice a notification.

Time to reply within a conversation. Once they have replied, how long until the next answer. A lead who replies and waits ten minutes has moved on. Automation fixes this for the simple cases; for the rest, it depends on someone owning the inbox.

Time to human. When the rules hand off to a person, how long until the person actually engages. This is a staffing and process number, and it is the one most businesses do not measure.

Targets

Time to first reply: under one minute, 24 hours a day. This is achievable with an AI receptionist and not otherwise.

Time to reply within a conversation: under one minute for anything the AI handles; under ten minutes for anything handed to a person during business hours.

Time to human callback: within the hour during business hours, at a time agreed by text ("Dana will call at 2"). After hours: first thing in the morning, and say so.

Why "useful" matters

A first reply that says "thanks, we will be in touch" in ten seconds does not count. It has to do something: answer, offer times, ask the one question you need. Measuring time to a useless reply produces a flattering number and no bookings.

How to measure from your own inbox

Your platform should timestamp every inbound message and every reply. Report, by week and by location:

1. Median time to first reply, and the share over one minute.
2. Median time to reply within conversations, split by AI-handled and person-handled.
3. Median time from handoff to first human message.
4. Conversion (booked or lead captured) by time-to-first-reply bucket.

The fourth report is the one that tells you whether speed is worth anything for your business. Usually it is, sharply.

The number that surprises people

Time to human. Businesses that have automated the first reply often find the handoffs sit for hours because nobody owns the queue. The AI made the first minute perfect and the process made the next hour worse than before. Assign the queue to a person, per location, and put the number on the wall.

Frequently asked questions

Is under one minute realistic for a small business?

For the first reply, yes, with automation. Without it, no; a person cannot be at every channel at every hour.

What about leads that arrive at 3am?

Reply at 3am, once, honestly (closed, when you reopen, what can be done now), and book if they want to. Follow-ups wait for the morning.

Should I publish my response time?

If it is good and measured, yes. "We reply within a minute, any hour" is a claim customers test immediately, so be sure.

What Frontiva does here

Frontiva's AI replies on SMS and web chat as soon as a message arrives when its agent is set to autonomous, and analytics report median first response against the previous period, filterable by location. Handoff-to-human and resolution times are not reported yet. For the research behind response time, see speed to lead statistics.