CUSTOMER SUPPORT
Daily Sweep of Pending Refund Tickets Against Stripe
Runs on a schedule to re-check every open refund ticket in Zendesk against current Stripe state, then posts a digest to Slack listing tickets now safe to refund, already…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList open pending-refund tickets in ZendeskZendesk
- ActionRe-fetch current Stripe charge state per ticketStripe
- LogicBucket as eligible, refunded, or disputed
- OutputPost status-change digest to SlackSlack
What it does
Refund tickets often sit waiting on a settlement or a hold to clear. This scheduled agent sweeps all open refund tickets each morning, re-pulls their Stripe charge state, and sorts them: now eligible, already refunded elsewhere, or newly disputed. It posts a single Slack digest so the team works the unblocked ones first and closes the ones that resolved themselves.
When to use it
Use it when refund tickets pile up in a holding state and someone has to manually re-check Stripe each day. It surfaces exactly which tickets changed status overnight.
How it works
- 1A daily schedule triggers the sweep.
- 2The agent lists all open Zendesk tickets tagged as pending refunds.
- 3For each, it re-fetches the current charge and dispute state from Stripe.
- 4Logic buckets each ticket into now-eligible, already-refunded, or disputed.
- 5A consolidated digest of all three buckets is posted to Slack.
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.