What does agent recovery data mean in an ordinary business workflow?
It means a company kept enough of a broken task to show three things together: where it broke, what someone did about it, and how they knew the result was right. Any one of those on its own is ordinary operational noise. Linked, they become an example of recovery.
AI developers want these examples because agents that only learn from clean successes do not know what to do when a step breaks. Appen, which sells data services for agent training, describes a trajectory analysis service in which experts classify where agents go wrong and, for failed runs, write the correct continuation from the point of failure. A business that already recorded how its people recovered from real failures holds the natural version of that continuation, written by someone who had to live with the outcome. Our explainer on why AI agents fail covers the failure side, and agent trajectory data covers step-by-step records in general.
The everyday example on this page is a customer transfer in a messaging channel: a bot tries to hand a customer to a human, the handoff does not complete, and the company has to recover the case. The wider family of bot-to-person handoff records is described on the AI-to-human handoff data page.
A failed transfer, hour by hour (Illustrative)
Everything below is fictional. A 420-person subscription meal-kit retailer runs a chat assistant in front of its billing team. Zendesk's documentation describes the kind of mechanism involved: messaging conversation control can pass a conversation to the next configured integration, or release control, which clears the handoff and returns the conversation to its default state.
| Time | Event | System of record | Recovery stage |
|---|---|---|---|
| Mon 18:02 | Customer reports a double charge; bot classifies it as billing | Bot conversation log | Task starts |
| Mon 18:04 | Bot passes control to the billing queue; the queue has closed for the day | Messaging routing event | Failure point |
| Mon 18:09 | Conversation returns to the bot; customer leaves without an answer | Conversation log, released status | Failure visible |
| Tue 08:40 | Morning report lists conversations released without an agent | Daily handoff report | Detection |
| Tue 09:15 | Agent opens a ticket, links the conversation ID, refunds the duplicate charge | Help desk ticket, billing refund record | Recovery action |
| Tue 09:20 | Agent emails the customer; ticket set to solved with reason "failed handoff" | Ticket audit trail | Resolution |
| Tue +7 days | No new contact from the customer on billing; refund settled | Ticket search, payment processor | Verification |
The useful part is not the bot error. It is the chain from failure to verified fix, and the decision the agent made at 09:15: refund first and explain second, because the charge was clearly duplicated. That judgment is what an AI agent would need to learn. A second agent might have asked the customer to confirm the charge before refunding, which would also have been defensible. A collection of real recoveries shows which path the company actually chose, how often, and with what result.
Notice, too, that the recovery started from a report rather than from the customer. Detection is its own step, and a company that only recovers when customers complain records a narrower kind of recovery than one that looks for its own failures.
The fields that tie the failure to the fix
The example works only because a handful of fields connect records held in different places. These are the fields a reviewer would look for in the annotated case above.
| Field | Where it sits in the example | Why the example depends on it |
|---|---|---|
| Conversation ID | Bot log, copied onto the ticket at 09:15 | The single key that joins the failed attempt to the repair |
| Routing event with time and target queue | Messaging routing event at 18:04 | Shows exactly where the task broke and why |
| Released or abandoned status | Conversation log at 18:09 | Proves the customer left without help |
| Detection source | Daily handoff report at 08:40 | Shows the company found the failure itself |
| Recovery action reference | Refund record in billing | Ties the fix to a real change, not just a note |
| Resolution reason code | Ticket field "failed handoff" | Lets the case be found again among thousands of ordinary tickets |
| Field and status history | Ticket audit trail | Zendesk stores an audit for each ticket update, with events such as field changes and comments, so the order of actions can be rebuilt |
| Verification window | Seven days without re-contact, refund settled | The weakest link, but the only evidence the fix held |
If the conversation ID had not been copied onto the ticket, the retailer would hold a failed conversation and an unrelated-looking refund. Both records would exist; the recovery would not.
What the example shows, and what it cannot
One case shows the shape of agent recovery data. It does not show that a company's archive is full of such cases, and it is worth being clear about the limits before anyone treats it as a template.
- Silence is weak proof. Seven days with no new contact may mean the customer was satisfied, or that they canceled. A refund that settled is firmer evidence than the silence.
- One recovery path is not the only right one. The refund-first choice was reasonable here. Whether it is the company's standard practice can only be seen across many cases.
- Bot and ticket records may not share a history. In the example both survive. In practice, conversation logs and tickets often sit in different tools with different retention, and that is decided per company in review.
- Recovery is not the same as root cause. The example records the fix for one customer, not the change to the billing queue's hours that would stop it happening again.
Who owns these records, and what stays unknown
In a company like the one described, support operations owns the conversation and ticket history, finance owns refund records, and IT administers the tools. Authority to discuss licensing usually sits with the COO, CFO or CEO.
The company, not just the records, has to qualify. It needs 50 or more full-time employees at peak (contractors excluded), documented operating history, rights to license the records, 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.
Unknown until SourceX reviews it: how many recoveries pass an acceptance check, how customer data is de-identified, whether the bot or help desk vendor's terms restrict use, and whether there is buyer interest in this task type. Industry interest in the concept does not mean every support archive qualifies. Discovery stays at metadata level; partners never ask for transcripts or tickets. The owner can prepare with questions to ask before licensing company data, and our guide to using historical tickets for a support agent covers the wider ticket archive. Other workflow record types are listed in the data types hub.
Go deeper on agent recovery data
- Questions to ask a client about agent recovery data: a short discovery script for checking whether a company's records could qualify.
- Record gaps that make agent recovery data hard to assess: a guide to the missing links and short retention that weaken a recovery archive.
- Agent recovery data review packet: a list of the metadata a company prepares before SourceX reviews its recovery records.
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 the support lead confirms that failed handoffs are logged and follow-up tickets carry the original conversation ID, register as a partner, check the company against who qualifies, and read the terms before you introduce the COO or CEO.