diff --git a/content/departments/technical-success/ce/team-culture/team-norms.md b/content/departments/technical-success/ce/team-culture/team-norms.md index 88a5c6147aa2..5fa509c21527 100644 --- a/content/departments/technical-success/ce/team-culture/team-norms.md +++ b/content/departments/technical-success/ce/team-culture/team-norms.md @@ -2,8 +2,8 @@ ## Recurring Team Meetings -- \*\*CE Regional meetings(weekly): Regional team syncs; pre sales teammates discuss their current opportunities and crowdsource how to help advance the deals -- **Global team meeting** (monthly): Top-down communication to the global organization for pre sales +- **Team meeting** (weekly): Regular syncs for the CE team to discuss relevant topics +- **TS Department Meeting** (bi-monthly): Sync for all teams in TS to share progress, updates, wins, and kudos ## OOO Protocols @@ -17,11 +17,14 @@ Prior to taking time off, CEs should: ## CE-Specific Slack Channels -| Slack Channel | Description | -| -------------------------- | -------------------------------------------------------------------------- | -| #team-ce | Internal channel the CE team uses to touch base with each other. | -| #discuss-ce | External channel for other teams to ask CEs a question. | -| #discuss-customer-support | Where support collaborates with everyone outside of support. | -| #discuss-engineering | Where CEs can ask product and Eng questions about Sourcegraph. | -| #feedback | Where CEs can share customer feedback with product. | -| #discuss-technical-success | Where customer-facing technical teams collaborate on questions and issues. | +| Slack Channel | Description | +| ---------------------------- | ------------------------------------------------------------------------------ | +| #team-ce | Internal channel the CE team uses to touch base with each other. | +| #discuss-ce | External channel for other teams to ask CEs a question. | +| #discuss-support-engineering | Where support collaborates with everyone outside of support. | +| #discuss-technical-advisory | Where TA collaborates with everyone outside of TA. | +| #discuss-engineering | Where CEs can ask product and Eng questions about Sourcegraph. | +| #feedback | Where CEs can share customer feedback with product. | +| #discuss-technical-success | Where customer-facing technical teams collaborate on questions and issues. | +| #announce-technical-success | Where important announcements are shared for all teams in Technical Success. | +| #team-technical-success | Where internal TS teams share information relevant primarily to our own teams. | diff --git a/content/departments/technical-success/ce/team-culture/working-with-customers.md b/content/departments/technical-success/ce/team-culture/working-with-customers.md index bdecc774b0fd..204f3084d56d 100644 --- a/content/departments/technical-success/ce/team-culture/working-with-customers.md +++ b/content/departments/technical-success/ce/team-culture/working-with-customers.md @@ -14,6 +14,7 @@ A CE, being both a pre-sales engineer and a post-sales technical account manager - [CE Technical Win Management](#ce-technical-win-management) - [Tech Reviews](#tech-reviews) - [Creating Tickets -Trial Support](#creating-trial-support-tickets) + - [Pre-to-Post Sales Handoff](#pre-to-post-sales-handoff) --- @@ -151,3 +152,21 @@ Ways to add these internal notes: - **Slack:** In Support Agent, under `home` > `Your current chats` > select the dropdown `Options`, and `Add Ticket Notes` - **Zendesk:** In Zendesk, in the view `Trial Customers`, you can select your existing ticket, `Apply Macro`, select `Customer Support Ticket Request`, and add the internal notes. + +## Pre-to-Post Sales Handoff + +A critical last step in the sales process is to hand off the opportunity to the Technical Advisory (post-sales) team. It's important so that we transfer important context about the deal (goals, needs, expectations, etc) and contacts so that the TA team is able to effectively take the relationship forward. + +The overall process is captured [here](../../ta/team-culture/working-with-customers.md#post-sales-handoff). It's most important that CE knows the process is slightly different depending on the [customer segmentation](../../ta/team-culture/team-norms.md#customer-segmentation) and whether they will be managed by a named, dedicated TA or part of our digital, scaled success program. + +Need-to-know's for a named TA account: + +- TA will handle the production license +- CEs are expected to participate in a formal knowledge transfer / hand-off with the TA before the deal closes + - CE should collect relevant information (doc links, channels, etc.) to make for a productive session +- CE should participate in the post-sales kick-off call; after that, CE should roll off of the account until / unless there is an active expansion opportunity. + +Need-to-know's for a digital, scaled success account: + +- CE must handle the production license, and if a separate production cloud instance is required, should handle the creation request of that. +- CE, as part of hand-off, should map the approproiate roles on the contacts in Salesforce. See role definitions [here, step 7](../../ta/team-culture/working-with-customers.md#process-overview).