Speeding Up Your Response Times – Ticket Resolutions
April 24, 2012 Leave a comment
A key to providing a high level of customer service is the ability to get information to your customers and end users quickly and efficiently. You may have the best system in the world for gathering important information for end users, but if it still takes your agents hours to reply to tickets or live chats then the amount of information you have becomes rather irrelevant.
There are a few simple tools that can assist with both the accumulation of important information as well as facilitate the distribution of that information, quickly, to end users and customers. With today’s tip we’ll focus on one way to make sure your users are not only well informed but that they receive their information in a timely manner. Over the next few weeks we’ll cover other time-saving tips, so stay tuned.
Ticket Resolutions as Time Savers
Perhaps one of the lesser-known features of SmarterTrack is the ability to add resolutions to tickets. What that means is that an agent can add instructions, be it a simple explanation or step-by-step walk through, on how a particular issue was resolved. That resolution is then stored with that ticket.
The bigger benefit is that these resolutions are fully indexed, just like ticket content. That means that ticket resolutions, along with KB articles, are available as resources to assist agents who are troubleshooting similar issues. Agents can see any and all potential ticket resolutions that are associated to the contents of the ticket they’re working on. By using a pre-existing resolution, agents can greatly reduce the time it takes them to reply back to customers since the agent doesn’t have to spend the time looking for a way to solve the customer’s issues – it’s already been done for them!
A recent real world example can help demonstrate the power of using ticket resolutions to save time.
As you many know, Microsoft released an update to Office for Mac about a week or two ago. This update included changes to Outlook for Mac that happened to break SmarterMail 9.x’s implementation of Exchange Web Services. Once we got a ticket in from a customer experiencing issues, it took one of our support agents about 90 minutes to work through various scenarios until he concluded that the recent Office update caused the problem. The simple solution was to simply roll back the update.
However, during that time, a second ticket came in. As that second ticket was being worked on, the original agent heard the new agent talking about the issue and asked if the second customer had installed the Office update. It turns out they had.
This caused our agents to work up a resolution for the issue that they added to both tickets. When additional tickets started coming in, that resolution was instrumental in our support agents getting responses and resolutions out to our customers quickly. Adding the resolutions to those two tickets literally saved upwards of 40 hours of troubleshooting.
Had this issue been more widespread, had it affected an incredibly large number of customers or if it required a longer-term solution, the issue resolution could have easily been turned into a canned reply, a news item post on the portal or a knowledge base article. It could even have been turned into all three, thereby making sure customers received a consistent, concise and easy explanation for issues and their resolution, regardless of how the customer was communicating with agents.
So there you go, both a simple time saving feature and a current, real world example of how it was used. Of course, here at SmarterTrack.com we’re using the latest version of SmarterTrack so we have the added benefit of seeing issue trends using the trend cloud. Having that AND the ability to apply previous ticket resolutions is an even greater time saver, but more on that, and other time saving features, in future posts.








For example, using reports can indicate where your agents are spending their time and where you’re spending your money. If you’re able to assign a cost to the various agent roles within your organization, you can see if your front-line agents are accounting for the majority of your expenses or if your support costs are consumed by escalation departments, development staff or even management. In addition, if emphasis is on “one-reply resolution,” being able to see if customers are averaging two or more responses per ticket is a good indication that this metric isn’t being met. Of course, the reason could simply be that agents need to be able to start new tickets for those customers who continually reply to a single ticket for multiple issues. If you don’t have a report to show you that information, you can’t refocus the agents (and the customers) so that your metrics are met.
Another good way to gather metrics is using customer satisfaction surveys. Your helpdesk should have a flexible and customizable survey engine that allows you to customize surveys based on the types of interaction between agents and customers. For example, a survey that is offered when live chat ends should be worded differently than one that appears after an email ticket is closed. In addition, if you want to move beyond response ratings, you should have the ability to build custom surveys, such as a simple 




