Designing SLA Tiers, Business Hours and a 4-Level Escalation Matrix
How to turn a support promise into something the system enforces, not something an agent has to remember.
9 min readService CRMSLAEscalation
- Four SLA tiers, response and resolution
- The clock stops when the office does
- Four escalation levels triggered by the SLA, not by memory
Why one SLA is never enough
- A single response target treats a payment failure the same as a general question — one is over-served, the other under-served
- Tiers let you promise faster response where it matters (billing, outages, safety) without over-committing everywhere
- QuipCRM Service ships with four tiers by default; most desks land on three to five once their categories are mapped
Assigning a tier without a meeting for every category
- Start from category and severity, not from the requester — the same customer can raise both a critical and a routine ticket
- Set response and resolution targets separately: a fast acknowledgement matters even when the fix takes longer
- Review tier assignment quarterly against actual breach data rather than gut feeling at launch
Business hours: the setting that saves your SLA compliance number
- Without a business-hours setting, every overnight or weekend ticket silently breaches by morning
- Configure business hours once per desk (or per region, if you operate across time zones) and every SLA clock reads from it
- A ticket raised outside business hours should start its clock at the next opening, not at midnight
Building the four-level escalation matrix
- Level 1: Team Lead — reassignment and capacity, triggered as the SLA approaches breach
- Level 2–3: escalate by role, not by name, so the matrix survives staff changes
- Level 4: the point at which leadership visibility, not just faster handling, is what is needed
- Escalation should notify, not silently reassign — the notification matrix is what closes the loop
What to measure once it is live
| Metric | What it tells you |
|---|---|
| SLA compliance by tier | Whether the tiers you set are actually achievable |
| Escalation rate by level | Where the matrix is doing real work vs. never firing |
| Breach reason (category) | Which categories need a tier change, not just more agents |
A rollout order that avoids a big-bang cutover
- Phase 1: categories, the ticket record, queues and roles
- Phase 2: SLA tiers, the escalation matrix, business hours and the notification matrix
- Phase 3: routing strategies and self-service intake, once the governance layer is stable
Relevant Modules
Best paired with: Service CRM.