FINANCE
Front Duplicate-Charge Auto-Refund Resolver
Detects conversations reporting a duplicate charge, confirms the duplicate against Stripe, issues a refund for the second charge, and replies to the customer in Front.
How it runs
The automated pipeline, trigger to output.
- TriggerDuplicate-charge complaint in FrontFront
- ActionLook up matching charges in windowStripe
- LogicConfirm duplicate and check refund ceiling
- ActionIssue refund on the later chargeStripe
- OutputReply and resolve conversationFront
What it does
This workflow handles the most common, clear-cut billing complaint: being charged twice. It confirms the customer was actually double-billed by inspecting Stripe charges within a short window, refunds the redundant charge automatically when it is below your auto-approve threshold, and closes the loop with the customer in Front — no agent touch required for the easy cases.
When to use it
Use it when duplicate-charge tickets are high volume and low risk, and you want sub-minute resolution instead of a multi-step manual refund. Larger amounts fall back to a human queue.
How it works
- 1A Front conversation classified as a duplicate-charge complaint triggers the run.
- 2Stripe is queried for charges to that customer in the last 72 hours with matching amounts.
- 3Branch logic confirms a true duplicate and checks the amount against the auto-refund ceiling.
- 4For approved cases, Stripe issues a refund on the later charge; over-ceiling cases route to a manual queue in Front.
- 5Front replies to the customer confirming the refund and resolves the conversation.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Finance workflows
Detect Annual-to-Monthly Downgrade Refunds Owed
Catches subscriptions switched from an annual term to monthly partway through the prepaid year, computes the unused prepaid balance owed back.
Detect Mid-Cycle Plan Change Mischarges and Queue Credit Memos
Listens for Stripe subscription plan changes, recomputes the correct prorated amount.
Expense Submission Webhook Instant Triage and Routing
Receives each expense submission via webhook the instant it's filed, classifies it as in-policy, needs-review, or hard-violation, and routes it to auto-approval.
Accrual Chase Board in Monday with Per-Owner Tasks
On a schedule it reads open uncoded expenses from Snowflake and creates or updates a Monday item per department owner.
Real-Time Uncoded Expense Nudge on New Spend Event
When a new expense lands without a GL code, a webhook fires and the workflow immediately Slack-nudges the spending owner to code it on the spot.
Monthly Vendor Spend Anomaly Brief for Finance Leads
Once a month, an agent analyzes the full expense ledger for vendor and category spend anomalies, drafts a narrative brief with the top outliers and likely causes.
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.