This page is intended for Partner Help Desk specialists to document and review processes and procedures, as well as anyone looking for information on what the team handles and how to contact us.
If you are a channel or sales team member looking for easy-to-read information and links, please visit the Partner Support page.
Channel Managers are managed differently depending on the region they are in.
When there are changes to each channel team, the corresponding PHD Specialist should create an MR with the update. The Channel Marketing team updates the CAMs in Impartner.
When updating the Account Owner on a partner account, make sure to also update the Contracted Territories
field.
GitLab Partner Program Info
, check to make sure the “Public Sector Partner” field is set to “No.” (Unless the account is US PubSec.)Change Account Owner
button at the top of the record.(How to tell which Channel Manager is assigned to an Opportunity)
In the CAM Mapping FY23 spreadsheet (“Mapping Tables” tab), (Non-US PubSec or Alliance) Channel Managers are mapped first by the Opp Owner’s User Data using the field [Deprecated] Owner Segment-Geo-Region-Area,
and then secondarily by the field Stamped Account Sales Territory.
These fields are found in the 'Comp and Attainment Information` section of an opportunity.
When determining which Channel Manager is mapped to an opportunity, First look up the [Deprecated] Owner Segment-Geo-Region-Area
field. If there’s a Channel Manager listed, that is the Channel Manager for the opportunity. If, instead of a Channel Manager, it says “Look at Territory,” then refer to the Stamped Account Sales Territory
column. That name will be the Channel Manager for the opportunity.
US PubSec and Alliance Channel Managers are mapped according to the partner and are listed on the two left-hand sections of the same spreadsheet. If the partner account is a GSI, use the GSI lookup columns on the far right of the spreadsheet.
As of FY23Q4, there should not be any resellers sending quote requests, orders, or order status requests to the Partner Support email box. Partners should be sending these to the Sales person or CAM assigned to their opportunity (see the Channel Ops handbook if you need to provide a link to Sales).
If the partner doesn't know who that is or who to send their request to, they can then email Partner Order Operations (partnerorderops@gitlab.com). The Common Response Template has been updated with scripts for various scenarios, explained below with the complete process for each.
Reply using the response from the Common Response Template. No additional steps are necessary.
More information to come soon!
To help a partner confirm what version their SaaS NFR is running, direct them to the “Group Billing Page.” They can navigate to their billing page with the following url: https://gitlab.com/groups/[The Partner’s Specific Namespace]/-/billings More information can be found in View your GitLab SaaS subscription
If a CAM needs help requesting additional minutes for a Partner’s SaaS NFR, please refer them to the NFR Requests for GitLab SaaS document. The Partner Help Desk is not enabled to handle or process requests for more minutes.
More information to come soon!
Partner invoices can be found on the Partner Account Record in SFDC under Invoices.
It helps to either have the date of the transaction and/or when the related opportunity was Closed-Won in the system.
Operational instructions for the Partner Help Desk's role in Service Attach PoEs can be found on the Channel Operations handbook page.
When a partner emails partnersupport@gitlab.com with a Statement of Work (SOW) or Proof of Execution (PoE):
Status
from "Approved" to "Closed-Won"Linked Opportunity
and chatter the Channel Manager who approved the Deal Registration
More information to come soon!
Copy for Family & Friends Days:
Thank you for contacting GitLab Partner Support! GitLab is closed [insert date] for a Family and Friends Day. All emails will be responded to in the order in which they were received upon our return.
Please link “Family and Friends Day” to https://about.gitlab.com/company/family-and-friends-day/
Example for offsites / SKO, etc: Thank you for contacting GitLab Partner Support! Our team is currently attending an internal offsite meeting [insert dates], so please expect our responses to be delayed.