The Support Operations team maintains the day-to-day operations and software systems used by GitLab’s global Technical Support team.
At GitLab, CSAT is a measure of how satisfied our customers' are with their interaction with the GitLab Support team. This is based on survey responses from customers after each ticket is solved by the Support team using a Good or Bad rating.
The target is 95% customer satisfaction. The definition of the KPI is:
Satisfied [total good scores] / Total Survey Responses [good scores + bad scores]
This calculation excludes cases where a survey was not offered or where it was offered but no score was provided.
The survey is sent out 24 hours after a ticket is solved. The tag
csat_survey_sent is added to a ticket as soon as a survey is sent out.
There are a few reasons why a customer wouldn’t receive a CSAT Survey after a ticket has been solved:
Starting July 9th, 2019, in order to learn about the reasons behind a bad satisfaction rating, we ask any customer who gives a negative survey response to select a reason for their dissatisfaction. This feedback is shared with the Product team and the Support Managers, depending on which reason is chosen. The dropdown options are:
All negative and positive feedback with comment is exported to an internal repository. Once the feedback has been submitted, an Issue is created and the Support Engineering Managers are tagged when a negative rating has been submitted. It is the responsibility of the Support Engineering Managers to investigate the feedback and ensure appropriate actions are taken to either resolve the root cause of the negative experience or reduce the likelihood of it recurring.
We have the option of allowing all of the end-users in an organization to see each other's tickets. This is referred to as a shared organization in Zendesk.
We can grant the end-users permissions to see the tickets at the organization level and the personal level (personal level overrides org level). This means that at the personal level, we can allow selected individuals in an org to access all the tickets created by members of their org or we can allow everyone in the company to see everyone's tickets.
Shared organizations will only be set up if we receive a request directly from the customer through a Support Ticket. Once the ticket is created, any member of the Customer Success or Support teams can create a request in the Support Ops project using the
Shared Organization Request template, and any member of the Support Team can update the organization settings once the issue is created.
There are a few different options available for our customers:
We have enabled Zendesk to send all ticket information to Salesforce using a target. Currently, we create a Salesforce Zendesk Ticket record whenever a ticket is created and when it is solved by one of our agents or an automation. Once the information is received in Salesforce, a notification is sent from SFDC to the Technical Account Managers so they are aware of the issues their accounts are experiencing.
To troubleshoot any issues with this functionality, we need to make sure that:
Use auto-matching criteria for searching Salesforce records
Zendesk Support Ticketand
Zendesk Support Ticket Commentis visible to the
When working on the Salesforce side of this configuration, make sure to always communicate with the Sales Systems and Operations team about any inconsistencies you find and request their help to troubleshoot any issues.
All organizations in Zendesk are created through our Salesforce Integration. Currently, only records with Account Type equal to
Customer are synced from Salesforce to Zendesk.
Accounts are synced with Organizations as long as the
Account ID in SFDC matches the one
Salesforce ID in Zendesk and the
Zendesk Support Organization ID in SFDC matches the
Zendesk Organization ID in Zendesk.
We have configured custom field mappings:
A script was created by the Support Team in order to do routine checks of data integrity between Salesforce and Zendesk. This script runs daily and it checks for:
missingzendeskorg_dotcom.rb) and Self-Managed Customers (
The premium breach notifications is a webhook that is triggered by a ZenDesk automation titled
Premium important ticket slack notification. The trigger looks for any
high premium tagged tickets that have less than 2 hours left on the breach clock.
The automation runs at the top of every hour
and due to this limitation, it does not run at the exact hour the ticket is less than 2 hour from breaching.
Once the ticket is updated, a trigger sends a webhook to slack which is configured on the slack side.
#zd-self-managed-feed channel is updated by a webhook that's triggered whenever a Self-Managed ticket is created or updated. The Zendesk trigger is called "Slack Support Live Feed (With Organization names)"
#zd-self-managed-feed channel does not display tickets addressed to GitLab.com or
#zd-gitlab-com-feed channel is updated by a webhook that's triggered whenever a GitLab.com ticket is created or updated. The Zendesk trigger is called "Slack Services Live Feed". This channel does not display EE tickets.
The Supportbot shares status of Zendesk views and number of tickets in Slack when invoked.