Reply response time

Start with response time as a routing decision. Set the target by reply type, assign ownership, and measure from a defined starting event to a defined first response. One team-wide promise hides the work. High-intent replies need a tighter window, while lower-intent replies can follow a same-day rule. For mid-market teams, one published target is a median of at most 15 minutes for high-intent replies, same-day response for lower-intent leads, and a P75 of at most 45 minutes.¹

Set the clock

When the reply became

Which lead type it

Which channel carried it

Who owns the next

What counts as the

• When the reply became
• Which lead type it
• Which channel carried it
• Who owns the next
• What counts as the

Choose the start event, stop event, working-hours rule, and owner before setting a target. If those definitions change between channels or regions, the reported speed changes with them.

Define the working day by region and decide whether to report both raw and business-hours-adjusted response times.² If coverage cannot support 24-hour support, publish the response expectation the team can meet.³ Set the target by lead type before the reply arrives, so the person handling it can act without negotiating the standard each time.

Follow-up emails increased after nonresponses, which drove emphasis on timely replies.⁴ Use that pressure to write a rule someone can apply at the inbox, not a promise that exists only in a dashboard.

Write these fields into the handoff or routing record:

• when the reply became visible
• which lead type it belongs to
• which channel carried it
• who owns the next response
• what counts as the first response
• when the clock pauses, if it ever does

Triage the reply

1

Which lead type

2

Which channel carried

3

What target applies

4

Who owns the next

5

Does the reply need

1. Which lead type
2. Which channel carried
3. What target applies
4. Who owns the next
5. Does the reply need

With the clock defined, sort each reply quickly enough to make urgency and ownership clear before drafting begins. The goal is a usable decision, not a long classification exercise.

Ask these questions in order:

• Which lead type is this?
• Which channel carried it?
• What target applies?
• Who owns the next response?
• Does the reply need an acknowledgment now, or can the full answer go out within the target?

Track response time by tier to see whether each service-level window is being met.⁵ Keep high-intent replies from waiting behind lower-intent work. Apply the target already attached to the lead type, then move on when the owner and deadline are visible. If either is missing, resolve that gap before writing the message.

Acknowledge before solving

Acknowledgment

What was received

Who will act

Response will arrive

Parts of acknowledgment:

• What was received
• Who will act
• Response will arrive

The first message can keep the thread moving when the full answer needs more time. Make the acknowledgment useful by confirming that the reply was seen, saying what happens next, and giving the sender a reliable time.

Mailbox staff should review all received emails daily and issue the appropriate response within the established timeframe.⁶ When time is limited, a one-line text or email response is sufficient.⁷ Use a specific commitment for the next response. Examples include "within 24 hours" and "within 2 business days".⁸

Promise acknowledgment when that is all you can promise, rather than promising a complete answer. A short message sets the next expectation and gives the owner room to finish the work without leaving the sender to guess.

A good acknowledgment answers three things: what was received, who will act, and when the next response will arrive. If the reply contains a direct request you can answer immediately, answer it and record the response time at once. If it needs another person, keep the original owner visible until the handoff is accepted.

Measure the path

A useful report shows where response time is lost and which rule produced the delay. Keep the event definitions stable, then inspect the result where someone can change the work.

For a lead-response view, calculate the total time between lead creation and first response for all assigned leads, divided by the number of leads the team responded to.⁹ For a reply-response view, use the received-reply event as the starting point while keeping the same first-response discipline.

Use CRM reports to track response time, with extra attention to time-based signals.¹⁰ If a reply passes through several owners, keep a separate full-path view. End-to-End Responding Latency is a metric for response latency.¹¹ That view shows whether the delay happened before assignment, during handoff, or after ownership was accepted.

Review the report after the response window has elapsed, then inspect the individual records behind the result. A missed target needs a cause you can act on: unclear routing, unavailable coverage, a missing owner, or a reply that entered the wrong tier. Keep the diagnosis tied to the event trail instead of changing the target to make the result look better.

What not to do

Most response-time failures come from rules that are too broad to run at the inbox. Keep these out of the operating standard.

• Set the response target by lead type.¹²
• In sales-rep onboarding, set response-time SLAs for different communication channels.¹³
• Monitor response time by representative and routing rule.¹⁴

Before the next block of replies, write the start event, stop event, owner, lead type, channel, and target in one place. Then review misses by tier and routing path, change coverage where the clock is failing, and keep the promise visible to whoever answers.