Use casesTriage

Put every refund request in front of a person, ready to decide

Mitra builds an agent that matches every refund request to the actual payment in Stripe, then summarizes what that customer has paid, asked for and been refunded before. The whole case lands in Slack each morning beside the Zendesk ticket. A person decides — Mitra never issues a refund.

Runs: Every day at 10am
Used by: Customer Support · Ops / Chief of Staff

The prompt

Every morning at 10am, take the open refund requests in Zendesk and find each customer's payment in Stripe. Summarize what they paid, when, what they have been refunded before and what the ticket is asking for, then post each case to #refunds in Slack for one of us to decide.

Stripe

Zendesk

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Collects the day's requests
The agent reads the open Zendesk tickets asking for money back, along with the requester and what they say went wrong.
Finds the payment in Stripe
Each request is matched to the real charge: the amount, the date, the plan and whether any of the money has already gone back.
Summarizes the customer's history
How long they have paid, what they have asked for before and how any earlier refund was handled, in a few lines rather than four open tabs.
Hands the case to a person
The whole thing goes to your refunds channel as one post, so whoever is on duty can decide without opening Stripe themselves.
Leaves the decision alone
The agent never issues, approves or declines a refund — a person answers in the channel, and the run is recorded step by step.

Make it yours.

Support and ops teams where a refund means opening Stripe, rereading the ticket and guessing at the history. If refund requests sit for two days because gathering the facts is the slow part, this is the gap the agent closes. Change any of this by saying so — there is nothing to rewire.

Assemble cases only above a certain amount, and let smaller requests through to the usual queue.
Post each case as a private note on the Zendesk ticket instead of into a Slack channel.
Add the customer's recent invoices and failed payments, so a billing pattern shows up in the same post.

Questions, answered.

Can Mitra approve refunds?

No — Mitra assembles the case and a person decides. The agent matches the request to the Stripe payment, summarizes the customer's history and posts everything to Slack, then stops. Issuing or declining the refund is done by whoever is on duty, in the tools they already use.

How does Mitra match a refund request to the right payment?

Mitra looks the customer up in Stripe by the email on their Zendesk ticket, then reads their charges to find the one the request is about, by amount, date or plan. Anything ambiguous is posted with both candidates rather than a guess, so the person deciding can see the difference.