In the Customer Success space, there are many discussions around nailing handoffs between sales-to-customer-onboarding and onboarding-to-success teams. However, the transitioning of customers between CSMs is a rarely discussed topic.
The handoff typically happens because:
- A new CSM is being onboarded
- The existing CSM has been promoted or is changing teams
- The existing CSM is underperforming
- The client’s organization is growing
- The existing CSM’s workload needs reducing
Making this transition happen is tricky, as it can break the customer-CSM relationship.
So, how to ensure that the transition of accounts between CSMs happens smoothly? We asked Preflighters to share practical suggestions to make the handoff smooth.
Aditya shares their handover process for a high-touch engagement model. This elaborate handover has four major steps:
1. Handover document
This document is prepared by the CSM handing over the client. It covers the business metrics and KPIs important to the customer and indicates any special technical integrations in place. The document also lists the stakeholders involved on the client side and the relationship with them.
Past engagement details, including the last QBR, executive relationships, product adoption status, and what needs to be done next with the customers, must also be mentioned.
2. Account context meeting
The old CSM walks the new CSM through the handover doc and answers any follow-up questions they might have during the meeting.
The new CSM is introduced to the customer, and the change/reason for leaving is communicated via email. It’s also important to mention whether the former CSM will continue to aid the client.
Include a line about the new CSM that can help build credibility, such as “<person> has over 11 years of experience working at the intersection of cutting-edge technology and client servicing. Before X, he has worked in companies like A, B, and C and will be able to add a lot of value to your growth strategies.”
4. Ongoing support
The former CSM must support the new CSM for the first few weeks until the new CSM is fully comfortable with the account, people, and technical details.
Ensure that the new CSM doesn’t have to do the same amount of groundwork already put in by the previous CSM.
Here’s a checklist of items for CSM-to-CSM handovers:
- Stakeholder + relationships analysis (along with their predisposition towards our solution)
- History of incidents for the account
- Joint success plan
- Adoption status
- Request tracker (if any)
- The last 2 QBR decks, key takeaways from each + any business metrics, KPIs tracked
- Last five communication threads + last five meeting notes
- Any workarounds, specific configurations, customizations followed for the customer, and history of problems from those
- Ongoing conversations and deadlines
Here's the process Whatfix follows:
- Using Google Drive folders to maintain a customer repository in a shared drive space that contains all the key docs such as the MSA, kickoff, sales handoff, PO, invoices, EBRs, etc. The former CSM shares the specific customer folder with the new one.
- Each CSM has to update the customer success tool with the latest pulse. Emails are auto-synced, pulse updates are done every couple of weeks, with an account summary added and updated by the former CSM.
- The new CSM must go through the CS tool and folder before setting up the internal handover call.
- The former CSM should do a warm handover with the customer and, if time permits, join a couple of subsequent calls as well
- Handoff Timeline: 2 - 3 weeks ideally. At least one week to cover until the warm handover.
- Apart from the warm handoff, this usually takes 1 - 2 internal calls and 1 hour of tool and doc review per customer.
- MSA, invoices, and other contracts in the drive
- All engagements/emails synced
- Key engagement collateral such as kickoff, EBRs, sales handoff, etc. in the drive
- A summary of recent issues (6 months usually) + ongoing issues + RCA/links to Jira
- Overall pulse of the account, the pulse of each stakeholder towards the product and team
- List of commitments made, blockers, renewal probability, risks documented
- History of advocacy engagements (if any)
- Technical documentation - workarounds, setup details, customer application access creds (if your product needs it), etc.
If you want to learn more about Customer Onboarding, Implementation, and Professional Services in-depth, join the Preflight Community.
- Implementation Stories
- Preflight Conversations
- The Launch Station - a podcast for all things customer onboarding
- Customer onboarding resources from Rocketlane
Industry insights you won’t delete. Delivered to your inbox weekly.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.