CUSTOMER SUPPORT
Refund decision brief for new Zendesk refund tickets
On a new Zendesk ticket about a refund, an agent assembles billing status from Stripe, usage and refund history from Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerNew refund ticket created in ZendeskZendesk
- ActionFetch Stripe billing status and invoicesStripe
- ActionQuery usage and prior refunds in PostgresPostgres
- LogicForm refund recommendation from policy
- OutputWrite eligibility brief as private Zendesk commentZendesk
What it does
Gives Zendesk agents a ready-made refund brief the moment a refund ticket lands. An agent reasons over the customer's Stripe billing state, recent usage, and refund track record, then drafts a private comment that states the recommended decision, the policy reasons behind it, and the numbers that matter — so the human reply is fast and defensible.
When to use it
Use it when refunds come through Zendesk and you want every agent to start from the same complete picture rather than reconstructing it ticket by ticket.
How it works
- 1A new Zendesk ticket matching your refund triggers (form or tag) starts the flow.
- 2The agent fetches Stripe subscription status, last invoice, and payment health for the requester.
- 3It queries Postgres for usage in the current period and prior refund events.
- 4The agent weighs the evidence against your refund policy and forms a recommendation.
- 5It writes a structured eligibility brief as a private internal comment on the Zendesk ticket.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.