CUSTOMER SUPPORT
Refund-vs-dispute pre-check on new Stripe disputes
When Stripe opens a dispute, this gathers the charge, usage, and prior refund history, decides whether a proactive refund is cheaper than fighting it.
How it runs
The automated pipeline, trigger to output.
- TriggerStripe dispute created eventStripe
- ActionFetch dispute and original charge detailsStripe
- ActionQuery usage and refund history in PostgresPostgres
- LogicCompare proactive refund vs contesting cost
- OutputPost recommendation to Slack disputes channelSlack
What it does
When a chargeback dispute opens in Stripe, it builds the case file your team needs to decide fast: refund proactively to avoid dispute fees, or contest with evidence. It pulls the disputed charge, the customer's actual product usage, and whether they've been refunded before, then recommends the cheaper path and posts it for the disputes team.
When to use it
Use it when chargebacks are eating into margin and you want a consistent, cost-aware first call on every new dispute instead of reacting case by case under the response deadline.
How it works
- 1A `charge.dispute.created` event from Stripe triggers the flow.
- 2Stripe is queried for the dispute amount, reason code, and original charge details.
- 3Postgres returns the customer's usage and prior refund history.
- 4A logic step compares the dispute fee plus loss risk against a proactive refund and picks the lower-cost action.
- 5The recommendation and supporting evidence are posted to a Slack disputes channel for sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.