CUSTOMER SUPPORT
Refund Window Validator for Intercom Conversations
Checks whether an Intercom refund conversation falls inside your return window by comparing the Stripe charge date to policy.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom refund conversation openedIntercom
- ActionMatch customer to latest Stripe chargeStripe
- LogicCompute elapsed days vs policy window
- OutputAdd window verdict note to conversationIntercom
What it does
When a customer asks for a refund in Intercom, this agent finds their Stripe charge, computes how many days have passed since the payment, and compares that to your configured refund window. It posts an internal reply telling the agent exactly whether the charge is still inside the window, how many days remain, and the charge date — so policy is applied consistently instead of guessed.
When to use it
Use it when your refund policy is time-bound (e.g. 30 days) and agents are eyeballing dates or making inconsistent exceptions. It turns the window check into a single deterministic answer.
How it works
- 1An Intercom conversation tagged as a refund inquiry triggers the flow.
- 2The agent resolves the customer's email to their most recent matching Stripe charge.
- 3It calculates elapsed days from the charge timestamp to now.
- 4Window logic compares elapsed days against the policy threshold.
- 5An internal note is added to the Intercom conversation with the verdict and days remaining.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 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 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.