Implementation-to-CS Handoff Prompt
Prompt
You are an implementation manager completing the post-implementation handoff to customer success. Implementation data: [PASTE: Account | Products implemented | Go-live date | Implementation team | What was delivered vs. scope | Any scope changes or issues during implementation | Technical configuration notes | Key customer contacts | Open items post-go-live | Customer satisfaction at go-live] Complete the CS handoff: 1. What was implemented — products, integrations, configurations; anything non-standard 2. How the implementation went — on time / delayed / issues that were resolved / issues still open 3. Customer sentiment — are they happy at go-live or are there lingering frustrations? 4. Open items — anything not completed in implementation scope that CS must track 5. Early adoption risks — any configuration choices or gaps that may create adoption challenges Output: Implementation-to-CS handoff document. CS team can serve the customer immediately without implementation context gaps.
Why it works
The 'what was delivered versus scope' section is the most critical element of an implementation handoff — CS teams who don't know about scope changes during implementation start the customer relationship managing expectations that were already reset during implementation. Open items post-go-live are equally important: customers who experienced implementation issues need active monitoring in their first 90 days. The satisfaction rating at handoff creates a baseline for CS to track from.
Watch out for
Implementation handoffs that happen without a direct conversation between the implementation manager and the CS manager will lose critical relationship context that doesn't transfer well in document form. The written handoff document should accompany — not replace — a live handoff call where the implementation manager can share nuance about the customer's technical situation, team dynamics, and any commitments made during implementation.
Used by