Response SLA for Cold Email: Targets and Tracking (2026)
On this page
Why trust this guide?
This guide is written by the Master Inbox team and reviewed by our founder, Abdul Mukati. We build reply management software for outbound teams and agencies, so response targets and missed replies are part of our daily work. Master Inbox is one of the tools mentioned, and we mark where it fits. The targets below are our recommendations based on how teams commonly tier their replies, and they are labeled as recommendations because the right numbers depend on your market, your offer and your staffing. We do not quote industry statistics. Instead we show how to measure your own baseline, which is the number that matters.
What a response SLA is for outbound replies
SLA stands for service level agreement. In support teams it is a promise to a customer. In outbound it is usually an internal promise: the maximum time between a reply landing and the first useful answer. It is a measurable standard that holds people and systems accountable for speed.
It matters because interest fades. A prospect who replied with a question is thinking about your message now. Hours or days later, they may have moved on to something else. A written target turns the vague aim of replying quickly into a number that a manager can check and a rep can plan around.
A good SLA has five parts:
- A trigger. The moment the clock starts, which is when the reply lands in your queue.
- A stop. The moment the clock stops, usually the first human or approved automated answer that moves the conversation forward.
- A target. The time allowed, by reply type.
- A calendar. Working hours, time zones and holidays.
- A consequence. An alert, an escalation or a review when a reply is about to miss.
The SLA belongs to the wider reply workflow described in the cold email reply management guide. It is the measure for Step 5 of that loop, and it depends on having every reply in one place, which the unified inbox guide covers. If replies are going missing, the clock cannot start, so fix capture first. See missed replies.
How to choose a target by reply type
One target for every reply wastes effort. An out-of-office message does not need a human at all, and an interested reply needs one quickly. The first step is reply labeling, so each reply has a type. Then set a target per type.
The table below is a recommendation to start from. It is not a statistic, and it is not a benchmark from any study. Adjust it to your own baseline and capacity. If you cannot meet a target today, set it at a level you can meet, then tighten it as you improve.
| Reply type | Suggested target (recommendation) | Why |
|---|---|---|
| Interested or meeting request | Within 15 minutes in working hours | The prospect is at peak interest, and the meeting is the goal of the whole campaign |
| Question about price or scope | Within 1 hour in working hours | A buying signal, and a clear answer often leads straight to a booking |
| Referral | Within 2 hours in working hours | Contact the named person while the referrer still remembers the thread |
| Wrong person | Within 1 working day | Useful, but not urgent: you need the right contact and a polite thank you |
| Not now | Within 1 working day | Confirm the timing and set a follow-up date |
| Already using a tool | Within 1 working day | A short note and a reminder to revisit later |
| Not interested | Within 2 working days, or no reply | A polite close is optional, and the lead should be marked closed |
| Unsubscribe | Immediately by automation | Suppression should not wait for a person |
| Out of office | No answer needed | Reschedule the touch for the return date |
| Auto-reply or bounce | No answer needed | Check the address and clean the list |
Three points on using the table:
- Start with fewer tiers. A team new to SLAs can use three: hot, warm and none. Add detail later.
- Tie the target to the label. If AI labeling or a rep changes the label, the target changes with it. See AI labeling and intent classification.
- Write the target where people see it. A target that lives in a document nobody opens will not change behavior. Put it in the view the team works from.
Business hours and time zones
The clock is the part of an SLA that teams skip and then argue about. Decide it before you set a number.
Working hours or all hours
Most teams count working hours only, because a reply that lands at midnight cannot be answered by someone asleep. If you run a follow-the-sun team or an autonomous reply agent, you may count all hours for some labels. Choose per label, and write it down.
Whose time zone
You have three options: the rep's time zone, the prospect's time zone, or one company time zone. A single company time zone is the easiest to report on. The prospect's time zone is the best for the experience, because a prospect in a different region will expect an answer during their day. Many teams use the rep's calendar for the clock and add coverage rules so a reply is routed to someone who is working.
Weekends and holidays
Decide whether the clock pauses at weekends and public holidays, and whose calendar defines a holiday. For global teams, give each rep their own calendar.
Coverage
Name a backup for every rep. When a rep is out, lead routing should send their replies to the backup automatically, so the SLA does not depend on one person's holiday plan. For fast handling of hot replies, see speed to lead.
How to track it
An SLA you cannot see is a hope. Tracking needs three things: a view of what is waiting, a named owner for each reply, and a rule for what happens when time runs out.
A needs-reply view
Create one view that lists every reply waiting for an answer, sorted by time remaining against its target. It should include the label, the owner, the client or campaign and how long the reply has been waiting. This is the screen the team works from. In Master Inbox this is the Needs Reply view. You can build the same thing in a spreadsheet, but it will need manual updates.
Ownership
Every reply needs one owner, not a team. Shared responsibility means nobody picks it up. Assign by rule: the owner of the campaign, the account or the client, with a backup for absence. Ownership should be visible in the queue so anyone can see who holds a reply and whether it is on time.
Escalation
Escalation is what turns a target into a standard. A simple ladder works:
- When a reply is halfway to its target, nudge the owner with an alert.
- When it reaches the target, alert the owner and the team lead.
- When it passes the target, reassign to the backup and note the miss.
Alerts work best where the team already looks. Many teams use Slack. In Master Inbox, workflows trigger Slack cards by label, with an approve button, so a hot reply reaches the right channel at once. See the Slack integration.
Close the loop
The clock stops on the first useful answer, so decide what counts. A one-line holding reply that promises a proper answer later usually should not stop the clock for a hot reply. A reply that proposes a time or answers the question does. Agree on it, and write it down.
Reporting by rep and by client
Tracking tells you what is late today. Reporting tells you what to change. Review a small set of numbers on a fixed day each week.
- Percentage of replies answered within target, by label. This is the headline SLA number. Compute it for your own data, and use it to see your trend over time.
- Median and slowest time to first answer, by label. The median shows normal behavior, and the slowest cases show where the process breaks.
- Missed replies, meaning replies with no answer past the target, listed by name so someone can act.
- Reply coverage, meaning the share of replies captured in the central queue and handled.
- Volume by label, so you can see whether a slow week was caused by a spike.
By rep
Per-rep reporting shows who is overloaded and who has capacity. Use it to rebalance routing, not to punish. If one person misses more targets than others, check their volume, their calendar and their label mix before drawing conclusions. A rep who gets all the interested replies will have the hardest targets.
By client
For agencies, per-client reporting is how you show that replies get handled. It also exposes differences between clients, since some clients have a short sales cycle and want faster answers. Per-client targets let you set service levels in the client agreement and report against them. Master Inbox client reporting works without a client login, and client workspaces keep each client's data separate. More on the built-in reports is on the reporting page.
By channel
Split email from LinkedIn if you use both. A LinkedIn reply often arrives in a tool that people check less often, so it may have a slower time to answer without anyone noticing. A unified view with LinkedIn Inbox brings the two together.
A worked example
All numbers below are made up for illustration. They are round numbers chosen to make the arithmetic easy, and they are not results from any real team.
Example setup. A team of three reps handles replies from a campaign. In one week, 200 replies arrive. Labels split them like this:
| Label (example) | Replies (example) | Target (example) | Answered on time (example) | On-time share (example) |
|---|---|---|---|---|
| Interested or meeting request | 20 | 15 minutes | 15 | 75% |
| Question | 20 | 1 hour | 18 | 90% |
| Referral or wrong person | 20 | 1 working day | 20 | 100% |
| Not now or not interested | 40 | 2 working days | 36 | 90% |
| Out of office, auto-reply, bounce | 100 | None | Not counted | Not counted |
Reading it. 100 of the 200 replies need an answer, and 89 of those were answered on time. That is 89% overall in this example. Looking only at the headline would hide the real issue: the label with the tightest target has the lowest on-time share, at 75%. Five interested replies were late.
Finding the cause. Suppose the missed ones all arrived outside the main rep's working hours. The fix is a coverage rule, not more effort. Route interested replies to whoever is on shift, and send a Slack card to the team channel. After the change, the next week's example result might be 18 of 20 on time. That would be 90% for the label, with the same team.
What to do with it. Compare the two weeks, note the change in routing, and decide whether to tighten the 15 minute target. Keep the example as a template for your own review: counts by label, on-time share by label, the cause of each miss and one change to try.
Where Master Inbox fits
Master Inbox is built so the SLA can be tracked from the moment a reply lands. It captures every email and LinkedIn reply from your sequencers and LinkedIn tools in one inbox, labels each one by intent, and measures the time to answer.
- SLA tracking on every reply. Each reply carries a clock, so you can report time to first answer by label, rep and client.
- Needs Reply views. A working queue of replies waiting for an answer, sorted by how long they have waited, with filters for label, owner, client and channel.
- Slack cards. Label-triggered cards with an approve button put hot replies in front of the team the moment they land.
- Reply coverage and missed replies. Reports show what was captured and what is still waiting.
- Team performance by channel and label, plus client reporting that works without a login.
- Unlimited users on every plan, so every rep, closer and client manager can see the queue.
- Reply Agents that answer, follow up and book meetings on your real calendar, human-in-the-loop first and autonomous when you are ready. See Reply Agents.
Master Inbox works alongside your sequencer, CRM and support desk. Plans are priced on connected mailboxes and client workspaces, never per seat: Reply Agent from $499 a month, Agency at $599 and Team at $799. Every plan starts with a free 7-day POC, and onboarding is done with you. Teams that use a seat-based support desk can compare the models in our Front pricing guide. Read the outbound teams page or take the product tour.
Frequently asked questions
What is a response SLA in cold email?
It is the longest time your team commits to taking to give a first answer to a reply. Teams usually set it per reply type, with the tightest target for interested replies.
What response time should I target?
There is no single right number. Measure your baseline by label for a few weeks, then set targets you can meet and tighten them over time. Our table offers a starting recommendation, not a benchmark.
Should the SLA count working hours or all hours?
Most teams count working hours and use coverage rules so a reply is routed to someone who is working. Count all hours only for labels handled by automation or a follow-the-sun team.
Do all replies need an SLA?
No. Out-of-office messages, auto-replies and bounces need no answer, and unsubscribes should be handled by automation. Focus your SLA on replies where a person adds value.
How do I track an SLA?
Use a needs-reply view sorted by time waiting, assign one owner per reply, and set escalation alerts. Then review the on-time share by label, rep and client each week.
What should happen when a reply misses the target?
Alert the owner first, then the team lead, then reassign to a backup. Log the miss and its cause so you can fix the process and not only the reply.
Can an agency report SLA to clients?
Yes. Keep each client in its own workspace and report on-time share and missed replies per client. Master Inbox client reporting works without a client login.
Does an SLA help if replies are already being missed?
Fix capture first. If replies never reach your queue, the clock cannot start. Reading the mailboxes themselves, as a unified inbox does, brings forwards, CC replies and new-address replies into the count.
Turn the target into a habit
Pick three reply types, set a target for each, build one needs-reply view and review misses every week. That is enough to start, and you can add detail as you learn. If you want the clock, the view and the Slack alerts ready to use, Start your free 7-day POC and we will set it up with you. Front is a trademark of its owner. Master Inbox is an independent product and is not affiliated with Front.