CUSTOMER SUPPORT
Autonomous Refund Pre-Check and Reply Drafting Agent
An agent reads an incoming refund email, verifies the purchase in Stripe against the policy window, logs the decision to Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerNew refund email in shared inboxGmail
- ActionMatch sender to Stripe purchaseStripe
- LogicEvaluate against policy window
- ActionLog decision to Postgres audit tablePostgres
- OutputDraft customer reply for approvalGmail
What it does
This runs a refund request end to end as an agent task. It interprets the customer's message, confirms the matching Stripe purchase, applies the policy window, records the structured decision in Postgres for audit, and writes a finished, empathetic reply explaining the outcome and the reasoning, ready for an agent to approve and send.
When to use it
Use it when refund volume is high and you want consistent, well-written first-draft replies that already contain the eligibility decision and its justification, while keeping a human in the loop for the final send.
How it works
- 1A new refund email arriving in the shared inbox triggers the agent.
- 2The agent matches the sender to their Stripe purchase and reads the charge date and amount.
- 3It evaluates the purchase against the policy window and any exceptions.
- 4It writes the structured decision and rationale to a Postgres audit table.
- 5It drafts the customer reply with the verdict and reasoning and routes it for human approval.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.