Charged twice, or the order never arrived.
An online fashion store. After every campaign, the inbox fills with payment questions.
Not every question is a refund
The assistant works out what the customer wants first. A delivery question goes to your team with the chat; it is never turned into a refund.
- Intent first, then action
- Asks when unclear
- Handoff with the transcript
Refund asked 45 days after purchase
Outside the 30-day refund window
Transcript · 6 messages
Guest checkout? An email code
The customer proves the address with a six-digit code, picks the duplicate charge and confirms. It is refunded once, however often they press.
- Email code for guests
- One refund per request, guaranteed
- Reasons your policy accepts
Confirm your email
We sent a six-digit code to j•••@example.com
VerifyWhich payment do you mean?
Chargebacks answered on time
When a “not received” dispute arrives, evidence is drafted from your records and filed before the deadline.
- Evidence from stored facts
- Filed before the deadline
- Every dispute becomes a case
Dispute evidence
Respond by 23 Oct
More in Use cases
Start with low limits. Raise them when the record shows it works.
Start in test mode, run your policy against your own history, and go live when the results meet your standards.
- 1A test workspace on your provider’s test mode
- 2Your past requests replayed against your policy
- 3Live with low limits, raised as the record allows