Stripe Checkout Recovery Agent with Codex

Read the session, read the customer where there is one, then either create a draft or post a line. Codex moves quickly through that shape and is exact with the parts that must not drift: two seats at 18,000 INR each, the total, the currency, the product names as Stripe returned them.

Loading preview…
Free to start · guided setup

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

Succeeded

Expired 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:

  1. Connect Stripe

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Gmail

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  4. 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.

  5. Runs on Codex

    Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.

  6. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

Why Codex for this agent

Their basket, item by item

Quantities, product names and figures come out of the session rather than out of a template. What arrives is recognisably the cart they built, which is most of why these mails work.

Nothing is added up

The total is the one Stripe holds, never a sum the agent computed. Arithmetic inside a customer facing email is a risk with no upside.

Before you fork

Who actually sends these, and from which mailbox?

A person does, out of the Gmail account you connect, because everything the agent produces is a draft sitting in that mailbox. That is a review step built into the template rather than a setting somebody can flip. In practice one person clears the drafts folder once or twice a day and sends the ones that read right.

Run it with a different agent

Put Stripe Checkout Recovery Agent to work on Codex

Free to start. Guided setup, a test run against staged conversations, and it's live.