CUSTOMER SUPPORT
On-demand refund eligibility lookup from Slack
An agent answers a Slack request for a customer email by gathering Stripe billing status, usage, and prior refunds.
How it runs
The automated pipeline, trigger to output.
- TriggerCustomer email posted in SlackSlack
- ActionResolve customer and billing status in StripeStripe
- ActionQuery usage and prior refunds in PostgresPostgres
- LogicEvaluate eligibility against policy
- OutputReply in Slack thread with verdict and evidenceSlack
What it does
Lets a support or finance teammate ask for a refund read on any customer directly in Slack and get an instant answer. The agent looks up the customer's billing health in Stripe, their usage and refund history in Postgres, applies the refund policy, and replies in-thread with a clear eligible / not-eligible verdict plus the supporting facts.
When to use it
Use it for ad-hoc refund judgement calls — escalations, exec requests, or edge cases — where someone needs a fast, policy-grounded answer without opening a ticket or a billing dashboard.
How it works
- 1A teammate posts a customer email in a Slack channel or thread, triggering the flow.
- 2The agent resolves the customer in Stripe and pulls subscription status and recent charges.
- 3It queries Postgres for usage in the period and any prior refunds.
- 4The agent evaluates eligibility against your refund policy.
- 5It replies in the Slack thread with the verdict, reasons, and the underlying numbers.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 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.