← All resources

Customer context

How to hand over a customer account without starting over

Imagine taking over a customer account and receiving a folder, a CRM record and a calendar invitation. On the first call, the customer says, “As we explained last week…”

The records may all be there. The handover still failed to carry the conversation forward. A useful customer account handover gives the incoming owner enough context to make the next sensible decision without making the customer start again.

Start with the next conversation, not the entire account history

A chronological archive is useful for investigation. It is a poor introduction to an account. The incoming owner has to discover which facts are current, which decisions are settled and which old concerns still matter.

Start with a short brief that answers four questions:

  1. What is the customer trying to achieve? Describe the business task or outcome in their terms, with a link to the agreed source where available.
  2. What is happening now? Include active work, current obstacles and the most recent meaningful change.
  3. Who matters to the next step? Identify the relevant customer contact, internal owner and any decision-maker whose involvement is actually needed.
  4. What should the incoming owner do next? State the next conversation or decision, why it matters and what preparation is needed.

Keep interpretation distinct from fact. “The customer is unhappy” leaves the new owner guessing. “The operations lead asked for a single contact after receiving conflicting updates” gives them something specific to address.

GitLab's public account handoff checklist is a useful reference for the breadth of context a transfer can involve, including communication, objectives and technical work. A handover for a smaller team can be shorter; it still needs to answer the questions that affect the next interaction.

Hand over unresolved decisions explicitly

Open tasks are often easier to find than open decisions. The task tracker says “Investigate export.” It may not say that the customer is choosing between a temporary manual process and waiting for the product change. That choice affects what the new owner should say.

For each active issue, record the current state, the next decision and who can make it. Add the evidence behind the current recommendation. If a date is a customer request rather than an agreed delivery date, label it that way.

The second note tells someone how to continue the work. It also avoids turning an assumption into a commitment just because it appeared in a handover document.

A customer account handover checklist

Use this as a working checklist, not a requirement to create another account database. Link to the authoritative records and keep the brief small enough to read before a call.

Customer purpose
The outcome the customer is working toward, the relevant workflow and the current success criteria.
People and communication
Relevant contacts, their role in the current work, the agreed channel and the next scheduled interaction. Include only information the receiving owner should have.
Active work
Open issues, their observed impact, internal owners and the latest verified state. Separate an assigned owner from a handoff awaiting acceptance.
Decisions and dates
Outstanding choices, who can decide, relevant deadlines and the source of each date. Mark estimates and unconfirmed assumptions.
Useful history
Recent decisions and their reasons, approaches already tried and constraints that still apply. Leave unrelated historical detail in its source.
Access and acceptance
Confirm that the incoming owner can open the permitted records, understands the next step and has accepted responsibility. An introduction email alone does not establish this.

Access deserves a real check. A brief with ten links is not useful if the recipient can open only two. Follow your organization's access process rather than copying restricted material into a shared document to work around permissions.

Introduce continuity, not just a new person

The first message should show that the incoming owner understands the current work. It can be short:

“I'm taking over as your account contact. I've reviewed the export issue and the decision about Friday's workaround. I'll confirm the latest investigation update before we speak. Is there anything that has changed since your last conversation with the team?”

This is a sample message, not a script to send without checking the facts. The useful part is the question about what changed. It respects the information the customer has already supplied instead of asking them to recreate it.

After the first interaction, correct the brief. Confirm which decisions are still open, remove stale assumptions and record the next step in the place the team actually uses. Keep the outgoing owner available for a bounded clarification period where practical, rather than silently making them responsible forever.

A handover is ready when the new owner can explain the current situation, open the supporting records and carry out the next action. The size of the folder is a poor substitute for that test.

For a technical issue changing teams, the support-to-engineering handoff template goes deeper on investigation evidence. Account continuity needs that detail only where it affects the relationship or the next decision.