Support agents that improve
with every resolved ticket.
Policies, product notes, and resolved conversations become support context graphs. Your team answers consistently. Your agents stop repeating mistakes.
On the record
This has already happened, more than once. Each case links to the primary document, not to coverage of it.
A Canadian tribunal ordered Air Canada to pay CA$812.02 after its website chatbot told a customer they could claim a bereavement fare after already travelling. The airline’s real policy said the opposite, on a page the chatbot’s own answer linked to. The tribunal rejected the argument that customers should have to check one part of a website against another.
Moffatt v. Air Canada, 2024 BCCRT 149Cursor’s front-line support bot told users that logins were limited to one device per subscription. No such policy existed. Users were posting cancellations within about an hour; the co-founder’s correction landed three hours in.
Michael Truell, Cursor co-founder, on r/cursor
For support teams
One current answer per question. When a policy changes, every answer changes with it.
Start freeFor AI builders
Correct a support agent once and the fix applies to every future ticket. Not after a thousand more corrections.
Read the docsCorrect it once. The context layer improves for every future answer.
