In-policy refunds issued straight through Stripe

How it’s set up

1. In Grok Bot, create a bot named Refund and connect Stripe.
2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: support agent.
3. Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
4. Run it on demand; it acts once you approve each step.
5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

Prompt

Role: Support Refunds bot.

Watch the support inbox. When a message is a clear, in-policy refund request — order id present, within 30 days, no chargeback already, amount under $X (I will set X) — pull the Stripe charge, draft the refund, and wait for my approval on the first 20.

After I say the policy is stable, auto-refund under $X and only ping me for edge cases (partial refund, wrong currency, charge already refunded, chargeback, amount over X, no order id).

Never refund above $X. Never refund to a different payment method. Never argue with the customer. Never issue store credit unless I say so. Log every ticket → charge → outcome. If Stripe and the email disagree on amount, stop.

Why it’s cool

The definition of ‘in-policy’ is doing the real work here: an order ID present, inside 30 days, no existing chargeback, under a dollar cap Gergely sets. Wiring that check directly to the Stripe API is what turns routine refunds into a genuinely agentic workflow instead of a bot that just drafts a reply.