The previous rep has moved roles, or left. Your manager hands you their accounts and live opportunities, along with a CRM export: stage, forecast value and last-contact date for every deal. It looks complete. Then you open one deal to find out what the customer said last time, what was promised and where it is stuck — and the record tells you none of it.
This is the most common situation in inheriting accounts. You have been given the list, but not the story.
What transfers in a handover is records. What does not transfer is context — and context is what the deal was actually running on.
This guide is written for the rep receiving the accounts, not the manager running the transition. It gives you a reconstruction sequence: how to recover the stakeholders, commitments and undocumented decisions from what was left behind, before your first customer meeting. It ends with what to capture from now on, so the next handover does not repeat this one.
What Survives a Handover, and What Doesn’t
| Usually survives | Usually lost |
|---|---|
| Account list and contact details | The real role and influence of each person |
| Deal stage and forecast value | Why the deal is sitting at that stage |
| Quotes and contracts | Conditions agreed verbally beyond the quote |
| Dates of meetings and calls | What was said in them, and what was concluded |
| Email threads | Agreements made by phone, text or messaging apps |
That last row deserves attention. A lot of B2B communication now happens outside email: a text confirming a spec, a direct message about pricing, a late-evening “let’s go with what we discussed.” When the previous rep leaves, those conversations often leave with their phone. And that is frequently where the deal was really being run.
The Reconstruction Sequence, Before You Meet Anyone
The most common mistake after inheriting accounts is rushing out to meet every customer and piecing the story together in the meeting itself. Customers feel they have to start over, and may discover you do not know what your predecessor promised. It works far better to recover what you can, in this order, before the first meeting.
1. Rebuild the stakeholder map from records
Ignore the stage for now and start with the people. Lay out everything connected to the deal: email recipients and copies, meeting invitees, the addressee on quotes, contract signatories. List every name that appears, then mark each person’s likely role: main contact, user, approver, budget holder.
The list will be incomplete. But it tells you two things: who you know, and where a key role is still a blank. For turning that list into a working map, see sales stakeholder mapping: who really influences the deal?
2. Identify commitments the previous rep made
This is the highest-risk part of any handover. Your predecessor may have promised a discount, a delivery date, a document not yet sent, or “better terms at renewal.” If you do not know, the first time the customer raises it you are stuck: agree, and you may exceed your authority; refuse, and the customer concludes your company does not keep its word.
Look for commitments in quote notes, in emails containing phrases like “I’ll send that over” or “we can look at that,” in contract attachments — and above all, with the previous rep, if you can reach them. If they have only moved roles, an hour going through each deal and asking “what did you promise this customer?” is the most valuable hour of the whole handover.
3. Find decisions that were made but never documented
Some decisions the customer has already made never appear in any record: the configuration they chose, the option they ruled out, the timeline they agreed internally. These usually live in the previous rep’s memory or in the verbal outcome of a meeting.
Besides your predecessor, ask anyone else who touched the deal: the sales engineer, technical support, customer success, your manager. Each knows part of it. Put the pieces together and you can often recover where the deal actually stands.
4. Re-verify who still holds each role
While your predecessor was running the account, the customer was changing too. Contacts move departments, managers retire, budget holders change. The stakeholder map in the record may describe the account as it was six months ago.
Before you meet the customer, confirm as far as you can whether key roles are still held by the same people — through public information, mutual contacts or a short confirmation email. In long-stalled deals especially, a change in a key person is often the very reason for the stall.
5. Do it before the first meeting, not during it
All four steps belong before your first customer meeting. The reason is simple: the first meeting is your chance to earn trust. If you can say, “I understand you discussed these terms with my predecessor, and that you’re still waiting on that document,” the customer feels the deal has not been broken. If all you can ask is “so, where are we?”, the customer feels they are starting again — and the deal is likely to slip further.
Some things can only be confirmed with the customer. When that is the case, bring what you already know and confirm it, rather than asking them to explain from scratch. “Here’s my understanding — is that right?” works far better than “can you walk me through where things are?”
An Inherited Deal, Rebuilt in Sequence
Hypothetical scenario. A rep inherits twelve live opportunities from a predecessor. One is a point-of-sale system upgrade for a restaurant group, shown in the CRM as “In negotiation,” with the last contact two months ago.
Instead of picking up the phone, the rep works through the sequence:
| Step | What the rep finds |
|---|---|
| Rebuild the stakeholder map | The IT manager, the finance manager and the VP of operations appear in emails, but only the IT manager is on every thread |
| Identify commitments | After checking with the previous rep: a 20% discount on second-year maintenance was promised in a text message, and never added to the quote |
| Find undocumented decisions | The sales engineer recalls the customer deciding at the last meeting to roll out in one region first and delay the rest until next year |
| Re-verify roles | Public information shows the VP of operations left last month; the successor has never seen this deal |
The first visit is completely different as a result. The rep arrives with a revised quote that includes the maintenance discount and a rollout plan scoped to the first region, meets the IT manager, and asks for an introduction to the new VP of operations. The customer does not have to start over, and the deal does not slide backwards because the rep changed.
If some of the deals you inherited have gone quiet for a long time, see when a prospect goes silent: reading a quiet deal.
What to Capture From Now On, So the Next Handover Is Different
The difficulty you are facing now will be faced by whoever inherits your accounts next — unless you change what you record. It does not take much. After every significant interaction, make sure four things are written down:
- Who you spoke with, and their role. Not just a name, but where they sit in this decision.
- What was discussed, and what was concluded. Especially decisions the customer has made.
- Who committed to what. What you promised the customer, and what the customer promised you.
- What is still unresolved. What needs to happen next, and where it is stuck.
Above all, record it in a company system, not only in your personal messages or your memory. For capturing every interaction in a usable way, see how to track every client interaction in B2B sales. For building each follow-up on the last exchange, see sales follow-up: making contact that changes the deal.
What Survives a Handover Is the Interaction History
People move, phones leave with them, memories fade. What survives a handover is a systematic record of each stakeholder, each conversation and each commitment.
VINEQRA is an iOS app that keeps the interaction history for each stakeholder in an opportunity: what was discussed, what was promised and what is still open. When a deal changes hands, the next rep sees not just stages and dates, but the context the deal was actually running on.
Frequently Asked Questions About Taking Over a Sales Territory
What should I do first when taking over accounts from another rep?
Hold off on visiting customers. Start by rebuilding the stakeholder map from existing records: list everyone who appears in emails, meeting invites, quotes and contracts, and mark their likely role.
What is most often lost in a sales account handover?
The previous rep’s verbal commitments, and decisions the customer made that were never recorded. These often live only in the predecessor’s memory, personal messages or a meeting’s verbal outcome — not in quotes or the CRM.
What if the previous rep has left and can’t be reached?
Go to others who worked on the deal: the sales engineer, technical support, customer success or your manager. Each knows part of the picture. For what only the customer can confirm, bring your current understanding and ask them to check it, rather than asking them to explain from the beginning.
How should I open the first meeting with an inherited customer?
Show that you already understand where things stand — the terms discussed last time, the document they are still waiting for — and ask them to confirm your understanding. The customer does not have to repeat themselves, and the deal is less likely to slip because of the change in rep.
How do I make sure the next handover doesn’t have the same problem?
After every significant interaction, record four things: who you spoke with and their role; what was discussed and concluded; who committed to what; and what is still unresolved. Keep it in a company system, not only on your phone or in your head.