Escalation in customer service: when, to whom, how fast

Most customer service teams have an unspoken agreement about what happens when someone cannot answer: you ask whoever usually knows, or the email waits until the manager has time to look. That works while the team is small and nobody is on leave. This article shows how to make that agreement explicit, so tickets do not get stuck between people and the customer does not have to tell the whole story again.

What is escalation in customer service?

Escalation is when a ticket is passed on to someone who can solve it, because the person holding it cannot. It happens in three directions:

• From self-service or AI to an agent, when the chat or form has no answer or the customer asks for a person.
• From the first line to a specialist, for example finance, the warehouse, technical staff or whoever owns the contracts.
• From an agent to a manager, when the ticket needs a decision beyond the agent's authority, such as compensation or an exception to the terms.

Escalation is not a failure. It is how you get the right person onto the right ticket. The failure is when the ticket stops halfway: handed off by one person and not picked up by the next.

When should a ticket be escalated?

When the person holding it lacks the knowledge, authority or time to solve it, or when the ticket carries a risk. Four triggers cover most cases:

1. Knowledge. The answer is not in the knowledge base and the agent cannot find it out alone. A customer asking about a special order, a technical fault or a contract nobody on the team has seen.
2. Authority. The solution needs a decision the agent is not allowed to make. Write the limit down in kronor or by type of action: credit up to a set amount, but no more.
3. Time. The response target is about to be missed, or the customer is getting in touch for the third time about the same thing. The third email is a signal in itself, whatever it is about.
4. Risk. The customer mentions a regulator or a lawyer, the ticket involves personal data sent to the wrong person, or it concerns security. Such tickets must never stay in the inbox.

Add a fifth, which is judgement rather than a rule: the very upset customer. They do not always need a manager, but they need someone with the time and authority to settle the matter in one reply.

What does an escalation matrix look like?

An escalation matrix is a table stating where a ticket goes, when and how fast. It does not need to be longer than one page. An example for an online shop with a small team:

The times in the table are examples, not rules. What matters is that each row has a time and a recipient, and a stand-in when the recipient is away. Give escalated tickets their own ticket type or flag so you can see how many there are and what they concern, following the principles in the article on categorising tickets.

What should go with the ticket when it is handed over?

Everything the next person needs to answer without asking the customer again. Having to repeat themselves is what customers dislike most about a handover: according to Zendesk's CX Trends 2026, 74 per cent of consumers are frustrated when they have to repeat information, and 81 per cent want the conversation to continue without backtracking.

A good handover contains five things:

1. What the customer wants, in one sentence.
2. What has already been done and said, including anything the customer has been promised.
3. The evidence: order, photos, earlier tickets.
4. Why the ticket is escalated, which trigger in the matrix.
5. What the customer has been told about the next step, and when.

The last point is the one most often forgotten. Tell the customer the ticket has moved on, to whom in general terms ("our finance team") and when they can expect an answer. To the customer, a ticket escalated in silence looks exactly like one that has been left lying.

When should the AI hand over to a person?

When it has no grounded answer, when the customer asks for a person, and when the ticket needs a decision. A chatbot that guesses instead of handing over makes escalation more expensive, because the customer reaches the agent carrying a wrong answer. Why the AI should answer from reviewed material and say so when the material is missing is covered in the article on chatbots that do not guess.

The same rule applies as for agents: the whole conversation goes with it. In Supportifier the chat says when the material is not enough and hands over to an agent in live chat, who sees the entire conversation; outside opening hours it shows the contact options instead of a queue.

What applies when you say no to the customer?

You must refer them to the National Board for Consumer Disputes (Allmänna reklamationsnämnden, ARN) at the same time. Under section 11 of the Swedish Alternative Dispute Resolution in Consumer Relations Act, a trader who wholly or partly rejects a consumer's claim must at the same time give information about the board the consumer can turn to, with its web and postal address, and say whether the trader intends to take part. The information must be given in a legible and durable form, for example in the email with the rejection.

That makes ARN the final level of escalation, and it sits outside the company. According to ARN, the consumer must first have complained to you, and the case must reach the board within one year of the first complaint. A rejection should therefore be considered, reasoned and made by someone with the authority to make it, not phrased in passing by whoever happened to pick up the email. How complaints should be assessed on the merits is covered in the article on complaints handling.

What to do

1. Go through the fifty tickets that took longest recently and note why. Those are your real triggers.
2. Write the matrix on one page: trigger, recipient, time and what goes with it. Start from the table above.
3. Set the amount limit for what an agent may decide alone, and write it down.
4. Name a stand-in for every recipient, so no ticket waits for someone on leave.
5. Write a handover template with the five points, and a template for the message to the customer.
6. Add the ARN referral to the rejection template, with the board's web and postal address.
7. Review every month: number of escalated tickets, what they concerned and how many were left lying.

Common questions

Should the customer get to speak to a manager when they demand it?

Not always, but the customer should always get to speak to someone who can solve the problem. Often the demand for a manager is a way of saying nobody has listened. If the agent has the authority to settle the ticket, it is better to do so straight away. If not, the ticket should move on according to the matrix, and the customer should be told to whom and when.

How fast should an escalated ticket be answered?

Set a separate time for escalated tickets, and measure it from the customer's first message, not from the escalation. The customer has already waited once. One working day is a reasonable starting point for most questions, the same day for tickets where the customer has been in touch several times, and immediately for personal data incidents.

Who owns the ticket after escalation?

Decide in advance and write it in the matrix. Either the recipient takes over the ticket completely and replies to the customer, or the recipient gives an answer to the first line, which replies. Both work. What does not work is nobody knowing, and the customer getting two different answers or none at all.

Do we have to refer to ARN every time we say no?

When you wholly or partly reject a claim from a consumer, yes. The Swedish dispute resolution act requires you to inform them about the board, with its web and postal address, and to say whether you intend to take part. Put the referral in the rejection template so it is never forgotten. It applies to consumers, not business customers.

Sources

• Lag (2015:671) om alternativ tvistlösning i konsumentförhållanden — Swedish Parliament, read 2026
• Kontrollera att ARN kan pröva din tvist — National Board for Consumer Disputes, read 2026
• Contextual Intelligence Becomes the New Standard for Exceptional Customer Experience in 2026 (CX Trends 2026) — Zendesk, 2025