As a member of the pre-sales team, closing another successful deal for GitLab, it is important to pave the way for the CSM. A successful CSM introduction is a critical step in the customer lifecycle. An effective CSM introduction will lead to customer excitement about the product and increase the CSM's credibility as they assist the customer through onboarding, implementation, and adoption.
<!-- NOTE: This course probably needs to be checked to ensure it's not conflicting with the new guidelines -->
Please review this course on [Introducing the Customer Success Manager](https://university.gitlab.com/courses/introducing-the-technical-account-manager).
@@ -48,6 +48,6 @@ A table showing coverage for queries by subject matter is available for internal
### Consider these additional guidelines
It is worth considering the [privilege guidelines](/handbook/legal/risk-management-dispute-resolution/#privilege) when communicating with GitLab's Legal and Corporate Affairs team (aka the LACA team), including the Legal Employment team. Note that, if a communication is privileged, it can be protected from disclosure in litigation or other disputes. If in doubt, there’s an internal, GitLab University micro course on [‘Privileged communication’](https://university.gitlab.com/courses/attorney-client-privilege), which is relevant to any team member who communicates with the LACA team, seeking legal advice on behalf of GitLab. The training explains the legal protection which may be applied to certain communications between team members and LACA and how best to communicate in order to be protected.
It is worth considering the [privilege guidelines](/handbook/legal/risk-management-dispute-resolution/#privilege) when communicating with GitLab's Legal and Corporate Affairs team (aka the LACA team), including the Legal Employment team. Note that, if a communication is privileged, it can be protected from disclosure in litigation or other disputes.
It is also important to note that, if you receive any formal documents that appear to be legal notices, demands, subpoenas, court papers, or other potential litigation materials, you should please forward these by email to the legal team immediately (to the 'legal@gitlab.com' email address) without responding yourself. Please add a brief note explaining when and how you received the document. These materials often have strict response deadlines, and your prompt sharing allows the legal team to review and address them properly to protect both you and GitLab.
@@ -5,7 +5,7 @@ description: "The Command Plan is how GitLab has operationalized a customer valu
## Overview
The Command Plan is how GitLab has operationalized [Command of the Message](/handbook/sales/command-of-the-message/)(*a customer value-driven sales methodology*) and [MEDDPPICC](/handbook/sales/meddppicc/) (*a proven methodology used for strategic opportunity management and complex sales process orchestration for enterprise organizations*) into the opportunity management process. Access the [Effective Command Plans to Help You Win More Deals](https://university.gitlab.com/access/saml/login/internal-team-members?returnTo=https://university.gitlab.com/learn/course/sal-effective-command-plans-to-help-you-win-more-deals) e-learning course for ENT or [Strategic Opportunity Management](https://university.gitlab.com/learn/course/strategic-opportunity-management-the-process/main/strategic-opportunity-management-the-process?client=internal-team-members&page=6) for Commercial.
The Command Plan is how GitLab has operationalized [Command of the Message](/handbook/sales/command-of-the-message/)(*a customer value-driven sales methodology*) and [MEDDPPICC](/handbook/sales/meddppicc/) (*a proven methodology used for strategic opportunity management and complex sales process orchestration for enterprise organizations*) into the opportunity management process.
@@ -216,8 +216,6 @@ Please take a moment to answer the questions in this short [quiz.](https://docs.
- Check out the [slide deck](https://drive.google.com/open?id=1UCRF6PC6al8XxT8E_4rDKkQjkW6WGPA6gybWeuRIg7A&authuser=0) on creating a great profile that will look good to your prospects and clients!
-[Learn how to create](/handbook/sales/field-operations/order-processing/) Accounts, Contacts, Opportunities, and [Quotes](/handbook/sales/field-operations/sales-operations/deal-desk/#zuora-quote-configuration-guide---standard-quotes) in Salesforce.
-**Lead Scoring - Filtering Prospects in Salesforce (FOR SALES ONLY - Material - Level Up Video Course - 20 minutes)**
-[Lead Scoring - How Does It Work?](https://university.gitlab.com/access/saml/login/internal-team-members?returnTo=https://university.gitlab.com/learn/course/lead-scoring-training) Learn the fundamentals of lead scoring and how to use lead score classifications
-**Reference Edge (Material - Video - 10 Minutes)**
- Reference Edge Software will help reps to easily see what available references are the best fit for their current opportunity. Check out the [video](/handbook/sales/training/#functional-and-technical-skills--processes), and [Powerpoint](https://docs.google.com/presentation/d/18odHX0PTzifRJaeAr-yxa9jdg1_nw4RYDiBqAkYFAyM/edit?usp=sharing) on this new tool.
@@ -233,8 +231,6 @@ Please take a moment to answer the questions in this short [quiz.](https://docs.
-**The GitLab Legal Team (Material - Handbook - 10 Minutes)**
- Familiarize yourself with submitting Contract Requests for Legal/Contract assistance. [Presentation](https://docs.google.com/presentation/d/1lesWNvPAFd1B3RuCgKsqQlE85ZEwLuE01QpVAKPhQKw/edit#slide=id.g5d6196cc9d_2_0), [Video](https://www.youtube.com/watch?v=CIWdsqRX7E0&=&feature=youtu.be) and [Handbook Page](/handbook/sales/field-operations/order-processing/#process-for-agreement-terms-negotiations-when-applicable-and-contacting-legal)
- You can reach out to the [Legal Team](/handbook/legal/) on the #legal Slack chat channel. The legal Slack chat channel is reserved for everyday legal questions. If you are making a request that requires some sort of deliverable, please do not use the legal Slack chat channel. Slack is reserved for immediate, informal communications. Also, please do not share confidential information on Slack that is not meant for the entire company to see, and do not use it to seek legal advice. You can email the legal team at legal@gitlab.com.
-**Support for GitLab Team Members (Material - Handbook - 10 Minutes)**
-[GitLab Support](/handbook/support/internal-support/#what-does-the-support-team-do) provides technical support to our Self-managed and GitLab.com customers for the GitLab product. We are not internal IT Support, so we probably can't help you with your MacBook, 1Password or similar issues.
- Watch the [video](https://www.youtube.com/watch?v=Mi3dtKxypkA&feature=youtu.be), check out the [handbook](/handbook/alliances/) page, and [slides](https://docs.google.com/presentation/d/1iSW8-h6nVaqIdHm5jJZqRrHMB-GCiOe-9ODFo0oke4E/edit?usp=sharing) to understand how we parter with other companies to accelerate GitLab's trajectory by connecting the great work every team is doing with the outside world.
@@ -257,9 +253,6 @@ Please take a moment to answer the questions in this short [quiz.](https://docs.
- Check out this [Slack workflow](/handbook/support/internal-support/#i-want-to-escalate-a-ticket) if you have to escalate a ticket for a customer to understand the expectations around it.
- Read the [Trials and Prospect Support](/handbook/support/internal-support/#trials-and-prospect-support) workflow that should be followed for prospects looking to evaluate Support experience.
- Make note of Support's [internal-requests](https://gitlab.com/gitlab-com/support/internal-requests) project - you will be filing issues under this for some of the workflows listed in the above page.
-**Review the Zendesk Workflow (Material - Handbook - 15 minutes)**
- Zendesk is the tool the GitLab Support Team uses to work tickets for customers. Please familiarize yourself with the associated workflows.
- Review the workflows in this section of the [Handbook](/handbook/support/workflows/#zendesk).
-**Sign up for Zendesk (Assignment - 5 Minutes - 10 Points - Pre Work)**
- All GitLab staff can request a 'Light Agent' account so that you can see customer tickets in Zendesk and leave notes for the Support team.
- To do so, follow the process outlined in the [handbook](/handbook/support/internal-support/#requesting-a-zendesk-light-agent-account). Once the account is created, you'll need to wait 24 hours for it to be assigned in Okta. Once Zendesk is assigned, you should be able to login to Zendesk at https://gitlab.zendesk.com/agent.
@@ -281,8 +274,6 @@ Please take a moment to answer the questions in this short [quiz.](https://docs.
- Please work in small groups to fill out the [attached assignment](https://docs.google.com/document/d/1V2yMIaHvp_s1RzSlsAR2_AsExSloyLKbVuSlqVkbufg/edit?usp=sharing) on defensible differentiators.
-**Searching GitLab Like a Pro (Assignment - 10 Minutes - 10 Points - In-Class)**
- At GitLab, we're prolific at documenting what we do in the handbook, the website, and in GitLab documentation. This may make it difficult to find specific pieces of content. Google already indexes all our public facing pages and there is a search modifier google offers that will help. Take a look at the handbook page on how to [set up your search engine like the pros!](/handbook/tools-and-tips/searching/)
- Please submit your notes from one of the role plays that you observed using the [notes template](https://docs.google.com/document/d/1bzuO-ngACn4Z1S55Z7EtNOb2HYCZbcBZZRYIVpkeMtw/edit?usp=sharing). Dont forget to check out the [handbook page](/handbook/sales/#sales-note-taking) on how we take notes at GitLab.