Response time targets for a shared inbox
Targets a small team can actually hold: first reply, human reply after handoff, and resolution, by channel and by hour, and how to report them without turning the inbox into a stopwatch.
Frontiva · · 3 min read
A shared inbox needs three targets: time to first reply (under a minute, any hour, which the AI delivers), time to a human reply after a handoff (under ten minutes during business hours, first thing in the morning otherwise), and time to resolution (same day for anything that can be resolved by the front desk). Report them by channel and by person weekly, and put the worst-waiting conversations at the top of the inbox every hour. Targets that are not visible in the inbox are not targets.
The three clocks
First reply. From the customer's message to the first useful reply. Automation makes this a near-constant; without automation it is whatever the busiest hour makes it.
Human reply after handoff. From the moment the AI or a rule hands off, to the first message from a person. This is the number that a shared inbox exists to control, and the one most teams have never measured.
Resolution. From the first message to the conversation being closed with the customer's need met. Bookings resolve in minutes; a billing dispute may take a day. Set the target per type.
Targets by hour
During business hours: first reply under a minute, human reply under ten minutes, resolution same day.
After hours: first reply under a minute (automated, honest about being closed), human reply by 9am, resolution next business day. The after-hours first reply tells the customer when to expect the human one, so the target is a promise you made.
Targets by channel
The same for all. A customer on Instagram is not less important than one on SMS, and the AI answers all channels equally. Where teams differ is in habit: the channel nobody has on their screen is the one that waits. A unified inbox removes the difference; the report shows whether it has.
Reporting without a stopwatch culture
Report medians and the share over target, by person and by queue, weekly. Do not report individual conversations to individuals as a league table; that produces people closing conversations to hit numbers. Do show, in the inbox, the conversations waiting longest, so the team can fix the waiting rather than argue about the average.
The number that usually surprises
Handoff to human reply. Teams that have automated the first reply often find handoffs sit for an hour because the queue has no owner or the owner is busy with walk-ins. The first reply looked great and the customer still waited. Assignment fixes this; measurement finds it.
When targets are missed
Look at the hour, not the person. Missed targets cluster at the same times every week: the 8am rush, the lunch hour, the last hour of the day. The fix is coverage or rules (let the AI handle more categories at those hours), not a reminder to reply faster.
Frequently asked questions
Is under a minute realistic for the first reply?
With an AI that answers from approved knowledge, yes, and it is the normal case. Without one, no team holds it.
Should the customer see the target?
You can publish "we reply within minutes" if it is true. Do not publish a target you do not measure.
What about a conversation waiting on the customer?
The clock stops when the last message is yours. Report waiting-on-customer separately; those are follow-up candidates, not response failures.
What Frontiva does here
Frontiva's analytics report median first response against the previous period, filterable by location, and the unified inbox sorts conversations by real activity so the ones that need an answer rise to the top. Resolution time and per-person reports are not built yet. See lead response time for the lead-specific version.