CUSTOMER SUPPORT
Stripe Dispute Refund-Policy Evidence Drafter
When a Stripe chargeback opens, it checks the disputed charge against your refund policy and either drafts evidence to contest it or routes a likely-loss case to a supervisor…
How it runs
The automated pipeline, trigger to output.
- TriggerStripe chargeback dispute created (webhook)Stripe
- ActionPull charge, customer, and prior refundsStripe
- ActionScore defensibility and draft evidenceOpenAI
- LogicBranch: winnable vs. likely-loss
- OutputNotify team evidence draft is readySlack
- OutputEscalate goodwill-refund cases to supervisorSlack
What it does
It reacts to new Stripe disputes by deciding, per your refund policy, whether the charge is defensible. Winnable disputes get a structured evidence draft; weak ones get routed to a human before you waste a fight you'll lose.
When to use it
Use it when chargebacks pile up and someone has to manually judge each one. This automates the first read — policy match, refund-window check, prior contact — and only pulls a supervisor in when judgment is genuinely required.
How it works
- 1A Stripe `charge.dispute.created` webhook triggers the flow with the dispute and charge details.
- 2The flow gathers the original charge, customer email, and any prior refund on that payment from Stripe.
- 3An OpenAI step scores defensibility against your refund policy and drafts contest evidence text.
- 4A logic branch splits high-confidence-winnable from low-confidence or out-of-policy disputes.
- 5Winnable cases store the drafted evidence package and notify the team it's ready to submit.
- 6Weak or ambiguous disputes are posted to a Slack supervisor thread recommending a goodwill refund and pause on contesting.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.