Customer support can be a tough job, but the building blocks of meeting your customer's expectations are actually quite straightforward. Inquiries to your team must be resolved in an accurate and helpful way, and the faster you respond, the better.
There's a lot to pay attention to when looking at your ticket stats, but first reply time (FRT) is high up there. In fact, Zendesk's data team has found that decreasing FRT correlates with an increasing customer satisfaction rating.
In your Zendesk Support, FRT is calculated as the time between when a ticket was created to the time the first public comment from an agent is made on that ticket. If the ticket is solved without any public comment at all, it doesn't contribute to your FRT metrics.
When you see that FRT start to rise, take notice, and take advantage of some of these tips to help bring it back down:
- Self Service: When your customers help themselves, you don't need to worry about FRT! Not sure how to start? Keep track of your top issues, and write articles based on those making sure that agents are well trained and refreshed on those articles. Many customers now go online to serve themselves and you should do your best to meet them there. Build up your Help Center, and make sure your agents are active there to quickly answer questions from your community.
- Trend or Outlier: Look at your ticket volume when looking at changes to your first response. Have you had a big surge leading up to the increase in FRT? Start with the Tickets and Efficiency tabs of the Zendesk Support dashboard in Explore. If you had a temporary surge from a new product launch or a major service incident, then this might not be a sign of a worrying trend. Even so, if you can predict these surges, that's a great time to bring a bit of extra help on board. At Zendesk, when we have a new product launch, we like to bring in the responsible product team and developers to help out.
- Look at your support hours: Do you know when you get most of your tickets? Are you sure? A quick look at the Explore Tickets created by hour report on the Tickets tab of the Zendesk Support dashboard can help you make sure that you have support online and ready to go when your customers are. Thinking about making the jump to round-the-clock support? Have we got a white paper for you .
- Real-time support: Even if you're super fast at answering tickets, you can't beat live channels like Zendesk Chat and phone calls . Plus we've found that people really prefer using the phone to other channels when reaching out to a company's customer support (here's a sweet infographic ). How cool would it be to have a median FRT under a minute?
- Problems & Incidents: When something goes wrong, it's critical to quickly identify and address emerging issues. Get back to your customers quickly, letting them know you're aware and working on a problem is key to turning something unfortunate into an opportunity to give them a positive experience interacting with your company. We use Problem & Incident ticket types extensively, so that we can get back to affected customers as fast as possible (here are some views/triggers we've setup to keep track of them), and also let them know when we've resolved an issue. It's a great and easy way for your agents to get an early jump on these tickets.
2 Comments
Hi,
We use many triggers to send auto-replies when customers contact us outside of business hours. Many of those set the ticket status to 'Open', considering it would positively impact our FRT and contribute to following our SLA policy. However, this is different from the expected behaviour, as our first reply time increases as time goes by.
I saw a post saying that their auto-replies do the reverse, which has an impact on SLA. They'd like it to consider the first public comment from an agent - https://support.zendesk.com/hc/en-us/community/posts/5131656743322-First-Reply-time-SLA-skipping-the-auto-reply. So if it does impact their SLAs and the FRT counts when the auto-reply is sent to the customer, why doesn't it happen with our auto-replies? From what I researched and found, only public comments contribute to FRT, so I need clarification. Can we set an auto-reply using triggers to impact FRT, especially outside business hours, positively? Thanks.
Triggers cannot impact the first reply time as the messages sent this way are not considered messages from agents.
Only an agent's public reply can stop this metric. In the context of an SLA, if there is no reply but the ticket is solved, the metric is fulfilled.
The status of the ticket does not affect the way this is measured.
You can find more details on how exactly the FRT works in this article:
I hope this helps! Please let me know if you have any questions.
Please sign in to leave a comment.