Ticketing Style Guide
Why do we need a Ticketing Style Guide?
To maintain the quality of our customer experience as the Support team grows, we have gathered a collection of best practices and suggestions for styling and responding to Zendesk tickets.
Consistency is what enables any Support Engineer to jump into an unfamiliar ticket and get to work fairly quickly. Consistency enables scaling, and consistency is what we’re hoping to achieve with this guide.
Some of the suggestions in this guide will encounter cases that warrant exceptions, and that’s OK.
Everyone in the Support Team is welcome to contribute or modify the suggestions in this guide given that they provide the “Why”, especially when a practice has proven to work, or not work for them through experience.
Readability
- If your reply consists of more than 6 lines, consider breaking it to sections using HEADERS. Example:
|
|
This will help the customer as well as fellow support engineers to quickly find the information they’re looking for.
- Aim to add a public 1 line summary of the latest current issue for every 3 replies you send to the customer. Example:
|
|
This will ensure that the customer and you remain on the same page regarding what the issue is.
This will also help other support engineers to jump into the ticket and catch up on the context more efficiently.
Technical Content
- Ask for
gitlab.rb
, or any other missing information or logs, but don’t let your reply consist of only that. Describe why you’re asking for the additional info. Example:
|
|
This will help the customer understand how they can debug this issue themselves.
It will also help other support engineers to understand what you were aiming to look for in the provided data, and keep the debugging direction consistent over the next replies.
- When requesting logs from the customer, only ask for as much as you think you’ll need to diagnose the problem. Example:
|
|
This makes it easier to debug the issue as you’ll go through the minimal number of log files, and save the customer from breaking up a large GitLabSOS file, unless GitlabSOS is necessary.
f348e5a6
)