Sales account handover: what the new rep needs on day one

The short answer

A sales account handover gives the new rep what the CRM fields do not: where the deal really stands, who matters on the client side, what was promised, which objections are still open and which files are current. Put it in one note, introduce the rep to the client yourself, and make sure the rep confirms they own the account.

Accounts change hands all the time. A rep moves to a new territory, an account grows into an enterprise deal, someone leaves. The client does not care about any of that. They care that the person who calls them next knows what was agreed. This article gives you a ten-point checklist, an example, and the five ways sales handovers usually go wrong.

Why the CRM is not enough

A CRM record tells the new rep the stage, the value and the close date. It rarely says:

• that the buyer’s finance director is the real decision-maker, not the contact in the record;
• that you promised a pilot price if they sign before the quarter ends;
• that the last call went badly because of a delivery delay;
• which of the four proposal files in the folder is the one the client saw.

That knowledge lives in the outgoing rep’s head, in their inbox and, more and more, in their chats with Claude or ChatGPT where they prepared the call and drafted the proposal. The handover note is where it has to land.

The day-one checklist

The fifth point, commitments, causes the most damage when it is missing. A rep who does not know about a promised discount either honours it by surprise or loses trust by refusing it.

A filled-in example

Here is the checklist for a made-up account. James takes over the Nordlit account from Anna, who moves to the enterprise team.

ACCOUNT HANDOVER: Nordlit
From: Anna   To: James   Effective: Mon 26 Oct

Stage
Proposal sent 12 Oct. Client reviewing. Waiting for their
answer on the annual option.

Value and timing
€24,000 a year. Expected close end of November. Depends on
their budget sign-off on 20 Nov.

Contacts
- Laura Price, operations lead: day-to-day contact, champion
- Peter Holm, finance director: decides, cautious on price
- IT team: needs a security answer before signing

Relationship
Laura prefers short emails, calls only when booked.

Commitments
- 10% off the first year if signed by 30 Nov (said on the
  call of 12 Oct, not yet in writing)

Open objections
- Peter worried about onboarding time. We offered a setup call.

Competitors
They mentioned looking at one other supplier. Name unknown.

Files
- nordlit-proposal-2026-10-12.pdf: the version they received
- call-notes-12-oct.md: my notes from the last call

Next step
James sends the security answer to IT by Fri 30 Oct.

Introduction
Anna emails Laura on Mon 26 Oct to introduce James.

It fits on one screen, and James can call Laura on Monday without asking Anna anything.

Five common failures

1. The silent switch

The client finds out about the new rep when an unfamiliar name appears in their inbox. Always introduce the new rep yourself, with a reason the client can accept.

2. Promises that only lived on a call

The client remembers the discount. The new rep has never heard of it. Write down every commitment, even the informal ones, and mark which ones are not yet in writing.

3. The wrong file

The rep sends “the latest proposal” and it is not the one the client saw. Name files with dates and say which version went out.

4. A list of names with no roles

Five contacts with job titles do not tell the rep who decides. Add one line on each person’s role in the deal.

5. No confirmation

The old rep thinks the account is handed over. The new rep thinks they were only copied in. For a week, nobody follows up. End the handover with a clear “it’s mine” from the new rep.

For the general structure behind any handover note, see how to write a handover note people actually read. For handovers that cover a whole project, with budget and access, the project handover checklist goes further.

Doing it in one sentence with Colle

If Anna prepared the account in Claude or ChatGPT, most of the checklist is already in her chats. With Colle she says:

Her assistant finds James, writes the summary, records the facts (the value, the close date, the promised discount and its deadline) and attaches the proposal and the notes. James gets a notification straight away and accepts in one click. He asks his own assistant “what did I get?” and prepares Monday’s email to Laura with the full context. If something is missing, he returns the handoff with a reason, such as “which proposal did they receive?”.

Facts keep their history. If the close date moves, James updates it and the earlier value is still there. If the handoff is not picked up in time, both see it as overdue. Colle does not replace your CRM; the record stays there. Colle carries the part the CRM does not hold, from one rep’s assistant to the next. See how this works for sales teams.

When you do not need Colle

If your reps do not use an AI assistant, or your team keeps detailed account notes in the CRM and handovers are rare, a good written note and an introduction are enough. To check whether handovers cost your team enough to fix, use the formula in the real cost of a handoff. Agencies moving client accounts between managers face a similar problem; see client handover in an agency.