Write an account handover email
Introduces a new account owner to a client when responsibility changes, covering continuity, what stays the same, open items and a meeting offer. Use for account managers and freelancers.
When an account owner changes, the client's first worry is not the person but the risk: will deadlines slip, will they have to explain everything again, will pricing or service change. Clients churn after handovers that arrive as a surprise, from someone they have never heard of, with no date and no word about open work. The handovers that keep clients come from the outgoing owner as a warm introduction, say when the change happens and how long the outgoing owner overlaps, name what stays the same, show the incoming owner already knows the open items, and offer a short joint call. A separate first note from the incoming owner then starts the new relationship.
Write an account handover email for , from introducing .
Only if [REASON] is given:
Only if [OPEN_ITEMS] is given:
- If it is unclear who takes over, ask and stop. Missing dates or details become placeholders.
- Write the handover email from the outgoing owner, with the incoming owner in copy:
- Subject: "[Client/project]: introducing [incoming owner] as your new account lead".
- First two sentences: the change, the effective date (or
[need: effective date]), and that the outgoing owner remains reachable until a stated date if given. - Reason in one neutral sentence if it is shareable (a move, a promotion, a team change). Leave out anything sensitive such as a performance issue, a dispute, health or a departure the company has not announced, and say so under Notes.
- Why the incoming owner is a good fit, using only the experience given. If none is given, leave
[need: one line on relevant experience]rather than inventing praise. - What stays the same: contract, pricing, team, service levels, tools and contact routes, only as stated or as placeholders to confirm.
- Open items as a short list with status and dates, showing the incoming owner has been briefed.
- A joint call offer with two or three slot placeholders or proposed times, 20 to 30 minutes.
- Sincere thanks to the client for the relationship in one or two lines, specific to it if the input allows.
- Write a short first note from the incoming owner to send after the introduction: thanks, one line on what they will do first (review the open items, confirm the call), and their direct contact details.
- Under Notes, list what to confirm internally before sending (pricing, notice, any commitments the outgoing owner made verbally) and whether to phone the client first if the relationship is long or sensitive.
- Handover email under about 200 words; incoming note under about 80 words.
- Use only facts given; never invent experience, dates, commitments, pricing or names. Use
[need: …]. - Do not promise that nothing will change if the input suggests changes; state what is known.
- Warm and confident, not apologetic. The tone says "you are in good hands", supported by facts, not adjectives.
- Never disclose internal reasons the client does not need, and never criticise the outgoing or incoming owner.
Handover email
Subject line, To/Cc line, then the body.
Incoming owner follow-up
Subject line, then the body.
Notes
Placeholders, internal checks, and whether to call first. "None" if nothing.
3 required values still a placeholder; the assistant will ask for them.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Writing and communication
- category
- level
- Beginner
- made for
- Consultant / freelancer, Sales, Customer support, People manager
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install write-account-handover-email --target claude-codeThis entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.
pairs well with
All of EmailWrite a handover document
Writes a handover for leave or a role change covering responsibilities, open work status, contacts, access, recurring tasks, known risks and first-week priorities, with gaps listed as questions.
write-handover-documentWrite a farewell message
Writes a goodbye message to colleagues, clients or a community when leaving a job or team, with specific thanks, handover pointers and a way to stay in touch, and nothing that burns bridges.
write-farewell-messageWrite an introduction email
Writes a double opt-in introduction, first the private ask to the person being introduced, then the intro email itself, with why the two should talk and an easy next step.
write-introduction-emailDecline a request gracefully
Declines a request or invitation clearly and kindly in the first lines, gives an honest brief reason if wanted, offers only real alternatives and preserves the relationship.
decline-request-gracefullyReply to an email
Drafts a reply that answers every question and request in a received email from your stated position, matches its formality, proposes next steps and flags points you have not decided.
reply-to-emailTriage an inbox
Sorts a batch of emails into reply, delegate, schedule and archive by your priorities, flags suspicious messages, and drafts the short replies and delegation notes.
triage-inbox