Account Manager Handover Email to a Client: 8 Templates

The short answer
Send the handover email as a joint note from outgoing and incoming account managers, at least a week before the change, copying the client. State the handover date, what stays the same (pricing, contract, support), who to contact starting when, and one open item the new manager is already tracking. Follow up once if the client doesn't reply within three business days.
8 copy-paste account manager handover email templates, including the hard version: handing over an unhappy client.
On this page
- 01When to send this
- 02What a good one contains
- 03The templates
- 041. The joint handover email (default choice)
- 052. The outgoing manager's goodbye
- 063. The incoming manager's introduction
- 074. The internal context summary (for the new owner, not the client)
- 085. The first-90-days plan (sent to the client)
- 096. The mid-project handover (a project is actively in flight)
- 107. The delayed-notice email (change already happened, telling them late)
- 118. The reassurance follow-up (client hasn't responded)
- 12The hard version of this situation
- 13Template: handing over an unhappy account
- 14What to do if there's no reply
- 15A faster way to keep handovers from slipping
A client finding out their account manager left from an auto-reply is the fastest way to make them nervous about the account. The fix isn't complicated: a clear email, sent early enough, that says what's changing, what isn't, and who to talk to now.
Below are eight templates covering the situations that actually come up — the outgoing manager's note, the incoming manager's introduction, the joint version most teams should default to, a context summary for internal handoff, a first-90-days plan, and the one that's actually hard to write: handing over an account that isn't going well.
When to send this#
Send it as soon as the change is confirmed internally — not the day it happens. For a planned departure or promotion, that's usually 1–2 weeks out. For an unplanned exit, send it the same day the client's new contact is assigned, even if the full transition plan isn't ready yet. A short "here's what's happening, more details Thursday" email beats silence.
The one exception: don't send anything to the client before the outgoing employee has been told internally and, where relevant, before HR has finished its process. Timing the client email around your own team's timeline is not being slow — it's not creating a situation where the client knows before the departing person does.
What a good one contains#
- The handover date — the exact day the new contact takes over, not "soon"
- Who's incoming, with one line on their background relevant to this account
- What doesn't change — pricing, contract terms, support channels, SLAs
- A named open item or two, so the client doesn't have to re-explain their history
- A clear next step — reply to confirm, or a call on the calendar
- One sender the client can reach if anything falls through the cracks during the switch
The templates#
Use the joint version by default — it's the one clients respond to best, because it comes from both people at once and reads as an orderly handoff rather than one person quietly disappearing. The rest cover situations where a joint email isn't possible or isn't enough.
1. The joint handover email (default choice)#
Subject: A change to your account team
Hi [CLIENT NAME],
We wanted you to hear this directly from us: starting [HANDOVER DATE], [INCOMING NAME] will be your account manager going forward. [OUTGOING NAME] is moving to [NEW ROLE / REASON — keep this one line], and has spent the last [TIMEFRAME] making sure [INCOMING NAME] is fully up to speed on your account, including [OPEN ITEM].
Nothing else changes — same pricing, same contract terms, same support channel. [INCOMING NAME] will reach out this week to introduce themselves properly and get a call on the calendar.
In the meantime, if anything comes up, you can still reach either of us at this address.
Best,
[OUTGOING NAME] & [INCOMING NAME]
2. The outgoing manager's goodbye#
Subject: Wrapping up my time as your account manager
Hi [CLIENT NAME],
I wanted to let you know that [HANDOVER DATE] will be my last day working directly on your account — I'm moving to [NEW ROLE]. It's genuinely been a pleasure working with you on [PROJECT / RELATIONSHIP DETAIL].
[INCOMING NAME] is taking over starting [HANDOVER DATE]. I've walked them through the account in detail, including [OPEN ITEM], so there shouldn't be a gap. They'll follow up separately to introduce themselves.
Thank you for the trust over the past [TIMEFRAME] — you're in good hands.
[OUTGOING NAME]
3. The incoming manager's introduction#
Subject: Your new point of contact starting [HANDOVER DATE]
Hi [CLIENT NAME],
My name is [INCOMING NAME], and I'll be taking over as your account manager from [OUTGOING NAME] starting [HANDOVER DATE]. A bit about me: [ONE LINE — relevant background, not a full bio].
[OUTGOING NAME] has briefed me thoroughly, including [OPEN ITEM], so I'm not starting from zero. That said, I'd like to get 30 minutes on the calendar in the next two weeks just to hear directly from you what's working and what you'd want to see more of.
Does [DAY/TIME OPTION] work, or would you prefer to suggest a time?
[INCOMING NAME]
4. The internal context summary (for the new owner, not the client)#
Subject: [CLIENT NAME] handover notes
Account: [CLIENT NAME] · Contract: [PLAN / VALUE / RENEWAL DATE]
Primary contact: [CLIENT CONTACT NAME], [ROLE]. Prefers [CHANNEL — email vs. call], usually responds within [TIMEFRAME].
History: [1–2 sentences — how the relationship started, any past issues].
Open items: [OPEN ITEM 1], [OPEN ITEM 2]. Owner and target date for each.
What they care about most: [1–2 things — response speed, a specific feature, price sensitivity].
Don't do this: [any standing instruction — e.g. "never CC their legal team without asking first"].
5. The first-90-days plan (sent to the client)#
Subject: What to expect from [INCOMING NAME] over the next few months
Hi [CLIENT NAME],
Now that [INCOMING NAME] has taken over your account, here's roughly what the next 90 days will look like:
Week 1: Intro call, review of [OPEN ITEM], no changes to current service.
Weeks 2–4: [INCOMING NAME] shadows your regular check-ins to confirm nothing is missed.
Day 60: A short check-in — is anything different from your side, good or bad?
Day 90: Full review, same cadence as before, [INCOMING NAME] fully independent.
You shouldn't notice a dip in service at any point in that window — if you do, reply here directly.
[INCOMING NAME]
6. The mid-project handover (a project is actively in flight)#
Subject: [PROJECT NAME] — a change on our side, no change to your timeline
Hi [CLIENT NAME],
Quick note on [PROJECT NAME]: starting [HANDOVER DATE], [INCOMING NAME] is taking over from [OUTGOING NAME] as your account manager. The project timeline doesn't change — we're still targeting [DELIVERY DATE], and [OPEN ITEM] is already on [INCOMING NAME]'s radar as the next milestone.
[INCOMING NAME] will join our next scheduled check-in on [DATE] rather than scheduling a separate call, so this doesn't cost you extra time.
[OUTGOING NAME] / [INCOMING NAME]
7. The delayed-notice email (change already happened, telling them late)#
Subject: An update on your account team
Hi [CLIENT NAME],
I should have sent this sooner: [INCOMING NAME] has been your account manager since [PAST DATE], following [OUTGOING NAME]'s move to [NEW ROLE]. I apologize for the delay in letting you know directly.
To catch up: [OPEN ITEM] is [STATUS], and nothing about your pricing or support has changed in the meantime. [INCOMING NAME] would like to get a short call on the calendar this week to close the loop properly.
[SENDER NAME]
8. The reassurance follow-up (client hasn't responded)#
Subject: Re: A change to your account team
Hi [CLIENT NAME],
Wanted to make sure this didn't get lost — [INCOMING NAME] is now your account manager as of [HANDOVER DATE], and everything else about your account is unchanged.
No action needed from you unless you'd like a call to talk through anything — happy to set that up whenever works.
[INCOMING NAME]
The hard version of this situation#
Handing over a healthy account is easy to write. Handing over one that's unhappy — a missed deadline, a support complaint still open, a renewal in question — is where most handover emails go wrong, because the temptation is to smooth it over and let the new manager discover the mess on their own.
That backfires twice. The client feels blindsided when the new manager doesn't already know what happened. And the new manager starts the relationship having to ask "wait, what issue?" in front of the client, which reads as either carelessness or a cover-up.
Name the problem in writing before the handover, not after
Template: handing over an unhappy account#
Internal note first, always. Then the client email, which should acknowledge the issue directly rather than hoping it doesn't come up:
Subject: Your account team, and the [ISSUE] from [DATE]
Hi [CLIENT NAME],
Starting [HANDOVER DATE], [INCOMING NAME] is taking over as your account manager. Before anything else: I've made sure [INCOMING NAME] is fully briefed on [SPECIFIC ISSUE], including what's already been done ([ACTION TAKEN]) and what's still open ([REMAINING STEP]).
This isn't a fresh start where that gets forgotten — it's the first thing on [INCOMING NAME]'s list, with [TARGET DATE] as the target to close it out. [INCOMING NAME] will call you directly this week rather than send another email, given where things stand.
[OUTGOING NAME] / [INCOMING NAME]
| Situation | What to name explicitly | What not to do |
|---|---|---|
| Missed deadline or deliverable | The specific date missed and the revised commitment | Blame the outgoing manager by name in a client-facing email |
| Open support ticket or complaint | Ticket status and who owns closing it now | Say "we're looking into it" with no owner or date |
| Renewal at risk | That the new manager knows the renewal is in question, and by when a decision is needed | Bring up pricing or a discount before the relationship is stable again |
| Repeated account manager changes | Acknowledge it directly if this is the second or third change in a year | Pretend this handover is routine when the client has flagged the pattern before |
What to do if there's no reply#
Most clients don't reply to a handover email — that's normal, not a bad sign. Wait three business days, then send the reassurance follow-up (template 8) once. If there's still no response after that, the incoming manager should call rather than email a third time; a handover notice going unacknowledged twice is worth a two-minute conversation instead of a third message in the same thread.
For accounts flagged as at-risk, don't wait for silence to become a pattern — put a call on the calendar in the same week as the first email rather than defaulting to a written follow-up at all.

A faster way to keep handovers from slipping#
The templates above work, but they depend on someone remembering to draft them, personalize the placeholders correctly, and follow up on schedule across every account changing hands — which is exactly the kind of task that gets missed when three people leave in the same quarter.
AI Emaily's AI drafting fills in a handover template like these from the actual thread history with a client — the open item, the last date something was promised, the tone that account is used to — so the incoming manager isn't starting from a blank draft or a guess at what "the open item" even was. Nothing sends without a human approving it first. We build AI Emaily.
Frequently asked
See it in AI Emaily

Written by
Nafiul HasanNafiul Hasan is an entrepreneur and AI automation system builder with 10+ years of experience turning messy, manual workflows into reliable automated systems. He designs and ships AI enterprise solutions end-to-end — the agent logic, the data plumbing, and the product people actually use — and founded AI Emaily to give busy professionals their attention back. He writes here from the builder's seat: what works, what breaks, and how to put AI to work without giving up control.