Which customer support AI can actually process a refund?

There is a video on YouTube from a support vendor with a title along the lines of automating 80% of customer support with a single agent. It is a good video. What it does not dwell on is that the last 20% contains almost all of the money.

Because answering “what is your refund policy” is easy. Every AI agent built in the last two years can do it. Answering “I want my money back for order 4417” requires the agent to look up an order, check it against a policy, decide whether the customer qualifies, and then move actual money. That is a completely different problem, and most tools sold as customer support AI cannot do it.

Why refunds are the real test

Refunds sit at the intersection of the three things AI support finds hardest: querying an external system, applying judgement, and taking an irreversible action. Every other support task is easier than this one.

It is also the ticket type customers care most about. Nobody escalates because a chatbot explained shipping times poorly. They escalate when they want money back and cannot get it.

One of the pages currently ranking for this question, published by My AskAI, scores tools on a dimension it calls money guardrails. That is exactly the right frame. Once an AI can issue refunds, the question stops being how well it converses and becomes how much authority you are comfortable giving it.

Three tiers of capability

Sort the market this way and it becomes much easier to shortlist.

• Explains the policy. The agent reads your help centre and describes how refunds work. Useful for deflection, useless for resolution. Most cheap tools live here.
• Looks up the order. The agent can query your commerce system and tell the customer the status of a specific order. Genuinely helpful, and still hands off to a human for the actual refund.
• Executes the refund. The agent processes it. This requires a real integration and a decision about how much money you will let software move without a person in the loop.

The distinction that matters on this table is between the middle column and the marketing. Nearly every vendor here will tell you it handles refunds. What most of them mean is that it handles refund conversations.

The custom actions trap

Fin, Zendesk and most general-purpose platforms can execute refunds through custom actions that call your APIs mid-conversation. This is genuinely capable and it is the thing teams most consistently underestimate during evaluation.

Custom actions are engineering work. Somebody has to build the endpoint, handle authentication, define the error cases and decide what happens when the refund fails halfway. It does not arrive configured. Teams demo the conversational quality, sign, and then discover the capability they bought requires a sprint to switch on.

The purpose-built commerce tools avoid this by shipping the Shopify integration already built. That is the entire reason Gorgias exists as a separate product rather than a Zendesk app.

How much money should it be allowed to move?

This is the question to settle before you shortlist anything, and it is a business decision rather than a technical one.

• Set a value ceiling. Below it the agent refunds automatically; above it a human approves. Most teams land somewhere between $50 and $200.
• Require an audit trail. Every automated refund should be reconstructible afterwards: who asked, what the agent checked, why it approved.
• Decide about repeat requesters. A customer requesting their fourth refund this quarter is a pattern, and an agent that cannot see the pattern will approve it.
• Define the failure path. If the payment processor rejects the refund, the customer must not be told it succeeded.

Return abuse is a real category of loss here. One tool covered in the ranking results, ReturnGO, exists specifically to catch return abuse before refunds are processed by analysing customer history and policy violations. That is a signal about where automated refunds go wrong at scale.

What the self-serve crowd actually uses

A thread on r/AI_Customer_Support settles on Chatbase paired with AI Actions and a Shopify or Stripe integration as the strongest self-serve route to order and refund automation. That is a reasonable answer for a small store, and it is worth being clear about what it involves: you are wiring the actions yourself.

For anyone not wanting to build, the honest shortlist for Shopify is Gorgias first and Yuma second, because the integration is the product rather than a project.

We have not yet run refund requests through these platforms ourselves. This post classifies capability from vendor documentation and integration surface, not from measured performance. Our own refund test on a live Shopify store is scheduled and will replace this classification when it is done.

The short version

If refunds are the reason you are buying AI support, ignore autonomy percentages entirely and ask one question: can it execute the refund, and what did it have to integrate with to do that? On Shopify the answer is usually Gorgias or Yuma. On a general platform the answer is yes with custom actions, which means budget engineering time. And whatever you choose, set the value ceiling before you switch it on rather than after the first surprise.

WRITTEN BY AR · UPDATED 2026-07-28

I run the testing here. Every platform on this site gets the same ticket set, the same escalation cases, and the same billing period — and I publish the invoice, not the marketing number. Where I have not tested something, the page says so.

How we test · About the author