Lead response time: how fast to reply, and a standard your team can actually keep

Ask any sales manager how fast your team should respond to a new lead and you’ll hear “as fast as possible.” That’s true and not very useful. “As fast as possible” isn’t a standard anyone can be held to, it doesn’t say what happens at 9 PM on a Saturday, and it treats an automated “Thanks, we got your message!” the same as an answer to the customer’s question.

This article skips the scary statistics and works from the situation itself: who is messaging you, what they’re doing while they wait, and what a small team can realistically promise.

Why response time matters for messaged leads

Think about what a person is doing when they text a business.

A homeowner with a leaking water heater searches, finds three plumbers, and messages all three from the search results. A parent looking at language classes for a child sends the same question to two schools on Instagram. Someone who needs an immigration consultation fills out a form on four law firm websites in one evening.

In each case, the person is actively shopping right now. They’ve already done the hard part of deciding they need help. The first business that replies with something useful gets a conversation; the others get compared against a business that’s already talking to them.

Messaging makes this sharper than email or forms, for a few reasons:

• Chat feels live. People expect a chat to be answered more like a conversation than like a letter.
• Switching costs are low. Messaging the next business takes a few seconds.
• The intent fades. The water heater gets fixed, the child gets enrolled somewhere, the person books a consultation. A reply tomorrow can be a reply to someone who no longer needs you.

You don’t need a study to see this. Look at your own last ten lost leads and ask how long each one waited for a useful first reply. The concept has a name, speed to lead, and it’s mostly common sense applied consistently.

First response vs. useful response

Before you set a target, separate two things that often get blurred.

First response is the first message from your business after the lead reaches out. An automated acknowledgment counts here, technically.

Useful response is the first message that moves the customer forward: answers their question, asks the right qualifying question, or proposes a next step.

Compare these two replies to “Hi, do you do bathroom-only remodels in Oak Park?”:

Thanks for reaching out! A member of our team will be in touch soon.

Hi! Yes, we do bathroom-only remodels and Oak Park is in our area. Is this a full gut or more of an update (fixtures, tile, vanity)? And roughly when are you hoping to start? — Priya

The first is a response. The second is a useful response. An auto-acknowledgment can be a reasonable bridge, especially after hours, but don’t let it hide the real number. If you measure only first response time, an auto-reply makes you look instant while customers still wait hours for an actual answer.

A good standard sets a target for the useful response, and treats the automatic acknowledgment as optional.

Setting a standard your team can actually keep

A response-time standard is a promise to your customers and a rule for your team. It only helps if it’s met most of the time. A too-ambitious target that’s missed every afternoon teaches the team to ignore it.

Step 1: Look at your real coverage

Write down, honestly, who can reply to new leads and when:

This table is usually more revealing than any target. Gaps you didn’t know about show up quickly, like the lunch hour when everyone is out on site visits.

Step 2: Set separate targets for business hours and after-hours

One number for all hours doesn’t work for a small team. Set two.

Business-hours target. For most small teams selling in chat, a useful reply within a short window during staffed hours is achievable. A reasonable starting point is something like “within 15 minutes” or “within 30 minutes,” adjusted after a few weeks of real data. Pick a number you can hit on a normal busy day, not on a quiet one.

After-hours target. Be specific about what happens outside staffed hours. For example:

• An acknowledgment that sets expectations, sent immediately.
• A useful reply by a fixed time the next business morning, such as “by 9:30 AM.”

Here’s an after-hours acknowledgment that’s honest and still helpful:

Thanks for messaging Westside Remodeling. We’re out of the office until 8 AM tomorrow, and Priya will reply first thing. If you can share a couple of photos of the space and your zip code, we’ll come back with next steps.

That message sets a time, names a person, and asks for something useful, so the morning reply can be useful too.

Step 3: Define who is on point

A standard without an owner is a wish. For every time block, someone should be explicitly responsible for new leads. On small teams this is often a rotation: “Today Marcus is on new leads.” New conversations go to that person, or get assigned in rotation across the team if volume is higher.

The person on point doesn’t have to close every lead. Their job is the useful first reply and a clean handoff if someone else should take it.

Step 4: Write it down in one paragraph

Here’s a sample standard a five-person service team might adopt:

Lead response standard. During business hours (Mon–Fri 8 AM–6 PM, Sat 9 AM–1 PM), new leads get a useful reply within 30 minutes. The person on new leads that day owns the first reply. Outside business hours, an automatic acknowledgment goes out and the lead gets a useful reply by 9:30 AM the next business day. If you’re going to miss the target, tell the person on point so they can cover.

Short enough to remember, specific enough to check.

Measuring it honestly

You can’t improve what nobody looks at. You also don’t need a dashboard on day one.

What to measure

• Time to useful first reply, in business hours. This is the core number.
• Leads still waiting for a first reply right now, and for how long. This is the operational number: it tells you what to do in the next ten minutes.
• After-hours leads answered by the morning target. A simple yes/no count is enough.

How to measure without software

If you don’t have a tool that tracks this, sample it. Once a week, take the last 20 new leads and note when each one arrived and when the first useful reply went out. Fifteen minutes with a spreadsheet will tell you more than a month of guessing.

Common measurement traps

• Counting auto-replies. Exclude them, or track them separately.
• Measuring in clock hours. A lead that arrived at 11 PM and was answered at 8:15 AM wasn’t “9 hours late.” Measure against your after-hours promise instead.
• Averages that hide the long tail. One day of 2-minute replies doesn’t cancel out a lead that waited two days. Look at how many leads missed the target, not just the average.
• Only measuring new leads. Existing customers waiting on a reply matter too, especially mid-deal. Track them separately so they don’t get crowded out.

For a broader set of numbers worth watching, see sales productivity metrics for messaging teams.

Practical scenarios

The lunchtime gap. Everyone is out on site visits from 12 to 2. Fix: one person checks new leads at 12:30 and 1:30 from their phone, or the office manager staggers lunch.

The specialist question. A lead asks something only the owner can answer, like a pricing exception. Fix: the person on point replies usefully anyway (“Great question — I’m checking with Dan, who handles custom work, and will get back to you by 3 PM”) and adds an internal note for Dan. The clock is about the customer waiting without information, not about who has the answer.

The Monday pile. Twenty leads arrived over the weekend. Fix: reply in order of arrival, but with a short, useful message to all of them by 10 AM, then go deeper one by one.

The WhatsApp window. On WhatsApp, a free-form reply is only possible within 24 hours of the customer’s last message; after that, the business needs an approved template to restart. A next-morning reply is usually fine. A reply two days later is harder. Our post on running WhatsApp sales as a team covers this.

Making the standard stick

• Review missed targets weekly, as a team, without blame. Ask what got in the way.
• Adjust the target if it’s missed most days. A kept promise of 30 minutes beats a broken promise of 5.
• Use reminders that fire when a conversation has waited too long, rather than relying on people to notice.
• Make “who’s on new leads today” visible to everyone.

Where inChat fits

inChat is a conversation-first CRM in development. Response timers and “no reply in X hours” reminders are part of its planned launch scope, so a team can see which conversations are waiting and who owns them. It’s in early access; the lead response use case and planned analytics show how it’s designed to work.