CUSTOMER SUPPORT
Refund Eligibility Pre-Check on New Zendesk Ticket
When a refund request arrives in Zendesk, it checks the original Stripe charge date against your policy window.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Zendesk ticket tagged refund-requestZendesk
- ActionLook up customer's latest charge in StripeStripe
- LogicCompare charge date to policy window
- LogicDraft eligibility rationale
- OutputPost verdict as internal note on ticketZendesk
What it does
Every new Zendesk ticket tagged as a refund request is scored against your refund policy before a human touches it. It pulls the original purchase date from Stripe, compares it to the configured window (for example 30 days), and writes a clear eligible / not-eligible verdict plus the reasoning as an internal note on the ticket.
When to use it
Use it when agents waste time manually looking up purchase dates and re-reading the policy on every refund ask. It removes the guesswork and gives a consistent, auditable decision before the reply goes out.
How it works
- 1A new Zendesk ticket tagged `refund-request` fires the trigger.
- 2The flow extracts the customer email and looks up their most recent charge in Stripe.
- 3A logic step compares the charge date to the policy window and flags edge cases (no charge found, multiple charges).
- 4It drafts a short rationale citing the exact dates and the rule applied.
- 5The verdict and rationale are posted as an internal note on the ticket for the agent to confirm and send.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 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
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.