What Should the First Email From the New CSM Say After the Handoff?

The customer reads your first email against one question: do these people talk to each other. They went through discovery, a demo, a proposal and a pricing call, and they told your company what they want at least three times. The r/CustomerSuccess threads on the handoff describe what happens when the email fails that test.

Of the 946 r/CustomerSuccess threads we read, 30 are about a handoff or handover, and 17 mention a customer repeating themselves, starting over, or answering a question they had already answered. One of them is a single sentence from a customer, said mid-meeting.

The first email is where you pass or fail that test in writing, before anyone has met you. Every line that shows you know what happened buys you a reply; every question you could have answered from the handoff doc costs you one. The sequence the email opens is covered in customer onboarding best practices; this page is only the first message, because the first message decides how the rest are read.

The email has four jobs and a length limit. Under 150 words, because the sponsor reads it on a phone between meetings and the day-to-day owner forwards it to their team. Anything longer is a document, and documents get filed.

Two rules on the envelope. Send it from your own address, not a shared inbox and not a sequence tool; the customer will reply to it, and a reply that lands in a queue is a reply nobody owns. Copy the AE on this one email and drop them from the thread after it, so the customer sees the handover happen and stops emailing the person who sold to them.

Timing: within one working day of the handoff call, and never before it. An email sent before the AE has confirmed the goal line is a guess dressed as knowledge, and the customer will see the seam. If the AE sends their own two-line introduction on the day of the handoff, yours follows it; two introductions from the AE, or yours arriving first, both read as a team that has not agreed who is doing what.

Most first emails fail by addition. This list comes from the emails CSMs in our corpus describe sending, and from what customers in the same threads say they ignore.

• Your career history and how excited you are. The customer has a project and a deadline; your enthusiasm is not information.
• Any question the handoff doc answers. Who is on the team, what they are trying to achieve, what they used before, when they need to be live. Asking these tells the customer the doc does not exist.
• A list of resources: the help centre, the community, the webinar calendar, the status page. One link at most, and only if it is the next step.
• Feature tours. 'You will love the dashboard' is a demo, and the customer has had the demo.
• Merge-field prose. 'Hi FIRSTNAME, welcome to COMPANY' is a form letter even when the fields fill correctly, because the sentence around them could go to anyone.
• A promise you cannot date. 'We will get you live in no time' is worse than silence. If the go-live date is not agreed yet, say when it will be.

The clean test is to strip your name off the draft and ask whether the customer could tell it was written for them. If not, the email is a template with a name on it, and it reads that way on their side.

The same four parts, in three situations. They are written in plain prose so you can send them after changing the specifics; the words in square brackets are the specifics. The names, figures and dates are illustrations.

The first row is the one CSMs skip when they are in a hurry, and it is the one the customer notices. Among 3,628 public G2 reviews of the three most-reviewed customer success platforms, 18 mention email templates and 30 mention handoffs or transitions; the reviewers who wanted templates wanted speed, and the reviewers who wanted handoffs wanted context. The first row is where context has to be typed by a person, every time, because it is the only row a template cannot fill.

A first email with a date in it gets a reply most of the time, because a proposed slot is easy to accept or move. When it does not, the sequence is short and it escalates through people, not through more email.

1. 1

   Day 3: one reply to your own email

   Reply in the same thread so the context is one scroll up. Two sentences: the slot is still open, and one new piece of information (the draft plan is attached, or the routing rules are in). No 'just checking in'.

2. 2

   Day 5: call the day-to-day owner

   The person who will use the product, not the sponsor. A missed call with a 20-second voicemail that names the date you are trying to protect does more than a third email.

3. 3

   Day 7: ask the AE to send one message to the sponsor

   The AE's relationship is still the warmer one in week one. The message is about the date at risk, not about you: 'we are trying to hold 24 October and need 20 minutes from your team this week'.

4. 4

   Day 10: put the slipping date in writing

   Tell the sponsor what happens to the go-live if the kickoff moves, and offer the new date. A customer who sees the consequence usually finds the 20 minutes. If they do not, the account goes on the no-show playbook.

5. 5

   Do not send a fourth email

   After day 10, more email trains the customer to ignore you. Silence in week two after a purchase is a signal, and customers not showing up to onboarding covers what to do with it. Silence later in the life of the account is a different problem, on customer went quiet.

Three replies mean the email did its job and surfaced a problem early. Each has a right next move.

• 'We were told X would be included.' The email restated the goal and the customer added a promise you did not know about. Do not answer it in email. Check the handoff doc, then the call recording, and follow what to do when a customer says a feature was promised. Reply the same day to say you are checking, with a date for the answer.
• 'Please deal with my colleague from now on.' The sponsor has delegated. Good: you now know the day-to-day owner. Reply to both, thank the sponsor, and send the colleague the same four parts in a fresh email, because the forwarded version has lost the subject line and half the context.
• 'Can we push the kickoff to next month?' The deadline in your email was not theirs, or their side is not ready. Ask which. If the date has moved on their side, move it and say what the new go-live becomes. If nobody on their side has been assigned, that is the risk to raise with the AE now, not in month two.

The reply to worry about is the polite one with no date in it: 'thanks, we will be in touch'. Treat it as no reply and start the day-3 sequence. When the account came through an implementation team rather than straight from sales, the first email follows a live introduction instead of a handoff call, and the sequence is on the implementation to CSM handoff.

GainTrace pulls the contract, the contacts and the handoff notes onto one account record, so the goal line and the promises are in front of you when you write. After you send, product signals show whether the day-to-day owner you named has signed in and whether the first outcome is moving, and customer success on GainTrace turns a missed kickoff or a day-3 silence into a task with a date and an owner, without anyone building a workflow.