CUSTOMER SUPPORT
Refund Pre-Check Copilot for Support Agents in Chat
A chat agent that takes a customer email or order ID, validates refund eligibility against live Stripe charge and subscription data.
How it runs
The automated pipeline, trigger to output.
- TriggerAgent sends refund question in chat
- ActionResolve identifier to Stripe customer and chargesStripe
- ActionRetrieve subscription for prorationStripe
- LogicDecide full, prorated, or declined and draft rationaleOpenAI
- OutputReturn recommendation and reply wording in chat
What it does
This is an interactive copilot for support agents. An agent drops a customer email or order ID into chat and asks whether a refund is allowed. The agent pulls the matching Stripe charge plus any active subscription, checks refund/dispute state, amount, and prorated subscription rules, then returns a recommended action: full refund, prorated refund, or decline — with a customer-ready explanation the agent can adapt.
When to use it
Use it for ad-hoc refund questions that don't start as a structured ticket — live chat, phone follow-ups, or escalations where the agent just needs a fast, policy-grounded answer and suggested wording.
How it works
- 1An agent sends a refund question with a customer identifier in chat.
- 2The agent resolves the identifier to the Stripe customer and active charges.
- 3It retrieves any subscription to compute prorated refund eligibility.
- 4Policy logic determines full, prorated, or declined and drafts the rationale.
- 5The recommendation and customer-ready wording are returned in the chat reply.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect OpenAIModels, embeddings, files.
- 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 Customer Support workflows
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.
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.
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.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.