SLA (Service Level Agreement)
An SLA (Service Level Agreement) is the commitment your business makes about how fast it will respond to and resolve customer conversations. In a WhatsApp support inbox it becomes a concrete, measurable target — for example, "first reply within 5 minutes, resolution within 4 working hours" — that the platform tracks against every incoming chat. On WhatsApp, SLAs carry extra weight because there is a hard 24-hour service window: reply late and you can no longer send a free-form message, forcing you into a paid template just to reopen the conversation. A well-designed SLA keeps agents accountable, keeps customers happy, and quietly protects your messaging budget.
In one line
An SLA is your promised response and resolution time for support conversations. On WhatsApp it matters doubly because the free 24-hour service window closes if you reply too slowly, pushing you into paid templates to re-open the chat.What an SLA actually measures
An SLA turns a vague promise like "we reply quickly" into a number the inbox can measure and report on. Most WhatsApp support teams track two distinct clocks. The first-response SLA measures how long a customer waits for a human (or bot) to acknowledge their message after it lands in the queue. The resolution SLA measures how long the whole conversation takes to close, from the customer's first message to the moment their issue is genuinely fixed. These are different targets for a reason: acknowledging a customer in 60 seconds is easy and hugely reassuring, while fully resolving a refund or a shipping dispute might legitimately take hours. Splitting them lets you set an ambitious first-response goal without punishing agents for complex cases that take real time to solve.
- First-response SLA: time until the first reply reaches the customer
- Resolution SLA: time until the conversation is closed as resolved
- Often tiered by priority — VIP or paid customers get tighter targets
- Usually measured only during business hours, pausing overnight and on holidays
Why SLAs matter more on WhatsApp than on email
On email or a web helpdesk, a slow reply is simply a slow reply. On the WhatsApp Business API it is also a billing event waiting to happen. When a customer messages you, a free 24-hour service window opens during which your agents can send any free-form reply at no messaging charge. Miss that window — because a ticket sat unanswered overnight or slipped through the queue — and the window closes. To restart the conversation you now have to send a pre-approved template, which is a delivered message you pay for. A sloppy SLA therefore does not just annoy customers; it quietly converts free service replies into paid utility or marketing template sends. Teams that hold a tight first-response SLA answer while the free window is still open, keep customers inside a single continuous thread, and spend nothing extra to do it.
How SLA tracking works in a shared inbox
In a shared team inbox, the SLA clock starts the instant a customer message arrives and is assigned to a queue. As agents pick up, reply, snooze, or escalate the conversation, the inbox timestamps each event and compares it against your configured targets. Conversations approaching their deadline are flagged — often colour-coded or floated to the top of the queue — so supervisors can reassign work before a breach happens. When a target is missed, the conversation is marked as breached and logged for reporting. Good tooling also respects your business hours and holiday calendar so the clock pauses when your team is legitimately offline, rather than penalising agents for the hours nobody was rostered to work.
- Clock starts on message arrival, not when an agent opens the chat
- Auto-assignment routes chats fast so the SLA timer doesn't burn in an unassigned queue
- At-risk conversations surface visually before they breach
- Breaches are logged for coaching, staffing, and trend analysis
Setting SLA targets that your team can actually hit
The most common SLA mistake is copying an aspirational number from a competitor's website instead of grounding the target in your own staffing and volume. Start from reality: look at your current median first-response and resolution times, then set a target slightly tighter to create healthy pressure without guaranteeing daily breaches. Segment by priority so a routine "what are your hours" question and an angry payment failure aren't held to the same clock. Crucially, define your business hours honestly — a promise of "5-minute replies" means nothing at 2am if no one is staffed, and an all-hours SLA you cannot meet just manufactures breaches. Finally, revisit the numbers every quarter as volume grows and headcount changes; an SLA is a living commitment, not a plaque on the wall.
Common SLA mistakes to avoid
Several pitfalls quietly undermine SLA programmes. The biggest is confusing response with resolution — a team that fires off a fast acknowledgement and then leaves the issue unsolved looks great on the first-response metric while customers seethe. Another is ignoring the WhatsApp service window entirely, so overnight questions expire and get answered with a paid template the next morning, inflating cost with no one noticing. Teams also forget to route conversations automatically, letting chats rot in an unassigned queue while the clock runs. And many track SLAs but never act on breach data, so the same understaffed evening shift breaches every week without anyone adjusting the roster. An SLA is only useful if the numbers change how you staff, route, and coach.
- Measuring only first response and ignoring resolution
- Setting 24/7 targets a business-hours team can't meet
- Letting the free 24-hour window lapse into paid templates
- Collecting breach data but never changing staffing or routing