Refunds, goodwill credits,
instantly settled — with audit.
Support agents issue refunds, send goodwill gift cards, and ship replacement orders without escalating every $40 decision. Per-customer caps, per-week budgets, signed audit trail on every payout.
Why the corporate card
doesn't work for this agent.
Every refund escalates
Tier-1 agent has to ping a tier-2 manager to approve a $35 goodwill credit. The manager is in a meeting. The customer waits 2 hours. CSAT drops 11 points.
Goodwill credits leak
Agents have access to a shared 'goodwill' fund with no per-agent budget. One bad month and the fund is exhausted; the next month nobody knows where the money went.
No attribution
Refund issued through Zendesk → Stripe → bank — three systems, three IDs, zero linkage. Finance can't tell which support tickets caused which dollars of refunds.
Everything this agent needs.
Nothing it doesn't.
From mandate to settlement.
Ticket arrives
Zendesk routes a refund request to the support agent. Agent reads the ticket, customer history, order context, and chargeback risk.
Within policy
Agent decides on a $40 refund + a $10 Amazon goodwill card. Both under per-customer cap, under weekly budget. No human required.
Both settle live
Refund settles on the original card in 4 seconds. Gift card SMS lands in 3 seconds. Customer is happy before the agent's typing indicator stops.
Linked to ticket
Both ledger rows tagged with the Zendesk ticket ID. Manager dashboard shows weekly burn, per-agent, per-ticket-category. Quarter-close is one CSV away.
Plug-and-play merchant lists.
Curated merchant allowlists ship with the wallet template. Add your own in one API call or one click in the portal.
Defaults you can flex.
| Per-agent weekly budget | $10,000 |
| Per-customer 30-day cap | $200 |
| Single-refund cap | $150 |
| Goodwill gift max | $50 |
| Manager-approval ≥ | $200 |
| Refund rail | Original payment method |
Everything else you need to know.
Why support agents bottleneck on refunds.
Support agents — human or AI — are the slowest part of most refund flows because every dollar of goodwill requires an approval. The bottleneck isn't the customer (they want resolution); it isn't the agent (the agent knows the right call); it's the manager who has to look at a $35 goodwill credit and sign off. In practice, this means CSAT drops because the customer waits, and managers spend half their time approving micro-decisions instead of coaching.
AgentWallet eliminates the bottleneck by giving each support agent a real budget. Within the budget, the agent transacts freely — refunds settle on the original rail, goodwill gift cards SMS in seconds, replacement orders ship on a scoped card. Above the budget, the agent escalates with full context, and the manager makes one decision per shift instead of forty.
Per-customer caps that prevent goodwill abuse.
Without per-customer caps, the same customer can extract unlimited goodwill by opening repeated tickets — sometimes legitimately, often not. The 'professional refund-hunter' is a real cohort for any consumer brand at scale. AgentWallet enforces a per-customer 30-day cap (configurable; default $200) across all agents in your account. The 41st ticket from the same customer this month is escalated automatically.
The cap is enforced at the wallet level, not at the helpdesk level, so it works across multiple support channels (Zendesk, Intercom, Front) and across multiple agents. The customer's payout history is queryable: GET /api/customers/:id/payouts?from=…&to=…. Managers see exactly who they're saying yes to repeatedly.
Refunds on the original rail, settled in seconds.
A refund that lands 7 business days later is a refund the customer remembers as 'late' even when it's the original payment processor's standard timeline. AgentWallet's refund tool routes to the fastest available reverse path: card refunds via the network (typically same-day), ACH returns where supported, USDC reverse-transfer in seconds, Pix instant-refund in 8 seconds.
If the original payment is a card, the refund is issued through the card network's standard refund flow — visible on the customer's card statement within minutes on most issuers. If the original payment is USDC, the funds are returned to the source wallet inside one block. If the original payment was bank-rail, the agent issues an instant rail refund (FedNow, SEPA Instant, Pix) where the bank supports it, falling back to ACH return where not.
Ticket-aware attribution for refund metrics.
Refund metrics are notoriously hard to compute because the data lives in three systems: the helpdesk (ticket category, agent, customer), the payment processor (amount, rail, timestamp), and the financial GL (expense category). AgentWallet collapses this by carrying the helpdesk ticket ID as the trace ID on every refund. One SQL join produces refund-per-ticket-category, refund-per-agent, refund-per-customer-segment in seconds.
Many support teams discover that 6% of their ticket types account for 60% of their refund spend — usually a specific bug or a specific failure mode in the product. With attribution automatic, the support team can hand engineering a Friday-afternoon list of 'these 6 issues cost us $48k in refunds this month, please prioritize.'
Common questions.
- Can the agent issue partial refunds?
- Yes. The refund tool takes ticket_id and amount; the amount can be any value up to the original payment minus any prior refunds. Partial refunds are tracked at the line-item level if the original order had line items captured.
- What helpdesks integrate natively?
- Zendesk, Intercom, Front, Help Scout, Freshdesk, and Salesforce Service Cloud have webhook-based native integrations. Any helpdesk with outbound webhooks can be wired in 15 minutes.
- How do you stop one bad agent from burning through the goodwill budget?
- Per-agent weekly budgets are the structural protection. Above the budget, escalation. Per-customer caps prevent extraction by one chatty customer. Per-shift summary reports flag any agent whose payout rate is more than 2x the team median.
- What's the goodwill gift card flow technically?
- Agent calls send_gift_card({customer_id, merchant, amount, channel: 'sms'}). AgentWallet sources the gift card from the merchant's API (via Tango Card or Rybbon depending on merchant), captures the redemption code, and SMSs the customer. The ledger row records the merchant, the amount, and the redemption code (hashed).
- Does the agent learn over time which refunds win disputes?
- AgentWallet provides the data (dispute outcomes are recorded against each refund); the learning model is your support stack's responsibility. We expose the data, we don't ship the model.
- Can a manager retroactively claw back a refund the agent issued?
- On card refunds, no — once the network refund is settled, it's customer-side. On gift cards before redemption, yes — the gift card can be voided. On bank-rail refunds, recovery depends on the rail. The audit trail captures everything; the recovery options depend on rail mechanics, not on us.
Ship this agent today.
Provision a wallet, attach a verified principal, set caps, plug into your LLM via MCP. Live in under a minute.