Refunds with guardrails
The purchase verified, your policy checked, the refund prepared and the customer answered, with the money step always waiting for you.
Chat
Connected apps.
Connect each one once. You sign in on the app's own screen, and you can disconnect any time.
Zendesk
Stripe
HubSpot
Gmail
Slack
An example run.
What the agent does, step by step, after you ask. This is an illustration; your results depend on your own data.
Refunds with guardrails
zendesk.get_ticketCustomer asks for a refund 9 days after purchaseDonestripe.get_chargeCharge of 240 dollars found, not yet refundedDonehubspot.get_companyNo previous refunds, customer for 2 yearsDonezendesk.search_articlesPolicy: refunds are allowed within 14 daysDonestripe.create_refundRefund 240 dollars to the original cardWaits for youzendesk.add_commentReply sent confirming the refundWaits for youslack.post_messageLogged in #support-opsDone
You stay in control.
Looking things up is automatic. Anything that changes something waits for you, and every step is logged.
Runs on its own
- Customer asks for a refund 9 days after purchase
- Charge of 240 dollars found, not yet refunded
- No previous refunds, customer for 2 years
- Policy: refunds are allowed within 14 days
- Logged in #support-ops
Waits for your approval
- Refund 240 dollars to the original card
- Reply sent confirming the refund
How it works.
Connect your apps
Zendesk, Stripe, HubSpot, Gmail, Slack. Setu keeps the sign-in secure and never shows your passwords to the agent.
Ask, or set a trigger
Run it when a refund is requested. You describe the job in your own words.
You stay in control
Reading is quick. Anything that writes or deletes can wait for your approval, and every step is logged.
More for customer support.
-
Customer support
Triage and route every ticket
“Triage the new tickets.”
Each ticket categorised, prioritised using the customer's plan and history, linked to bugs and sent to the right queue.
When a ticket arrives
-
Customer support
Escalation with full context
“Prepare the escalation for the Northwind ticket.”
Everything the next person needs, gathered first: the history, the account, the billing, what has been tried and what to do.
On request, or when a ticket escalates
-
Customer support
Close the help center gaps
“What do customers keep asking that our help center doesn't answer?”
Repeat questions found across channels, checked against existing articles, with drafts for the biggest gaps.
Every month
Give your agent real hands.
Connect an app, hand your agent the tools, and watch it finish the job.