Use casesTriage
Put every refund request in front of a person, ready to decide
Mitra matches every refund request to the actual payment in Stripe. The agent summarizes what that customer has paid, asked for and been refunded before. The whole case goes to Slack each morning beside the Zendesk ticket, and a person decides.
Every morning at 10am, match the open Zendesk refund requests to their Stripe payments. Post each case to #refunds with the customer's history.
200 credits to start · no credit card
What the agent actually does.
Collect the day's requests
The agent reads the open Zendesk tickets asking for money back, with the requester and what went wrong.
Find the payment in Stripe
Each request is matched to the real charge: the amount, the date, the plan and any money already returned.
Summarize the history
How long they have paid, what they asked for before and how any earlier refund went, in a few lines.
Hand the case over
The whole thing goes to your refunds channel as one post, so whoever is on duty decides without opening Stripe.
Leave the decision alone
The agent never issues, approves or declines a refund, and the run is recorded step by step.
Make it yours.
For teams where refund requests sit for two days because gathering the facts is the slow part. Change any of this by saying so — there is nothing to rewire.
- Assemble cases only above a certain amount, and let smaller ones through.
- Post each case as a private note on the Zendesk ticket instead.
- Add recent invoices and failed payments, so a billing pattern shows up.
Questions, answered.
Can Mitra approve refunds?
How does Mitra match a refund request to the right payment?
Ready to
reclaim your day?
Build my first agent200 free credits · no credit card · nothing to install