Stripe Checkout Recovery Agent with OpenCode
This is short customer facing writing under hard constraints: three paragraphs, their own cart quoted back, and no offer that is not in your policy word for word. OpenCode leaves the model open, which counts for more here than in a reporting job, since the output is prose a buyer will read.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Payment
SucceededExpired checkout
priya.raghavan@northloop.in · cs_live_a1Fq7Zc9RmT4
Created 4 August at 14:02 IST and expired unpaid twenty four hours later. Cart: 2 x Studio annual seats at 18,000 INR each, total 36,000 INR. The session carries customer cus_QtR8m2Vd, an account opened in June that has never paid for anything, and the payment page was opened three separate times.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Stripe
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Recovery policy
What you are willing to say to somebody who did not finish paying: the tone, how quickly the mail goes out, any offer you genuinely make and its exact wording, the cart value above which a person writes instead, and who should never be chased at all. Anything absent from this is not on the table.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
Prose with a hard fence
The writing is judged on tone and the fence is judged on obedience. Raising the model to improve the first while the second stays fixed is what a model agnostic harness buys you here.
One nudge, never a sequence
A single draft per expired session, written as though they got distracted, because they did. Nothing follows it and no second run is scheduled.
Before you fork
If the drafts read badly, do I have to rebuild anything to try another model?
No. The Stripe connection, the Gmail mailbox, the Slack channel and the recovery policy all stay where they are, and the model is one field on the agent. Compare two engines on the same staged sessions and read the drafts side by side before either meets a real shopper.
Run it with a different agent
Put Stripe Checkout Recovery Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.