SOPStarter

Customer Support Escalation SOP Template

I wrote this for support teams that hand hard cases up a level and need it done the same way each time. It sets the triggers, what the handover must contain and how the customer is kept informed.

Purpose

Move customer cases that the first line cannot solve to the right person quickly, with everything they need, so the customer does not have to repeat themselves and does not wait without news.

Scope

Covers cases that are escalated from first-line support to second line, specialist teams or management. Routine requests solved at first contact and legal or safety emergencies handled by the incident process are out of scope.

Roles and responsibilities

RoleResponsibility
First-line agentTriages the case, decides whether it meets an escalation trigger and writes the handover.
Second-line specialistAccepts the case, investigates, and either solves it or passes it to engineering or management.
Support team leadApproves exceptions, handles complaints about the process and watches the escalation queue.
Account ownerIs told about escalations for their accounts and speaks to the customer when the relationship is at risk.

Prerequisites

  • A ticketing system with an escalation status and an assignee field
  • The escalation triggers, with response times for each priority
  • On-call or queue ownership for each escalation team
  • Templates for the customer holding message and the handover note
  • Access for second line to account data and logs the customer has agreed can be viewed

Procedure

  1. Try to resolve at first contact. Use the knowledge base and your checklists, ask for any missing details and try the standard fixes. Do not escalate a case just because it is difficult for you.
  2. Check the escalation triggers. Escalate when the case matches a trigger: a fix needs access or authority you do not have, the issue affects more than one customer, a data, security or billing risk exists, the customer has asked for a manager, or the response deadline for the priority is close.
  3. Set the priority. Set priority using the table by impact on the customer and urgency. A customer who cannot use the service at all is higher than one who finds a feature inconvenient.
  4. Write the handover note. Include who the customer is, what they want, what happened and when, what you already tried and what the result was, relevant IDs, logs or screenshots, and what you told the customer. The next person must not need to ask the customer anything you already know.
  5. Assign to a named owner. Assign to the right queue or person and set the status to escalated. If nobody accepts within the agreed time, tell the team lead.
  6. Tell the customer. Send a message that says the case has gone to a specialist, who will look at it, when they will hear next and how to add information. Do not promise a fix time you do not control.
  7. Accept and acknowledge. The receiving specialist confirms acceptance in the ticket within the response time and reads the handover. If it is wrongly routed, they hand it on with a reason instead of leaving it in the queue.
  8. Update on the promised schedule. Add an internal note after each action and send the customer an update at the interval promised, even when there is no progress to report.
  9. Escalate again if needed. If the specialist cannot solve it, they pass it to engineering or management with a new handover note. The first-line agent stays the customer's contact unless the customer agrees otherwise.
  10. Resolve and confirm with the customer. Tell the customer what was done, ask them to confirm it works and close the case after they confirm or after the agreed waiting period.
  11. Review escalations weekly. The team lead reviews escalated cases for patterns, missing knowledge-base articles and avoidable escalations, and records changes to triggers or training.

Revision history

VersionDateAuthorChange
1.0[Date][Name]First version

Assign this SOP to your team and track who has read it

The Word export uses the docx library (MIT licence).

How it works, and what stays on your device

Download the template as a Word file or as Markdown. Both are built in your browser from the text on this page, so nothing is uploaded and nothing is sent to a server.

Copy to Google Docs puts the template on your clipboard as formatted text, then opens a new Google Doc in another tab. Paste it there with Ctrl+V, or Cmd+V on a Mac. Google only sees what you paste.

Fill in the square brackets, change anything that does not match how your team works, and add a row to the revision table each time you change it.

Frequently asked questions

How many support tiers should I have?

Use as few as you can. Two levels, first line and specialists, is enough for many teams. Add a third only when a separate group, such as engineering, takes cases.

What is a good handover note?

One the next person can act on without contacting the customer. It lists what happened, what you tried, the IDs and evidence, and what the customer has been told.

Should the customer know about the escalation?

Yes. Tell them a specialist has the case and when to expect the next message. Customers mind silence more than they mind a handover.

How do I handle an angry customer who asks for a manager?

Treat that as a trigger. Hand over with the full history, tell the customer who will contact them and when, and make sure the manager reads the case before they call.