Let’s face it, nobody enjoys dealing with ticket escalations.
When a ticket is escalated, it means there’s a problem that your ground-level employees can’t solve. The customer will have to wait, rather impatiently, for a solution; and if it escalates beyond that, it indicates a systemic issue that will require your developers to pull all-nighters.
It’s an unpleasant situation all around! But for a new business, a formalized ticket escalation process may even seem counter-intuitive. After all, if your team is small and your customer base is still growing, it may seem like unnecessary red-tape to add even more procedures in place.
Your tickets are bound to keep growing as your business thrives, and the sooner you get a handle on escalation, the better your customer service department will run in the long haul.
Expectations define the customer experience: those that your customers have of you and those that your agents strive to meet.These expectations are the heart of your service level agreement(SLA). Your SLA creates standards that your customers can expect you to meet, and sets benchmarks for your agents.
It’s basically the rule book that you share with everyone who comes into contact with your brand. It should have standards for every channel that you operate on, such as Twitter or Facebook, as well as a default policy.
Assigning tickets to agents individually may be doable for a startup with three team members. But when your team — and your tickets — grow, you need a helping hand to make sure there’s no delay between a ticket hitting the desk and an agent getting it on the docket.
But that’s not the only automation you should use. Letting resolved tickets stack up in the background may seem harmless, but it could impede your reporting by inflating the number of open tickets if they’re not closed, even though they’ve been addressed. For escalating tickets, you should automate reporting with scenario automations, so every team (such as your developers) involved is kept up-to-date with the status of the issue.
The problem with creating guidelines for escalation is that they’re all dependent on how people interpret them. Fortunately, there’s at least one reliable method for determining escalation needs with a ticket.
In a test environment, instruct your agents to repeat the events that led to the ticket, to see if they can replicate it. If they can replicate the issue, the ticket needs to be sent to the development (or equivalent) team as it indicates a product-wide problem. If they can’t, the problem might be isolated to a single user and can instead be escalated to higher customer service teams or agents.
This also helps create the priority level for the ticket. An issue that impacts multiple groups is always a higher priority than one that impacts a single user.
Special circumstances may dictate that a ticket is assigned a different priority level. In addition to your SLA, create a standardized protocol and checklist for agents to determine the priority level of a ticket. This will allow you to keep an eye on the tickets that need to be fixed ASAP, and those that have a little more time (though, of course, as a best practice, all tickets should be treated with urgency).
Escalated tickets will almost always mean escalated frustrations for the customer. You may not need to bombard them with updates. But if you know there is a roadblock, like if the development team hasn’t had a chance to look at it, then it is extremely crucial to keep customers on board and abreast of the process and progress. After all, slow or poor communication is the second most likely reason that your customers, particularly your younger customers, will leave your business.
Human memory is infamously fallible, and triggering recall with details that may be relevant to the ticket isn’t always perfect at first pass. So keeping in touch with the customer might not just alleviate their frustrations — it could actually expedite your problem-saving.
If you have omnichannel customer support, and you should, your escalation procedures should be as similar as possible across the different channels. For instance, if a ticket originates from social media, it should follow the same escalation path as an email-borne ticket. This creates a more seamless customer experience no matter where the customer initiates contact with your brand. Great omnichannel experiences drive great brand gains. To further streamline things, define the point during interactions when they need to change channels. Basically set rules for when a live chat needs to be escalated to email, or when social media needs to move to direct message.
Security and encryption can be a guiding hand for these rules. If the information required moves beyond what’s safe for the customer to share on that channel, they need to be escalated to a more secure, safer avenue to continue receiving service.
There are two sides to this.
If a customer’s tickets are regularly escalated, their account may need a review to see if they have the best solution for what they’re trying to accomplish with your product. You can view the ticket history of customers to identify trends. If an agent is regularly escalating tickets, then they may not be following your heuristics and guidelines. In that case, they require training to assign priority and follow your escalation process. Of course, it is possible, slim as the chance may be, that they’re simply more prone to receiving escalated tickets than others.
Alternatively, if it’s neither circumstance, you may have significant issues at the foundation of your product. Use that information to iterate your product and improve its overall function.