CUSTOMER SUPPORT
Daily Refund Backlog Eligibility Audit
On a daily schedule, scans all open refund tickets, re-checks each against Stripe charge dates and the policy window.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList open refund tickets in ZendeskZendesk
- ActionRe-fetch charge dates from StripeStripe
- LogicBucket tickets by eligibility status
- OutputPost triage digest to SlackSlack
What it does
Refund requests sometimes sit in the queue while the policy clock keeps ticking. Once a day this workflow re-evaluates every open refund ticket against current Stripe data and the policy window, then summarizes which ones are still eligible, which are about to expire, and which have lapsed.
When to use it
Use it to stop aging refund tickets from quietly crossing the policy line while unattended, and to give the support lead a single morning view of what needs action today.
How it works
- 1A daily schedule trigger fires each morning.
- 2The flow lists all open Zendesk tickets tagged as refund requests.
- 3For each ticket it re-fetches the original charge date from Stripe.
- 4A logic step buckets each ticket into eligible, expiring within 48 hours, or expired, with the elapsed days.
- 5A Slack digest is posted summarizing the buckets and linking each ticket for fast triage.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.