# Customer Service Escalation Template

Define exactly what escalates, to whom, how fast, and what the agent says while it happens.

Provided free by VoiceSupportCrew.

---

**Owner:** ____________________
**Last reviewed:** ____________________

---

## 1. Escalation triggers

Design triggers first, tiers second. List what genuinely needs someone more senior, then build the structure that handles it.

### Authority triggers
The resolution exceeds what the agent may approve.

- [ ] Refund above $______
- [ ] Discount above ______%
- [ ] Goodwill gesture above $______
- [ ] Contract or pricing change
- [ ] ____________________

### Knowledge triggers
The answer is not documented and cannot be found.

- [ ] Question with no documented answer
- [ ] Conflicting information in the documentation
- [ ] Product behaviour that appears to be a fault
- [ ] ____________________

### Risk triggers
These are the ones that must never sit in a queue.

- [ ] Legal action mentioned or threatened
- [ ] Regulator, ombudsman or trading standards mentioned
- [ ] Press or media contact
- [ ] Safety issue — specify what counts: ____________________
- [ ] Suspected data breach or unauthorised account access
- [ ] Serious allegation about staff conduct
- [ ] Suspected fraud
- [ ] Vulnerable customer indicators — specify: ____________________

### Emotion triggers
- [ ] Customer explicitly asks for a manager
- [ ] Customer has contacted us ______ times about the same issue
- [ ] Conversation has deteriorated past recovery
- [ ] Public complaint (review, social media) referenced

### Time triggers
The failure mode most processes miss.

- [ ] Unresolved after ______ hours / days
- [ ] More than ______ contacts without resolution
- [ ] Promised callback missed
- [ ] Awaiting internal input for more than ______

---

## 2. Tiers

Small teams need two tiers, occasionally three. More adds handoffs without adding capability.

| Tier | Handles | Owner (named person) | Backup | Contact method | Acknowledge within |
|---|---|---|---|---|---|
| 1 | Documented contacts within authority limits | Agent | — | — | — |
| 2 | Authority exceptions, undocumented questions, unhappy customers | | | | |
| 3 | Legal, regulatory, safety, security, media | | | | |

**Tier 3 must be a named person, not a department.** "The management team" is not an owner.

### Out-of-hours routing
> Which triggers justify contact outside working hours: ____________________
> Method: ____________________
> Named contact: ____________________ Backup: ____________________

---

## 3. Response commitments

An escalation without a response commitment is just a queue. Set targets for acknowledgement as well as resolution — most escalation anger comes from silence, not delay.

| Tier | Acknowledge | Customer update cadence | Target resolution |
|---|---|---|---|
| 2 | | | |
| 3 — risk triggers | Immediately, by phone | | |
| 3 — other | | | |

> **The silence rule:** a customer updated daily about an unresolved problem is usually calmer than one whose problem was fixed in three days with no contact in between.

---

## 4. What the agent says

The handover moment is where escalations go wrong. Approve wording for all three.

### Telling the customer it is escalating
> "____________________"

Include: what will happen, who will do it, by when. Avoid "I'll pass this to my manager" — it sounds like the end of your involvement.

### Setting the expectation
> "____________________"

### If the customer pushes for an immediate answer
> "____________________"

### If the customer is angry
> "____________________"

---

## 5. Escalation log

| Date | Ref | Customer | Trigger category | Tier | Raised by | Owner | Acknowledged | Resolved | Root cause |
|---|---|---|---|---|---|---|---|---|---|
| | | | | | | | | | |

---

## 6. Closing the loop

Every escalation should produce one of two outcomes:

1. **A documented answer** that prevents the next one, or
2. **A confirmed decision** that this genuinely needs a human every time

Escalations that produce neither are a leak — the same question arrives again next week.

### After each escalation
- [ ] Root cause recorded
- [ ] Documentation updated if the cause was a knowledge gap
- [ ] Authority limit reviewed if the cause was an authority trigger
- [ ] Agent told the outcome — closing the loop with them matters too

---

## 7. Monthly review agenda

1. **Volume** — how many escalations, trending which way
2. **Categories** — which trigger types dominate
3. **Appropriateness** — were they correctly escalated? Sample a few
4. **Response times** — were commitments met
5. **Root causes** — what patterns are visible
6. **Actions** — documentation to write, limits to adjust, product issues to raise

---

## 8. Diagnosing the two failure modes

### Over-escalation — too much reaches tier 2

Check in this order:

- **Authority limits too tight?** An agent who cannot approve a small refund will escalate a lot of small refunds. Raising a limit slightly is often the highest-value change available.
- **Documentation incomplete?** Every undocumented question becomes an escalation by definition.
- **Triggers too broad?** "Escalate anything unusual" produces a great deal of escalation.

### Silent escalation — too little reaches tier 2

Worse, and harder to see. Symptoms:

- Repeat contacts about the same unresolved issue
- Complaints arriving through channels other than support
- Agents making commitments outside their authority
- Customers escalating publicly instead of through you

Cause is almost always how escalations are *received*: slow responses, unfriendly reactions, or escalating treated as failure.

> **The cultural rule:** escalating correctly is good performance, not a failure. An agent who escalates a genuine risk trigger has done the job exactly right, even if the answer turns out to be routine.

---

*More free templates and guides: voicesupportcrew.com/downloads*