CUSTOMER SUPPORT
Refund Edge-Case Advisor for Intercom Conversations
When a customer asks for a refund in Intercom, an agent checks the request against your refund policy, drafts a compliant reply for the rep.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom refund conversationIntercom
- ActionFetch charges and refund history from StripeStripe
- ActionEvaluate request against refund policyOpenAI
- LogicBranch: in-policy vs. supervisor edge case
- ActionPost drafted reply as Intercom noteIntercom
- OutputFlag edge cases to Slack supervisor channelSlack
What it does
It turns every inbound refund request into a ready-to-send draft plus a clear verdict: in-policy, deny, or needs a supervisor. The agent reads the conversation, pulls the purchase context from Stripe, and applies your written refund policy so reps stop guessing on tricky cases.
When to use it
Use it when refund questions land in Intercom and your team needs consistent, policy-aligned answers — especially for edge cases like out-of-window requests, partial refunds, or repeat refunders that a junior rep shouldn't decide alone.
How it works
- 1A new Intercom conversation tagged or classified as a refund request triggers the flow.
- 2The agent pulls the customer's recent charges and refund history from Stripe for context.
- 3An OpenAI reasoning step compares the request to your refund policy and assigns a verdict with a rationale.
- 4A branch checks whether the case is clearly in-policy or an edge case (exceptions, high amount, prior refunds).
- 5In-policy cases get a drafted reply posted as an Intercom note for one-click send.
- 6Edge cases are posted to a Slack supervisor channel with the draft and the policy reasoning for human approval.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.
