How to Reduce Ticket Escalations to Tier 2 in Zendesk

Why tickets get escalated to Tier 2

Before you can reduce escalations, it helps to know where they come from. Most fall into a few predictable buckets.

Agents can't find the answer. The information exists somewhere, in a Help Center article, an internal doc or an old ticket, but Tier 1 can't find it fast enough. Escalating feels quicker than searching.

The documentation is outdated or missing. An agent finds an article, but it describes an old version of the product or skips the edge case the customer is asking about. Without confidence in the answer, they pass it up.

Agents aren't sure they're allowed to act. Refunds, exceptions and account changes often come with unclear rules. When agents don't know where their authority ends, they escalate to be safe.

New agents don't know what they don't know. Newer team members escalate more simply because they haven't seen enough tickets yet. That's expected, but a slow ramp-up keeps escalation rates high for months.

The ticket is too long to follow. A thread with ten back-and-forth replies, multiple contacts and side conversations is hard to pick up cold. Escalating can feel easier than piecing it all together.

Notice that only one of these is about ticket difficulty. The rest come down to access, confidence and clarity, which are all things managers can improve.

How to reduce escalations to Tier 2

1. Review your escalated tickets first

Pull the last 30 to 50 tickets that went to Tier 2 and read through them with one question in mind: could Tier 1 have solved this with the right information? Tag each one with a reason, such as "couldn't find the answer," "policy unclear" or "true Tier 2 issue."

This takes an afternoon, and it usually shows that a handful of topics account for most of your avoidable escalations. Those topics are where to start.

2. Fill the gaps in your knowledge base

For every escalated ticket that was really a missing answer, ask whether that answer is documented anywhere Tier 1 can reach. If not, write it down. If it's documented but buried or out of date, fix the article.

Tier 2 agents are your best source here. They've already solved these tickets, often many times. A quick internal note or short article from them can prevent dozens of future escalations.

3. Put answers where agents already work

Even a great knowledge base doesn't help if agents have to leave the ticket, open a new tab and guess at search terms. The more steps it takes to find an answer, the more likely an agent is to escalate instead.

Make answers easy to reach from inside the Zendesk ticket. Link related articles in your macros, keep internal docs in the same place as public ones, and give agents one place to search rather than several.

4. Write clear escalation criteria

Agents escalate when they aren't sure. Remove the guesswork by spelling out exactly what Tier 1 can handle on its own and what must go to Tier 2. For example, define refund limits, which account changes need approval and which error messages always mean a bug.

Keep the list short and specific, and put it somewhere agents can find it mid-ticket. When the rules are clear, agents stop escalating "just in case."

5. Shorten the ramp-up for new agents

New agents will always escalate more at first, but you can speed up how quickly they gain confidence. Pair them with a Tier 2 mentor for their first few weeks, walk them through your most common ticket types and show them how to search your docs effectively.

Also encourage them to read how Tier 2 resolved the tickets they escalated. Each one is a lesson that prevents the same escalation next time.

6. Make long tickets easier to pick up

When a ticket has a long history, a short summary at the top of the thread helps any agent get up to speed in seconds. Encourage agents to leave an internal note summarizing the issue, what's been tried and what's still needed before handing off or stepping away.

That same summary also makes the escalations that do happen go faster, since Tier 2 doesn't have to reread the entire thread.

7. Close the loop with Tier 2

Escalation shouldn't be a one-way street. When Tier 2 resolves a ticket that Tier 1 could have handled, they should share what the answer was, either directly with the agent or by updating the relevant article. Over time, this turns every escalation into documentation that prevents the next one.

How to measure your progress

Pick a few simple numbers and check them monthly:

• Escalation rate: the share of Tier 1 tickets that get escalated. This is your headline number.
• Avoidable escalations: the share of escalated tickets tagged as solvable by Tier 1. This tells you whether your fixes are working on the right problems.
• Escalation rate for new agents: how quickly new hires' rates drop toward the team average.
• Time to resolution for escalated tickets: with fewer easy tickets in the queue, Tier 2 should resolve the hard ones faster.

In Zendesk, adding a required "escalation reason" ticket field makes most of this easy to report on.

Give Tier 1 the answers they need

Most avoidable escalations come back to the same problem: the answer exists, but Tier 1 can't find it or doesn't trust it in the moment. Fixing that is less about new processes and more about putting the right information in front of agents while they work the ticket.

That's the gap TicketDone was built to close. It works inside the Zendesk ticket sidebar, drafting replies from your own Help Center articles and internal docs and answering agent questions with the sources cited, so Tier 1 can check the answer before they send it. It can also summarize long ticket threads for handoffs and flag outdated articles, so the gaps that cause escalations get fixed instead of repeated.

The result is fewer tickets passed up the chain, faster ramp-up for new agents, and a Tier 2 team that gets to focus on the problems that actually need them.