For an overview of the support we provide to customers and GitLab.com users, please see the general support page. What follows is a more detailed description of the levels of service.
Response time indicates the maximum first reply wait time.
We strive to answer tickets faster than the SLA requires. The higher in the list a channel is, the sooner it should be answered.
We use a webhook to get Slack notifications when a high priority premium ticket arrives. It is posted on the
#support_gitlab-com Slack channel. If you answer the ticket put either a
:heavy_check_mark: emoji to let other support engineers know if you're reading or have responded to the ticket.
If you're not sure how to answer the ticket start a thread under the ticket and tag other support engineers to join the discussion.
Zendesk has a maximum attachment size of 20MB per file. Zendesk will not allow us to increase this limit any further.
If you need a customer to share a larger file than this, then see Provide large files to GitLab support for more info on how.
Depending on the queue you are working on and the form the ticket belongs to, you might need to fill out some ticket fields manually. Those fields help us capture important data that will help us improve the customer experience. As a high percentage of our tickets are solved/closed automatically through our workflows, it is important to make sure that before you submit your response to a ticket, you check that all required (*) fields and relevant non-required fields have been filled out.
GitLab.com Support team members should work on tickets following these views in order:
Within a view, tickets should be prioritized based on the SLA time until breach.
Support Engineers should work on tickets within their assigned support speciality as a first priority. Tickets should be picked up in the following order to make sure that SLAs are not breached (maximum SLA wait time exceeded), and customers receive the proper level of service:
After these are addressed, tickets should be worked on in SLA Priority Order. When a ticket is near breaching, or has breached its first reply (or next reply) SLA, the ticket must be picked up by any available Support Engineer independently of who is assigned to it. This also applies to tickets for Resellers (i.e. anyone picks up if close to breaching, regardless of who the Dedicated Support Engineer is).
Traditional Support teams often use an "assignment" model, where an agent is assigned a ticket and guides the ticket through to completion. If they are stuck, they can re-assign this ticket to another agent to pick up and try and complete. At GitLab though, we take advantage of our global support team and use a system dubbed "Hot Queuing". This system means that we all work from one global queue and it's expected that multiple agents will work together on most issues. This allows us to do the following:
There are times in the support process that an agent may need to assign the ticket to themselves:
If you see a ticket in the queue that you are not able to answer, you should:
With the hot queue, we all work together and no one should be scared to start a ticket.
If another agent is looking at a ticket that you’re interested in working on, keep in mind:
If another agent is looking at a ticket that you would like to work on:
If you are working on a ticket, and need some time to research, indicate your involvement by:
SLAs are set as Business Rules within Zendesk. For more information, please refer to the specific Zendesk page.
We have a slack integration that will notify us for self-managed, if a Premium ticket will breach within an hour, and for GitLab.com, if a Premium ticket will breach within 2 hours. If you see one of these, start a thread and consider this a small emergency. If you need help, draw the attention of other support engineers by tagging them, and work to move the ticket forward.
If a customer's reply is the last one in the ticket, do not set it to any status silently (except for Solved), because the breach clock will continue to run and the ticket may breach silently.
Instead, send a confirmation, greeting, or other message, while also changing the status.
You should use the On-hold status when it is necessary to do some internal work, e.g. reproduce a complex bug, discuss something with developers or wait for a session scheduled with a customer. When setting the status to On-hold it will be automatically assigned to you by the trigger
Automatically assign on-hold ticket to an agent who put it to the on-hold status. If you think that it should be assigned to someone else (e.g. session is scheduled for another engineer), feel free to re-assign it. Tickets without assignee will be automatically reopened by the trigger
Automatically reopen on-hold tickets without assignee. Tickets in on-hold status with an assignee will be automatically reopened in 4 days by the automation
Reopen on-hold tickets after 4 days.
If a customer's reply is the last one in the ticket, do not set it to the On-hold status silently due to the same reasons as stated above in the Zendesk SLA settings and Breach Alerts section. Instead, reply to the ticket while also changing the status.
If you're merging two customer tickets that are related and it's not 100% obvious to the customer, be sure to send a message letting them know why you're merging them. If you don't, it often causes confusion and they open follow ups asking why it was closed without comment.
Additionally, when merging tickets, leave
Requester can see this comment unchecked in the ticket that's being merged into (the second ticket from the top) in order to maintain the SLA. If the merge comment is made public it, Zendesk will consider it a response and will remove the SLA.