Jan 12, 2021

Read Time 4 min

5 steps for a smoother customer escalation

Share

This is a guest blog post by Kristen Hayer, founder and CEO of The Success League

No one loves when a customer feels the need to escalate their concern. For the customer, it feels like they have to take an extra step to accomplish what should have happened, from their perspective, in the first place. A CSM can feel like they haven’t done their job well or that their company reflects poorly on them as a CS professional. Other teams who need to get involved may feel like they don’t have an incentive to help or support from their own leader. CS executives who have to step in to resolve customer issues often feel that they are a distraction from the critical work of managing and guiding the organization forward.

As a CS professional, how do you balance the customer’s need of feeling helped with the internal constraints of your own organization? Here are five steps to take when a customer wants to escalate an issue.

1. Try to diffuse the situation

Before you escalate an issue inside your organization, take a few minutes to attempt to resolve it on your own. Know that in every difficult conversation, there are things going on under the surface. Your customer may have a lot of pressure from their peers regarding the problem, they may be feeling disappointed and frustrated, or their job could be on the line. Until you understand the scope of the issue, you can’t effectively escalate it anyway. Ask questions about the impact the problem is having on the customer and their business, and actively listen to the answers. This does two things: It helps you understand what is really going on behind the scenes, and it gives the customer a chance to feel heard. Sometimes this is enough to de-escalate the situation. If not…

2. Tap into your peers

Ask your co-workers for suggestions on handling similar situations. Often, you’ll find that one of your peers has faced the same challenge and learned a lot from tackling it. Your team can be a great source of information on ways to address the issue directly with the customer, and also when and how to escalate further. Some CS teams have a Slack channel set up specifically for escalations, so that anyone can make suggestions when an escalation surfaces. By tapping into your own team, you can limit escalations to other teams inside your company so that when you need to you can…

3. Form a task force

In Customer Success, solutions typically involve other teams like product, engineering, operations or support. For small issues that require a handoff, follow the handoff processes you have in place and let the customer know what you’re doing (Note: if you don’t have a handoff process developed, consider our class on customer advocacy, which includes an escalation handoff worksheet). For larger escalations, however, you may need to form a cross-functional task force to tackle the issue. It helps to plan this out in advance and consider things like:

  • When is a task force required?
  • Who decides when to pull the group together?
  • Who should be in the group?
  • What is the group allowed to do to meet customer needs?

If the task force can’t reach a resolution with the customer, the next step is to…

4. Escalate to your manager

It’s important to note that there are three steps that come before this one. You don’t want to be the CSM who is always bringing things straight to your manager – that makes it seem like you don’t know how to handle challenging situations on your own. However, you also don’t want to be the CSM who doesn’t know when a manager needs to be looped in. The trick is to work things through very thoroughly (and quickly) on your own first, and then escalate to your manager when you have exhausted your other options. When you bring the issue to your manager, make sure you explain the issue, discuss what you’ve already tried, and offer up suggestions. This will help your leader take things to the next level rather than just repeat what you’ve already tried. And if that doesn’t work, they may need to…

5. Loop in an executive

If this issue is a big one, and executives on the customer’s end have also been looped in, it’s likely time to bring in your own executive. When challenges move outside of what you or your manager can resolve on your own (things like the customer needing a major piece of new functionality or the customer ignoring your security protocols), your executive has the clout to make business changes for the customer, or make the decision that they are OK with the churn that not making those changes may cause. This stage can take time because your executive may need to bring issues to the rest of the leadership team or look at the business case for a resolution. Be sure to ask your executive about their timeline instead of assuming that it will be similar to your own.

There is no shame in escalating an issue. Using these steps, you can loop in the right people at the right time, and ensure that you’re not escalating a problem too early or too late. Use your best judgement throughout this process, and be honest with yourself before kicking off an escalation. Ensure that you aren’t escalating because you’re nervous about having a tough conversation (here’s a class on difficult conversations if this is a challenge area for you), and don’t escalate before you have a clear understanding of the customer’s perspective on the issue. Knowing your escalation plan ahead of time allows your customers to get the help they need.

Share

Subscribe to the newsletter   

What’s new with ChurnZero: product release notes for Q1 2024

Just as customer success is always evolving, so is ChurnZero's customer success software. Catch up on what's new from Q1 2024, and see how it makes a difference, in our quarterly roundup of ChurnZero product release notes. Feature Update : Chart and table enhancements...

Digital Customer Success: A Getting Started Guide – Part 1

Every customer success leader I know is being asked to do more with less. I could go on and on about the macroeconomic factors, the cycle of overhiring and layoffs, and the “new normal” for spending justification that’s causing this, but I won’t. Instead, I’ll just...