Informa helps businesses and professionals in hundreds of ways.

Our international portfolio of live events, world-leading research publications, and innovative digital services provide specialists with the knowledge and connections they need to thrive.

HDI Service & Support World
April 25-29, 2027
Caesars PalaceLas Vegas, NV
Escalation Overload: How to Reclaim Ownership at Level I

If you’ve been working in frontline support for a while, you’ve probably seen that service desk analysts are handling more complex issues. According to Zendesk, escalation rates are rising, with 20-30% of tickets now getting pushed to Tier 2 or higher, and first-contact resolution rates around 70-80% (see also data from Fullview).

An escalation has a measurable impact and often costs two to three times more to resolve. This is due to longer handle times and the need to involve staff with specialized knowledge. Customers are affected by longer waits, staff may feel discouraged and it can affect your budget (SQM).

However, there are practical ways to reverse this trend and reclaim ownership at Level 1.

Understand why there are more escalations

To fix a problem, you must understand it. Look at why tickets are being escalated. Some common reasons are:

  • Knowledge gaps or ineffective tools that leave analysts unsure of how to proceed.
  • Policies that don’t allow the analyst to make simple decisions and force an escalation.
  • Routing complex issues to inexperienced staff.
  • Lack of change management, causing unfamiliar issues.
  • Poor communication of defects.

A mid-sized SaaS company analyzed a month’s worth of ticket escalations and found that 45% of the issues stemmed from just three knowledge gaps. Simply addressing those issues cut their escalation rate by 18%.

So, pull a sample of recent escalations and categorize them by root cause (knowledge gap, policies, tools, routing, etc.). When you identify a trend, address it with your team.

Empower your team with better tools and training

Escalations happen when your staff doesn’t know what to do. They lack confidence or are unfamiliar with the necessary resources. Effective teams address this:

  • Provide training on everyday issues, focusing on avoiding escalations if possible.
  • Embed decision trees within the associated knowledge, guiding the analyst to the right outcome.
  • Build a robust knowledge base and use real-time knowledge suggestions based on keywords in the ticket. Some AI-based systems “listen in” on a call and display knowledge based on what it hears.

A global technology firm identified the top 10 drivers of escalations with its frontline team and created short, scenario-based videos that addressed them. Within six months, resolution rates at Level 1 improved by 12%, and the staff reported feeling more empowered.

You can take a similar action. Build a Pareto chart identifying the top five escalation issues and update the knowledge article for each. Test with a small group and then roll it out across the team.

Loosen up policies without creating risk

Often, escalations happen because the team doesn’t have the appropriate rights to make a simple decision. Find ways to empower staff:

  • eCommerce companies can allow for “goodwill” gestures, where the analyst can give a monetary refund or increase the time limits on demo products.
  • For common scenarios, add a list of pre-approved solutions to the knowledge base.
  • Provide checklists that encourage ownership, directing the analyst to escalate only if certain criteria apply.

An eCommerce support team raised the refund authority of their support staff by $100 for verified issues. As a result, billing disputes dropped 28%, and customer satisfaction improved.

Identify a common scenario and give half of the team the ability to remediate it. Measure the escalation rates and costs before expanding across the team.

Improve routing

Improving how tickets route means getting issues to the right person the first time. Effective approaches include:

  • Use skill-based routing to match a complex issue to the team with the expertise to resolve it.
  • Communicate changes and identify known issues and how to avoid them or create a workaround.
  • Institute self-service processes that handle routine inquiries before they become tickets.

Teams that use intelligent or skills-based routing often see up to 25% less unnecessary escalations.

Your action: review your routing rules. Identify areas where skill-based routing might be effective and implement it for a single issue. Measure the deflection and resolution rates for 30 days, and if successful, identify additional opportunities.

Conclusion

The payoff for all this work should be a reduction in overall escalations. Even a 10% reduction has a measurable impact on handle time, resolution time and costs. Customers are happier, and the staff feel empowered.

Start today by conducting root-cause analysis and fix the most significant issues first. As you progress, you’ll watch the results — and ownership — grow.

Related news

Bridging the Gap: 5 Tips for Cross-Functional Collaboration That Enables AI Transformation

Ask ten executives who owns AI at their company, and you’ll get ten different answers. IT says it’s not their call. Legal gets blamed for slowing everything down. HR figures it’s someone else’s department. Meanwhile, teams are buying tools nobody signed off on, duplicating work and hoping it all sorts itself out. Sound familiar?

Lisa Duerre spent the last year studying why that happens. As part of an applied research project for her leadership consulting collective, RLD Group, she studied where AI adoption breaks down inside organizations, and where it works. The findings from RLD Group’s research helped inform a collaboration on the CONVERSATIONS WORTH HAVING®: The Human Accelerator for Artificial Intelligence Quick Start Guide, which is available as a digital download.

Duerre views organizations through what she calls an I–WE–US leadership framework, defined like this:

  • I: individual judgment and accountability

  • WE: workflows and cross-functional coordination

  • US: governance, decision rights and organizational measures

