The Golden Ticket: How to Improve Response Time and Enhanced Customer Service

Outstanding customer support is one the most important differentiators of a well-run software business. However, providing extraordinary support that delights your customers can become expensive.  

Since we never sell our businesses, we think differently about operational improvement. We are not optimizing for quarterly improvements, or an eventual sale. Instead, we help our businesses grow sustainably over the long-run. This mindset has led us to invest heavily in sharing practical best practices across our group, especially in areas that directly affect customer experience. 

This article focuses on one simple but very effective best practice that we have coined the “Golden Ticket”, which has sped up response times and enhanced customer service.  

What is a “Golden Ticket”? 

Most customer support calls start with an incident report or a “ticket”, but are all support tickets created equally? An experienced support professional would say no. Tickets are as unique as the customers from which they come. This can result in tremendous inefficiencies for even the most experienced support teams as they try to decipher the root cause of each incident. 

Tickets can be created for various reasons, therefore for better tracking and workflows, most support departments categorize them into areas such as: 

• Issue 

• Question 

• Upgrade 

• Feature Request 

The first category, “issue,” often takes the most time to resolve. To address this, we employ the “Golden Ticket” best practice for issue tickets across our group. We have found that this practice can increase the efficiency and effectiveness of support teams at any software organization. 

The Golden Ticket is a support ticket with enough detail for the team to resolve the issue correctly and efficiently.  

Grey Ticket Vs. Golden Ticket 

Quality customer service begins with getting the right information. In practice, there are a lot of “grey” tickets that lack the appropriate level of detail. In these cases, support representatives will spend too much time theorizing about what the customer needs. They may spend 30 minutes on the initial problem trying to understand the issue. After that, there may be an “e-mail loop” with the customer, where they go back and forth exchanging more information. In practice, some software companies see this go on for hours, days, or even weeks before being handed off to a developer or a subject matter expert. 

To make matters worse, grey tickets often include red herrings, sending support teams down the wrong path due to incomplete or conflicting information.  

The Anatomy of a Golden Ticket 

A Golden Ticket addresses pitfalls by mandating the following: 

• A detailed description outlining who is involved, what occurred, when the issue occurred, where the issue happened – which device, operating system etc., and how it happened, including the steps to duplicate the problem and which screens 

• Expected results vs. actual results: this replicates the methodology for user testing and can help you understand if what the user expects is reasonable given the capabilities of the software. 

• Screenshots: “a picture says a thousand words” 

Getting a detailed description speeds up prioritization, problem identification or debugging, development, testing and documentation. It also helps to detail the steps required to duplicate the issue. From a Quality Assurance (QA) standpoint, the team can add this to their testing scenario suite. 

How to Encourage Customers 

Getting your customers and team engaged is a key step to rollout. The Golden Ticket is a great agenda item for a user group with a support manager presenting, or even a regular webinar. 

Start by demonstrating the value for the customer. When discussing the Golden Ticket, you want to present it as a tool to get customer issues resolved more quickly. Let them know that you want to improve your service, and that you need their help. 

One effective way that our companies get buy-in is to be transparent and show each customer their current resolution times vs. targeted resolution times. 

Assess Your Ticketing System 

 If you have a form-based ticket submission process, you should have a detailed form appear for “issue” tickets and encourage customers to include a screen shot. When receiving a phone call, the support agent should use detailed prompts for “issue”-type tickets.

How to Coach Your Team 

Response times are key when it comes to managing a support team. You could consider tracking: 

• Time to first reply 

• Time between replies 

• Resolution time 

• Number of replies per ticket 

Helping your team understand that they can improve their response times and replies per ticket by getting more details from the outset, can create better habits. 

A Win-Win 

Ultimately, we see Golden tickets as a “win-win” for management, support teams and customers. They create clear communication between all parties and reduces friction.  

It respects the time of your support team, your developers and your customers, and strives to solve the problem correctly the first time.  In some cases, improving performance does not come from adding headcount or investing in new tools; it comes from raising the bar on clarity.

Back to Insights