Separate facts from assumptions
A useful handoff starts with the customer's requested outcome, then lists verified facts and where they came from. Mark anything inferred or unverified. Include the policy version and the steps already attempted with their results. A long transcript alone forces the next teammate to reconstruct the problem and can bury the one detail that changes the decision.
End with a concrete next action
State why the case was escalated, what authority is required and what the customer was told to expect. Retain relevant context, but avoid duplicating sensitive details that the recipient can access through the authorized case record. In a bilingual queue, keep identifiers unchanged and include the customer's preferred reply language; translating a name or order reference can break the lookup.
Fictional worked example
Fictional handoff: 'Goal: correct delivery address. Verified: order DEMO-208 is marked dispatched in the test record. Tried: checked the address-change article; it only covers pre-dispatch edits. Needed: shipping team's decision on carrier options. Customer told: we are checking; no redirect promised. Reply language: Arabic.' This note distinguishes what is known from the unresolved action.
Action checklist
- Include goal, facts with sources, completed steps and their results.
- Name the reason for escalation and the required decision.
- Preserve references and preferred language exactly.
- Have another teammate explain the next action using only the note.