“All three levels are contributing to the breakdown or the alignment, whether people realize it or not,” Duerre says. “AI is amplifying whatever’s already true in your system. The teams that were disconnected before AI showed up are more disconnected now. The ones that talked to each other are moving faster, together.”

If your company is ready to collaborate better with AI tools, Duerre shared the following tips. Take a look.

Form a cross-functional AI committee

Duerre’s background is in HR, and she says most HR leaders assume AI ownership belongs to IT. It doesn’t, at least not exclusively.

“Ownership needs to sit at the system level,” Duerre says. “Each function carries a piece of it, based on what they do, how well they understand that part of the business and how their work depends on everyone else’s. AI is flattening how we work. You can’t just keep it in your own business unit anymore. You have to look all around you.”

For starters, she suggests building a cross-functional AI committee instead of having one department make all the AI decisions. Legal, IT, cybersecurity and HR should be on the committee, Duerre says.

“If you have a C in front of your title, you should be on that committee,” Duerre says. “That’s how I look at it, because it’s a system-level solution.”

During these meetings, Duerre says you’ll find out that some departments are racing ahead with AI and others are holding back.

“Both sides need to name the trade-offs aloud,” Duerre says. “With teams moving too cautiously, you have to talk about the opportunity cost of falling behind. With teams sprinting ahead, you have to ask them what happens if they don’t bring everyone else along with them.”

Figure out how to use AI strategically

Most companies spent the past two years telling employees to use AI with anything, without much strategy behind it. Duerre says that’s starting to catch up with organizations as finance teams scrutinize the cost.

Her rule of thumb: if you can’t articulate the goal and how you’ll measure success, don’t roll it out yet.

“Teams that use AI well have a strategy behind it,” Duerre says. “They’ve kicked the tires on what they’re trying to solve it for. You need to ask yourself, ‘Which business outcome are we trying to improve, and what must be aligned for AI to create measurable value?’”

Here are a few examples of how to use AI strategically:

  • A company could select a workflow that regularly creates delays, redesign it with AI and test the new approach. Then, measure whether it improves time, cost, quality or capacity.

  • Use AI to support early sales outreach and qualification across markets and languages. AI can help a business reach and assess more potential opportunities, while people remain responsible for understanding the customer and building trust.

  • Flag patterns in customer complaints across multiple channels with AI, so leadership can see recurring problems before it shows up in satisfaction scores.

Check-in regularly during an AI rollout

Duerre recommends a minimum weekly check-in during any AI rollout, sometimes daily depending on complexity. But the format matters more than the frequency. Status updates don’t cut it.

“Ask, ‘What are we learning and what are we surprised by?’ That’s a question that helps you with your check-ins, versus, ‘It’s in three products now and we’ve tested six,’” Duerre says. “That doesn't help, because you’re having these meetings to figure out what’s working and why. If you ask more strategic questions, you can move even faster.”

Publish AI guardrails

Employees who don’t know what’s allowed with AI will either freeze or go around the system entirely, Duerre says. She recommends publishing clear, specific guardrails on what’s okay and what’s not. Come up with some real examples, and pair them with an intake process that doesn’t require writing a thesis to get an approval for using it.

"The approval path should be lightweight, not bureaucratic,” Duerre says. “Something like, ‘If you’re going to use AI, here’s the path. And if it needs approval, here’s three or four quick questions for you to answer.’”

Take employee anxiety about AI seriously

“AI is just a tool” is a phrase Duerre hears at nearly every conference she attends, but she doesn’t buy it.

“Saying it’s a tool is underselling what’s happening at companies right now,” Duerre says. “AI is changing how we work. It’s changing how we lead teams.”

Duerre wants leaders to remember that a lot of employees are fearful of AI. Pew Research Center found 52% of U.S. workers are worried about the future impact of AI in the workplace.

Employees who feel AI is being “done to them,” instead of built alongside them are especially anxious, she says.

“Leaders need to recognize that anxiety is contagious,” Duerre says. “As a leader, this is your opportunity to show up as the safe, steady person who is showing what you’re learning with AI. And don’t be afraid to show how you’ve failed using AI, too.”

Duerre asks every executive she works with: “Who am I with AI?” and encourages them to pass this mindset question along to their employees, too.

“AI is now your teammate,” Duerre says. “Phrasing it as, ‘who am I with AI?’ is different than, ‘what’s going to happen to me with AI?’ You really want your team to feel empowered with AI and show them how it can help accelerate their career.”

Put these ideas into action

Rewiring your organization for AI requires more than the right tools. It takes shared language, practical frameworks, and a willingness to keep learning. Here are a few resources to help you take the next step.

  • Enterprise AI Playbook: Practical frameworks and executive discussion questions to help IT, HR, and business leaders align around AI that delivers measurable value.

  • Work-First AI Use Case Assessment: Identify the workflows where AI can have the greatest impact before you invest in new tools.

  • The REWIRED Brief: Get weekly insights, real-world case studies, and practical advice on leading AI transformation.