Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Account Onboarding

Technical Account Management Handbook

On this page

Customer Onboarding

When a customer with the Gemstone Ruby or above purchases or upgrades GitLab, an onboarding object is automatically created.

The Technical Account Management team are subscribed to a Customer Onboarding Report in Salesforce which is sent every Monday. If new accounts have joined, the Technical Account Management Leader should align the account with a Technical Account Manager and kick off the customer's onboarding process. Due to the nature of Salesforce automations, and this being an early iteration, it is up to the TAM Leader to regularly clean up this report by deleting any duplicates.

Handy tip: In order to delete an onboarding object, you must first make yourself the owner of it.

If an account moves into a higher Gemstone category from a lower category, the same process should be followed. AKA Ruby or Sapphire to Pearl or Diamond. These are usually significant enough upgrades to warrant a dedicated Technical Account Manager and a fresh onboarding experience.

It doesn't matter who the Onboarding object owner is as long as the Technical Account Manager field is completed on the object. The object owner will usually be auto-generated and doesn't mean anything.

Once an account has been assigned to a Technical Account Manager, they must open an onboarding issue in the Customer Onboarding GitLab project. When you open a new issue in the project, you will be presented with instructions.

This project is internal only (not customer-facing) and is to help and guide Technical Account Managers in working through their customer onboarding properly with each customer. It also provides a platform for communication outside of Salesforce to pull in other members of the GitLab team for discussion if needed. You must complete all tasks within the issue in order to close it, and the onboarding object in Salesforce cannot be closed until this issue is completed. Do not skip steps. If you need help, please ask your leader and your team for support and guidance.

The onboarding object must be completed in parallel to the issue as Salesforce is our single source of truth and the fields in the object can be reported upon for historical context and metrics.

The onboarding object status and date time-box must be updated as quickly as possible upon account assignment. This is important for reporting purposes.

In order to complete the onboarding object, the onboarding survey must be sent to the customer. Be sure to send a personalised email to the team of people in the customer's organization that you have been working with throughout the onboarding time-box: Here is the link to the survey.

When the onboarding is complete, the Technical Account Manager will either continue to work with the customer permanently if they are so aligned or the account will be transitioned to a new Technical Account Manager if the previous Technical Account Manager was just stepping in to provide onboarding support to our customer base. It is important that all of our customers are properly onboarded in order to improve retention and ensure the best customer experience possible.

Customer Support

GitLab offers a variety of support options for all customers and users on both paid and free tiers. For customers on Standard and Priority support tiers please address the below items when submitting a support ticket:

  1. Provide as much detail as possible during the first submission of the ticket

  2. Summary of issue (when did it start, how frequently, impact on organization, etc.)
    • Detailed steps to recreate
    • Current behavior
    • Expected behavior
    • Any recent changes to Gitlab, its components, dependencies, or the services it's hosted on?
    • Attach logs and screenshots (avoid attaching .doc or .pdf files)
  3. Try and avoid requesting a call during the initial ticket submission. We would like to keep all communication within the ticket and attempt to resolve the issue here before going to a call.

  4. If a call is necessary, the support engineer will invite your team to a call via the ticket

  5. If a support engineer requests follow up items, please make sure to respond back with these items. This will help us resolve the issue as quickly as possible