Escalation timeline builder (L2)
When an account goes red, someone spends half a day reconstructing what happened. This play has the assistant assemble a dated timeline from tickets, call notes, and email threads so the escalation meeting starts with facts instead of memory.
The steps
- 01
Define the escalation packet
Tool: Manual
Fixed sections: dated event timeline, commitments made by us, commitments made by them, open items with owners, the customer's stated ask. Nothing else. Owner: CS leader. DoD: packet template approved by support and CS.
- 02
Assemble the inputs
Tool: Zendesk
Export the ticket thread, the call summaries, and the relevant email chain into one document. At L2 this is a human doing an export, not an integration. Pitfall: cherry picking inputs that support a preferred story. DoD: input bundle is attached to the escalation record.
- 03
Generate and fact check the timeline
Tool: Claude
Ask for a strictly dated timeline with a source line per entry. The CSM checks every commitment entry against the source before the packet is shared. Unsourced entries get deleted. Owner: account CSM. DoD: every timeline line carries a source reference.
- 04
Run the meeting off the packet
Tool: Slack
Post the packet in the escalation channel two hours before the call. The meeting becomes decisions, not recall. Owner: escalation lead. DoD: no escalation call starts without a posted packet.
Tools in this playbook
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.