The short answer: treat the outgoing account manager’s inbox as the handoff document. Before the new owner’s first day, pull every open client thread and every date promised in email into one list, give each line an owner and a due date, then send it to the client to confirm.
The items that get dropped in a handoff tend to be the ones that were promised in an email and never written down anywhere else. The account summary survives the transition. The “I’ll get you the revised schedule after the renewal meeting” in a reply from three weeks ago does not.
Why most handoff templates miss it
Most handoff advice asks the outgoing account manager to describe the account. Teamwork’s client handoff checklist template is a good example: it captures background, goals, active work, risks and key contacts, so the new owner is not “piecing context together from email threads and chats.” DOT & Company’s piece on agency handoffs lists what a strong handoff should include, down to “any promises made during sales conversations,” and describes the usual reality: someone “forwards a long email thread, drops a few scattered notes in Slack.”
Both are right about the context. The gap is the source. A template is filled in from what the outgoing account manager remembers, often in their last week, often while they are busy leaving. The open promises are in their sent mail. So the checklist below starts in the inbox.
The handoff checklist
Before the new owner’s first day
- Name one owner for the transition and one date. One person, usually the coordinator or the account managers’ manager, owns the handoff until the new account manager has closed or re-dated every open item. Set the date the new account manager takes over.
- Secure access to the outgoing mailbox while the account manager is still there. In Google Workspace, they can add a delegate who can read, send and delete mail in their account, if your admin has delegation on. In Microsoft 365, an admin can grant Read and manage (Full Access) permission, which does not include Send as. If they are leaving the company, plan now for step 12.
- Pull every open thread and promised date out of the outgoing account manager’s inbox before day one. Search mail with the client’s domain over the last 90 days, and open every thread where the client wrote last: those are waiting on you. Then search the account manager’s sent mail to that domain for date language. In Gmail, search operators like
from:me to:clientdomain.com newer_than:90d "by Friday"do this one phrase at a time; also try “next week”, “I’ll send”, “I’ll get back to you” and “end of month”. Note the threads where you are waiting on the client too; the new account manager will need to chase them. - Write the open-items list. One line per item: what was asked, what was promised, the date promised, the client contact, a link to the source thread, the new owner and the status. This list, not the account summary, is the handoff document.
- Check the list against the CRM. Reassign the account, contacts and open tasks to the new owner, then compare. Anything on the list with no CRM task gets one. Anything in the CRM that is not on the list gets asked about.
- Move the calendar. Recurring client meetings, renewal and review dates, and any meeting the outgoing account manager proposed but has not booked yet.
- Capture the unwritten context. Who actually decides, who is sensitive about what, pricing or service exceptions, anything the client was told informally. Ask the outgoing account manager directly: “What have you promised this client that is not in writing anywhere?”
Handover week
- Run the internal handoff meeting from the open-items list, line by line, not from the account summary. Every line leaves the meeting with a named owner and a date.
- Ask for a readback. The incoming account manager writes back their understanding of the account and the open items; the outgoing one corrects it. Gaps show up as errors in the new version, which is faster than asking someone to remember what they forgot.
- Introduce the new account manager in writing, with the list. Send the client the open items and their dates in the introduction email and ask one question: is anything missing? Clients know what they are waiting for.
- Hand over the threads, not just the account. The incoming account manager replies on every open thread from their own address, so the client’s next reply goes to the right person.
After the switch
- Decide what happens to the old address. If the outgoing account manager is leaving the company, do not delete the account on day one. In Microsoft 365, an admin can convert the mailbox to a shared mailbox; it needs a license at the moment of conversion, a shared mailbox without a license is limited to 50 GB, and Microsoft warns not to delete the old user account because it anchors the shared mailbox. In Google Workspace, an admin can delegate access to the account. Either way, set an auto-reply naming the new account manager.
- Watch the old address for 30 to 60 days. Clients reply to old threads. Someone has to see those replies.
- Check at 30 days. The transition owner walks the open-items list with the new account manager: every line closed or re-dated with the client’s agreement. Anything else goes back on the list.
Send the client the list: “Here is everything we have open with you and when it is due. Is anything missing?” It costs one email and it catches whatever the inbox search did not.
Where the tools fit
Same criteria per row, September 2026. What each option captures in a handoff, and whether it catches a promise that only exists in email.
| Option | What it captures | Catches promises made only in email | Who does the work | Where it breaks |
|---|---|---|---|---|
| Handoff template (Teamwork's, or your own in a doc or project tool) | Background, goals, active work, risks, key contacts | Only if the outgoing account manager remembers and types them in | The outgoing account manager | Filled in from memory, usually in their last week |
| CRM owner change and task report (Salesforce, HubSpot) | The account record, contacts, logged activity, open tasks | Only what was logged or turned into a task | An admin or the account managers | A follow-up exists only if someone created the task |
| Mailbox access (Gmail delegation, Microsoft 365 permissions, shared mailbox conversion) | Everything in the outgoing mailbox | Yes, if someone reads it | The coordinator or the new account manager, by hand | A raw inbox, nothing sorted; Full Access does not include Send as |
| Shared inbox app (Front, Missive) | Conversations and their assignment history | Yes, for email that lived in the app | Whoever reassigns conversations | Mail the account manager answered from personal Outlook or Gmail is not there |
| alfred_ | The client threads waiting on the account manager and the ones waiting on the client, asked for in plain language | Yes, for threads in the connected inbox | The outgoing account manager asks; a coordinator can open their inbox with their permission | Does not build the handoff list or detect handoffs; the coordinator setup is done with us; does not read the CRM |
Use a template for the account context; it is the right home for goals, contacts and risks. Use the CRM report for everything your team logs faithfully. Use mailbox access for steps 3 and 12, because nothing else holds the full record. Use a shared inbox’s reassignment if the account’s email already lived there. Use alfred_ for getting the open threads out of an inbox quickly, with the account manager’s permission.
Where alfred_ fits
alfred_ helps with the part of a handoff that lives in email. It does not run the handoff.
- The outgoing account manager can ask what is still open. If they use alfred_, they can ask it what is still open with a client, or what they are waiting on, and paste the answer into the open-items list in step 4. Each account manager’s own alfred_ tracks which client threads are waiting on them and which are waiting on the client; the prompts are in Follow-up tracking.
- A coordinator can open the outgoing account manager’s inbox with their permission. On a team set up for it, a coordinator can work a teammate’s inbox and calendar, read without marking mail read, and draft replies into their Drafts during the overlap. The teammate sees who looked. Permission comes from the teammate, so ask during the notice period, not after the last day.
- The incoming account manager starts with a list. Their own alfred_ tracks which client threads in their inbox are waiting on them from the day they take over, in the Gmail or Outlook they already use. Step 11 is what moves the open threads into that inbox.
What it does not do: it does not notice that a handoff is happening, build the list for you, move threads between mailboxes, or read Salesforce or HubSpot. It can log outbound mail to your CRM by BCC. The coordinator setup is not self-serve: it is set up with us for teams on the Team plan, $34.99 per seat per month with a two-seat minimum.
alfred_ helps a handoff when:
Pros
- The account's promises live in the outgoing account manager's own Gmail or Outlook
- You want the open client threads listed from the inbox, not reconstructed from memory
- A coordinator needs to read the outgoing inbox during the overlap, with permission, without marking mail read
- The incoming account manager should see what is waiting on them from day one
Cons
- It does not build the handoff list or detect that a handoff is happening
- It does not move mail between mailboxes or read the CRM
- The coordinator setup is done with us, not self-serve
Not the pick when:
Use something else if
- The whole account's email already lives in Front or Missive (reassign the conversations there)
- Your team logs every promise as a CRM task (run the CRM's open-task report for the account)
- The account manager has already left and cannot give permission (an admin converts or delegates the mailbox)
- It is one small account and one afternoon of searching a delegated inbox will do (Gmail or Outlook search)
What that option gives up
- Shared inbox: only covers mail that lived in the app
- CRM report: only covers what was logged
- Admin mailbox access: a raw inbox, nobody sorts it for you
- Manual search: one phrase at a time, and easy to stop early
For the everyday version of the same discipline, one person keeping track of their own follow-ups, see how to never drop a follow-up.
Our Verdict
Build the handoff from the inbox, then confirm it with the client.
Handoff templates and CRM owner changes carry the account context and whatever was logged. The promises that get dropped usually only exist in the outgoing account manager's email, so the checklist starts there: secure mailbox access early, pull every open thread and promised date before day one, check the list against the CRM, and send it to the client with the introduction. alfred_ helps with the email part: the outgoing account manager can ask what is still open with a client, a coordinator can open their inbox with their permission, and the incoming account manager's own alfred_ tracks what is waiting on them. It does not run the handoff for you.
Best for
- The checklist above for any account handoff, with or without new tools
- alfred_ when the account's promises live in personal Gmail or Outlook inboxes
- A shared inbox's reassignment when the account's email already lived there
Not for
- A template alone, filled in from memory in someone's last week
- A CRM owner change alone, if your team does not log every promise
- alfred_ as an automatic handoff tool; it does not detect or build handoffs