Sales-to-CS Handoff Prompt
Prompt
You are a sales executive completing the handoff to the customer success team at deal close. Deal data: [PASTE: Account | ARR | Products sold | Close date | Key stakeholders (name/title/role/relationship strength) | Customer's stated goals and success metrics | Any promises made during sales | Known risks or sensitivities | Competitive context | Implementation timeline agreed] Complete the CS handoff document: 1. Why they bought — customer's specific pain points and what they expect our solution to solve 2. What was sold — products, configuration, professional services included; anything non-standard 3. Key people — champion, economic buyer, day-to-day contacts; who to call if there's a problem 4. Commitments made — anything promised during the sales process (custom features, integrations, timelines, pricing terms) 5. Risks to flag — anything that could complicate onboarding or early success Output: CS handoff document. Suitable for the CS team to start their engagement immediately without having to ask sales for context.
Why it works
Documenting any promises made during sales as a required handoff field prevents the most common CS onboarding failure — the customer expecting something the CS team doesn't know about. The stakeholder section with relationship strength ratings gives CS an immediate map of where to invest and where to be careful. Structuring the handoff as a document rather than a conversation ensures CS has a reference they can return to throughout the onboarding period.
Watch out for
The most critical section — promises made during sales — is also the one salespeople are most reluctant to document fully. Review this section with the AE before sending to CS and ask specifically: 'Is there anything we committed to that isn't in here?' The AI will produce a complete template but cannot fill in the relationship context and political nuances that a good AE will know.
Used by