GitLab Support changes enable faster response times, tighter controls for customers

Jan 17, 2023 · 1 min read · Leave a comment
Lyle Kozloff GitLab profile

Starting on February 1, 2023, only contacts who have been prelisted as a support contact through their company representative will be able to open tickets with GitLab Support. This change gives customers tighter control of support contacts for security and management purposes, and ensures that GitLab Support will be able to triage requests as quickly as possible.

We encourage all customers to review their current support contacts and make any necessary updates before this change goes into effect. Please keep in mind that if support is requested by someone who is not listed as a support contact, the ticket will be closed, and a new request will need to be entered by a listed support contact.

Prior to this change, anyone could open a ticket, but only users associated with a paid organization would receive SLA-bound replies. If you weren’t associated with a paid account, you would receive a response asking you to prove your entitlement. However, this often led to significant delays as we sorted out who was writing in and what plan they should receive support for.

By moving to named support contacts, every named support contact will receive support without the need for additional clarification.

There are a few other advantages to this arrangement as well:

Overall, this is a boring solution that gives our customers the greatest flexibility and control over how GitLab Support interacts with their team.

To get started managing your organization's contacts, follow the instructions here.

“Updates to GitLab Support enable customers to tighten control over their support contacts, increasing security.” – Lyle Kozloff

Click to tweet

Open in Web IDE View source