When a sales rep leaves: keeping customer knowledge

A rep hands in their notice. The notice period runs, the handover happens in one meeting, and the portfolio is split between two colleagues. The CRM is up to date, the opportunities have their amount and their stage. Everything looks in order.

Three weeks later, the new owner of an account calls the main contact. They ask questions already asked, suggest a date already turned down, know nothing of the discount promised in June. The customer does not always say it, but they notice: they are starting from scratch.

This is not a discipline problem. It is a medium problem: most of what a rep knows about an account was never written anywhere.

What walks out the door with a rep

What leaves the company on the last day is not the contact details or the stage history. It is six things the rep carried in their head and used on every call.

• The context of the account. Why this customer started looking, what had failed before, what has changed in their organisation since.
• The promises made. A discount at renewal, a feature mentioned for next quarter, a call back promised before month end. Each one commits the company, not only the person who made it.
• Who really decides. The main contact is not always the person who signs, nor the one who can block. The rep knows because they heard it, rarely because they wrote it down.
• What was said about budget and timing. Budget released in September, a purchasing freeze until year end, a deadline tied to another project.
• The objections already raised. And above all the answer that convinced. Raising an objection that was already handled tells the customer they were not listened to.
• The tone of the relationship. A contact who prefers a short message to a call, a sensitive topic to avoid, a past tension that was settled together.

A portfolio is not handed over with a list of accounts. It is handed over with what was said on each one.

Why CRM notes do not hold it

A CRM is built to run a pipeline: fields, stages, amounts, dates. It answers "where is this account?" very well. It answers "what was said with this customer?" poorly.

Free text notes exist, but they are written after the call, quickly, between two meetings. They keep the conclusion and lose the path: "interested, follow up" instead of "waiting for their CFO's approval, who is worried about the integration cost".

The left column says where the account stands. The right column says how to pick it up. The second one is what disappears when a rep leaves.

What a useful account memory must contain

Before choosing a tool or a format, decide what a new owner must find when opening an account. This list works as a grid, whether the memory is a shared document or a customer file.

• The exchanges themselves, attached to the account, not only their summary.
• A short, dated synthesis of the current situation that says what changed since last time.
• Open commitments: who committed, to what, by which date, and whether they were kept.
• Past and current deals, with their outcome: won, lost, open, and why.
• The people on the customer side and their real role in the decision.
• The objections already heard and the answer that worked.
• What was said about budget, timing and the decision process.
• Risk signals: a competitor mentioned, dissatisfaction, a contact who stopped replying.

If any of these only exists in one person's memory, it is the first thing to go.

Documenting or capturing

The usual answer to the risk of departure is to ask reps to write more: a summary after every call, a handover sheet when they leave. That is documenting. It works as long as the team has time, and stops working exactly when you need it: a rep on their way out has neither the time nor the motivation to write ten complete account sheets.

Capturing means keeping the conversations themselves and drawing out what matters as you go. The memory builds while the rep works, not on the day they leave.

Capturing does not remove all writing. A rep who knows why an account turned should say so. But writing now complements the source, it no longer replaces it.

Running a portfolio handover in 30 days

The plan below is for the manager and the new owner. It assumes the departing rep is still around for a few days, which is not always the case; if they have already left, start directly at step two.

Days 1 to 5: sort the portfolio

The manager sorts the accounts into three groups: those with an open deal or an upcoming renewal, those with an open commitment, and the rest. The first two groups come first. With the departing rep, spend twenty minutes per priority account on a single question: "what is not written anywhere?".

Days 5 to 10: read before calling

For each priority account, the new owner reads the latest exchanges and the synthesis. They list the commitments made on the company's behalf and check the ones coming due. A commitment forgotten during a handover is the first cause of lost trust.

Days 10 to 20: the first contact

The new owner contacts each priority account and shows they know the file. They do not ask "where are you at?"; they say what they know and ask what has changed. For example: "I saw you were waiting for the November committee to approve the budget, is that date still holding?".

Days 20 to 30: consolidate

The manager and the new owner review account by account: commitments kept, deals whose stage has moved, accounts that went quiet since the departure. The third group is then picked up in turn, with the same method.

The questions to answer before the first call

A good handover test fits in five questions. If the new owner cannot answer them for an account, they are not ready to call it.

• Why did this customer choose us, or why are they evaluating us?
• What was promised, and by when?
• Who decides, and who can block?
• What was the last objection raised, and how was it handled?
• What could make this customer leave today?

These answers must be verifiable. An answer from memory, passed on orally, is a hypothesis. An answer that points to the passage where the customer said it is a fact.

A customer file that keeps itself up to date

That is the idea behind the customer file we offer. Every exchange is attached to it, whether it comes from a call recorded on Google Meet with the Chrome extension or from an uploaded recording. After each exchange, the customer synthesis is updated, commitments are extracted with their owner and due date, and deals detected in the conversation appear with their outcome, editable by hand.

The new owner can also ask their five questions straight to the assistant, which answers from the account's exchanges and cites, for every claim, the exact passage it comes from. They reread the source instead of trusting a summary.

The limits to keep in mind

An account memory only holds what was captured. An exchange that was not recorded, a lunch, a call from a personal phone, is not in it. Recording also requires informing the participants and obtaining their consent.

And a generated synthesis is a draft: it gets reviewed. Its value is not to replace the new owner's judgement, but to give them in a few minutes the material they would have spent weeks rebuilding.

The best time to prepare for a departure is the day the rep joins.