This page is part of support escalation records, which covers escalation chains in general. This page focuses on one asset: the timeline itself.
The timeline (Illustrative)
Fictional case, invented for this page. A 450-person industrial supplies distributor runs an AI agent in its customer chat. A customer writes in about a pallet that arrived damaged and asks for a credit on 12 cartons.
| Time | Lane | Event | Where it is recorded |
|---|---|---|---|
| 0:00 | Automated | Chat opens; agent matches the customer's email to the account and order | Chat platform log |
| 0:01 | Automated | Agent looks up the shipment: delivered yesterday, receipt signed "damaged" | Order lookup logged under the integration user |
| 0:03 | Automated | Agent asks for photos; customer uploads two | Transcript and attachments |
| 0:04 | Automated | Agent classifies the case as freight damage; the requested credit is above its limit | Agent decision log with policy version |
| 0:04 | Handoff | Ticket created by a trigger and routed to the claims group with a summary and the photos | Ticket event made by a business rule |
| 0:19 | Human | Claims specialist checks the photos against the delivery receipt note | Internal note by a named agent |
| 0:26 | Human | Specialist approves the credit for 12 cartons and opens a carrier claim | Credit memo in the ERP; carrier claim record |
| 0:27 | Human | Customer told the credit and its timing; ticket solved | Public reply and status change |
| Day 14 | Outcome | No reopen and no repeat contact | Ticket status and contact history |
| Day 30 | Outcome | Carrier accepts the claim | Carrier claim record |
The 15 minutes between handoff and pickup is a staffing question, not an escalation error. The escalation question is whether the agent stopped at the right point and passed on enough for the specialist to act without asking the customer again. Here it did both.
What each lane must contain
Automated lane. Every step the agent took, in order, with what it looked up and what it said. The step that matters most is the last one before the handoff: the reason the agent stopped. A policy limit, a low-confidence classification and a customer request for a person are different reasons, and a reviewer judges them differently. If the policy version in force that day is stored, the reviewer can check the agent against the rule it actually had.
Handoff. The event that moved the case, the group it went to, and the context passed with it: a summary, the attachments, the account and order. When the specialist's first action is to ask the customer something the agent already knew, the context was not good enough, and the record shows it.
Human lane. Each action authored by a named person or role: notes, approvals, replies. Linked records in other systems, like the credit memo and the carrier claim here, show the decision had consequences.
Outcome lane. What happened after the ticket closed: a reopen, a repeat contact within a set window, or a confirmed resolution. This lane is what lets a reviewer say the handoff was right rather than merely that it happened.
How the system marks the boundary
The timeline is only useful if automated and human actions can be told apart in the stored record, not just on screen. Helpdesks differ, so the question is always how this particular system marks it.
In Zendesk, ticket audits are a read-only history of every update to a ticket. Each audit holds one or more events, carries an author, and has a via object describing how the update was made. The via object's source distinguishes changes made by business rules such as triggers and automations, and names the rule. So a ticket created by a trigger in the handoff row above would show that rule, while the specialist's note would show a person as author.
Other platforms use different conventions: a dedicated integration user for the AI agent, a separate chat platform with its own log, or a flag on each message. Some companies lose the distinction when the chat transcript is pasted into the ticket as a single block. Ask how the separation survives, and where the agent's own decision log lives, because it is often in the chat vendor's system rather than the helpdesk.
Reading the timeline as an evaluator would
Teams that evaluate agents work from this same shape. Appen describes offering agent trajectories and failure annotations as data services, and triaging agent cases for expert review by flagged failure signals and severity. A company's own escalation history, with outcomes attached, is a human-made version of that labeled timeline: the specialist's action and the day-14 result act as the label.
An evaluator reading the case above asks four things:
- Did the agent try the safe steps it was allowed to take before stopping?
- Was the stop reason legitimate under the policy in force?
- Did the handoff carry enough context for the human to act at once?
- Did the outcome confirm the human's decision?
How trajectory records are defined more broadly is covered in agent trajectory data. Handoff transcripts on their own are covered in AI-to-human handoff data, and using past tickets to train support agents is covered in the historical tickets guide.
Confirming the records exist
Ask the head of support or customer operations, at metadata level only, and with the authorized sponsor's agreement. Never request transcripts, tickets or exports.
| Lane | Question | Answer that points to a usable timeline |
|---|---|---|
| Automated | Is the agent's step log kept after the case is handed off? | Yes, in the chat platform, linked by ticket ID |
| Automated | Is the policy or prompt version recorded by date? | Yes, changes are dated |
| Handoff | Is the handoff an event with a reason, or just a reassignment? | An event with a reason code or rule name |
| Human | Are human actions authored by named agents? | Yes, by user, separate from integration users |
| Outcome | Are reopens and repeat contacts linked to the first case? | Yes, within a set window |
| Depth | How many months or years of agent-assisted cases exist? | Since the agent launched, with no gaps |
Owners, authority and what stays open
The support operations manager usually knows where the lanes are stored; the chat platform and helpdesk administrators can describe the fields. Neither can authorize a licensing discussion. That is the CEO, who can also sign for the company; the COO or another executive responsible for customer records may sponsor the introduction. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
What stays unknown until SourceX reviews it: whether the chat vendor's terms affect who controls the agent logs, how customer details and attachments are de-identified, SourceX's current data needs for agent-assisted escalation records, and any offer. The company's payout and the partner's reward are separate; SourceX funds the reward and never deducts it from what the company receives. For the wider context on agent deployment, see agentic AI in the enterprise.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client can keep its automated steps, handoffs, human actions and outcomes apart in the stored record, register as a partner, confirm the basics on who qualifies and read the program terms before you introduce the executive who owns those records.