The Handoff Email When One Staff Member Passes a Client to Another

A staff handoff is one of those moments that feels internal but is actually completely external - the client doesn't care about your org chart, they care about whether the person who now knows their account actually knows their account 💖. Get the email wrong and even a smooth internal transition feels, from the outside, like the client's been quietly downgraded to "someone new figuring it out."

What most businesses get wrong

The most common mistake is sending the handoff as an announcement instead of a conversation - a one-way "just letting you know Sarah will now be looking after your account" email that reads like a form letter. It answers "who" but not "why should I feel fine about this," the only question the client actually has.

The second mistake is letting only one side send it. Just the departing staff member writes it, and it reads like an apology or a goodbye. Just the new person writes it, and it feels like a cold intro with no vouching behind it. The email needs both voices - the outgoing person handing over trust, and the incoming person showing they've done their homework.

How this plays out in practice

The mechanics: how to actually do this

Time it before, not after

Send the handoff email before the new person's first contact with the client, with enough notice that it doesn't feel rushed. A client who hears about a change from the new person cold will always wonder what else they weren't told.

Write an internal brief the client never sees

Before the email goes out, the outgoing person should hand the incoming person a short brief: what the client cares about, any sensitivities, any commitments already made, and how they like to communicate. This is what makes "I know your situation" true rather than performative.

Set a follow-up touchpoint

Build in a short check-in from the new person within the first couple of weeks - not a sales call, just a "how's this feeling" moment. It confirms the handoff landed and gives the client an easy way to flag anything that fell through the cracks.

Mistakes to avoid

• Sending the handoff from only one side instead of both people together.
• Making the client re-explain context that's already been documented internally.
• Waiting until the change has already happened to mention it.
• Using a generic template with no specific, genuine detail about the client's situation.
• Skipping the internal brief and expecting the new person to "figure it out" from the file.

Frequently asked questions

Should the outgoing staff member stay involved after the handoff email goes out?

It depends on the depth of the relationship. For a short project, a clean break after one follow-up message is usually fine. For a long-term or high-value client, staying cc'd on the first exchange or two - without inserting yourself into the work - can smooth the transition. There's a real trade-off: too much lingering involvement can undercut the new person's authority just as easily as too little can leave the client feeling dropped.

What if the handoff is happening because of a performance issue, not just a normal reshuffle?

Keep the email focused on the client's experience going forward, not the internal reason. The client doesn't need - and generally shouldn't get - details about why the change happened.

Should this go by email or would a phone call be better for bigger accounts?

For your highest-value or most sensitive accounts, a call with the email as written follow-up is usually worth the extra time. For most accounts, a well-written email covers it.

How much detail is too much in the context recap?

Enough to show continuity, not so much it reads like a file dump. One to three sentences covering where things stand and what's next is usually right.

Keep reading 🤍

• How to Introduce a New Team Member Without It Reading Like HR News
• Seasonal and Temp Staff Onboarding: Keeping Your Brand Voice Consistent
• Founder-Led Sales to Delegated Sales: The Trust Handover