Revenue
Catch the cancellation before it is a cancellation
A cancellation message is the most valuable thing in a support queue and usually the slowest to get answered. This one reads the account, works out whether the customer is worth an offer, and asks a person before discounting anything.
Retention lives in whoever happens to be on shift. The customer who has paid for three years gets the same canned reply as the one who signed up last week, because nobody has time to look up which is which before answering.
a year is where enterprise agent platforms start, before a helpdesk seat.
Published 2026 vendor pricing
The flow
What runs when the message arrives.
Every step below is a real node type on the canvas, and the log underneath is the execution it produces. A branch the run didn't take stays dark, same as it would in the console.
- 01agent.invokecancel-guard · ses_7c04queued
- 02messages.loadmanaged · 3 turns14ms
- 03moderation.checkflagged: false88ms
- 04tool.httpGET /v1/subscriptions/311200 · 112ms
- 05conditiontenure > 12mo → true1ms
- 06llm.calldrafts retention offer455ms
- 07human.waitinbox · approve 20%paused
- 08agent.returnoffer sent · retained1.41s
What it uses
What this leans on.
The account decides, not the wording
A CEL condition reads tenure, plan and usage straight off what your API returned. Who gets an offer is a rule you can read, not a paragraph buried in a prompt.
Nothing costly is sent unapproved
The discount goes to the Inbox as a confirm step. The model drafts it and a person decides.
Run it on a delay
Queue the follow-up for tomorrow with `run-async?delay=`, then cancel it if the customer replies first.
The reason is kept
Write the churn reason to a bucket on the way out, with an expiry if it shouldn't outlive the quarter.
What it meters
One execution per cancellation handled, plus the bucket writes the flow makes. The queued follow-up is a second execution.
More
Other things people build.
Sales
Lead qualification
Enrich the form submission, score it against your criteria, write it to the CRM and route it. Triggered by the webhook your form already sends.
ReadBack office
API orchestration
Turn a sequence of internal API calls into one request. Templated, branching and recorded, with no model anywhere in it.
ReadCustomer support
Support chatbot
Answer from your own help content, check the customer's account when the answer depends on it, and hand over to a person when it should.
Read