Response SLA

Why it matters for outbound teams

Speed to respond correlates strongly with whether a prospect who replied positively actually converts into a booked meeting, since interest fades fast once a prospect moves on to something else. A response SLA turns that urgency into an enforceable standard rather than a vague goal. Teams typically tighten the SLA for positive replies and relax it for neutral or informational ones.

How to set a response SLA

A response SLA has three parts: which replies it covers, how long you have, and what counts as a response. Be specific about each one.

• Scope. Tie targets to labels, not to every reply. Interested and meeting-request replies get the tightest target. Questions and referrals get a looser one. Out-of-office and unsubscribe messages need no human response at all.
• Clock. Decide whether the timer runs around the clock or only in working hours, and in whose time zone. Many teams use the rep's working hours and add an after-hours auto-reply or an AI reply for the gap.
• Definition of a response. A real reply from a person, or an approved automated answer. An internal note does not count.

Then add an escalation step. If the target time passes, the reply moves to a manager or a backup rep. Without escalation, an SLA is only a wish. For the full process, read the response SLA guide.

How to measure it

Measure time to first response for each reply, from the moment it arrives to the moment your team answers. Report it as a median and as the slowest few, because averages hide the replies that waited too long. Split the numbers by label, by rep and by client, so you can see where the delays are.

Two companion numbers are worth watching. Reply coverage is the share of replies that got any answer. Missed replies are replies still waiting past the target. Master Inbox tracks SLA on every reply and shows reply coverage, missed replies and team performance by channel and label in reporting, and agencies can share client reporting without giving the client a login.

A worked example

This is an illustrative example with round numbers, not measured data. A team sets three targets: interested replies within 15 minutes during working hours, questions within 4 hours, and referrals within 1 working day. In one week, 30 replies are labeled interested. Twenty-seven get an answer inside 15 minutes. Three wait longer because the owning rep was in a meeting.

The report shows three misses, all from the same rep on the same afternoon. The manager adds a backup owner for those hours and sets an escalation after 15 minutes. The next week there are no misses. The SLA did not make the team work harder. It made the gap visible, so it could be fixed.

Common mistakes

• One target for everything. A single number is too tight for neutral replies and too loose for interested ones.
• Setting a target nobody can see. Reps need a visible timer or alert, not a policy document. A Slack card in the channel works well, which is what workflows can post when a label lands.
• Ignoring weekends and time zones. A prospect in another time zone replies at their working hours, not yours. Cover the gap with Reply Agents or a rota.
• Counting auto-replies. Exclude out-of-office and bounce messages from SLA math, or the numbers look better than reality. This depends on good reply labeling.

Frequently asked questions

What is a good response time for a cold email reply?

There is no single correct number. Most teams aim for minutes to an hour on interested replies during working hours, and a few hours to a day on questions and referrals. Set targets by label and check them against how fast your prospects actually move.

What should a response SLA cover?

It should cover the replies that need a human answer, mostly interested, meeting-request and question labels. Out-of-office messages, bounces and unsubscribes should be excluded, since they need a system action rather than a written response.

How do I enforce a response SLA?

Make the timer visible, alert the owner before it expires, and escalate to a backup when it does. Report misses weekly by rep and by label so the pattern is clear and the team can fix the cause, not just the symptom.

Can automation help meet a response SLA?

Yes. Automation can alert the owner the moment a label lands, assign the reply, and send an approved first answer outside working hours. Keep a person in the loop for complex replies, and review automated answers regularly.

← All glossary terms