Direct answer
Your AI bought the wrong thing. Win the refund with the pack, not the argument.
The box is wrong, the booking is wrong, or the size, date, or model is wrong, and the agent that ordered it has already reported success. Refunds and chargebacks are not won by explaining that an AI made a mistake. They are won by a small pack of evidence that shows, line by line, what you asked for and what actually happened. Here is the pack, in order.
Updated October 17, 2026.
First, work out which fight this is
Two different doors, and the evidence leans differently at each. The merchant refund fits when the purchase itself went wrong at the merchant's end: the wrong item shipped, the wrong dates booked, a duplicate order. You are showing the merchant a mismatch between what was ordered and what arrived. The card dispute (a chargeback) fits when the purchase as made was not the purchase you authorized: you told the agent to buy one thing and it bought another, or bought when it should only have looked. You are showing your card issuer a gap between your instruction and the charge. Many cases start at the merchant door, because it is faster, and move to the issuer when the merchant will not move.
The evidence pack: five pieces, in this order
1. Your instruction, as you gave it. The message or settings that told the agent what to buy: the item, the limits, the budget, the dates. Save it exactly as written, with its time. This is the piece most people cannot produce later, and it is the piece the whole case hangs on.
2. The purchase record. What was actually ordered: item and variant, quantity, total price, merchant, order id, and the time of the order, plus the confirmation that came back. If the purchase ran through a recording connection, this is the purchase step's saved result, fixed at the moment it returned.
3. The mismatch, shown side by side. One short paragraph, no adjectives: instructed X, ordered Y, arrived Z. Attach a photo of what arrived and the delivery or booking confirmation.
4. Your contact with the merchant. Dates, what you asked for, what they answered. Issuers ask whether you tried the merchant first; a clean short log answers it.
5. The money trail. The card statement line for the charge, matching the order id and total in piece 2.
How to present it
Send the pack as one message with one ask: the refund, the correction, or the reversal, named plainly in the first line. Keep the timeline on one page: instruction, order, arrival, contact. Whoever reads it (a support agent or an issuer reviewer) should be able to verify every line against an attachment in under two minutes. Anger adds nothing; a pack that checks out is what moves a case.
The sibling page in the Related list works the other half of this problem: the instruction record versus the purchase record inside Zambo, and the prevention half, the caps and sign-off gates that keep the next purchase inside the instruction.
What the record adds, and the scope limits
A verifiable receipt for the purchase step proves the saved result was not changed since it was saved: the order details that came back at purchase time are the order details you present. It does not prove your intent was wise, and it does not decide your case. Two fences on this page: everything here is general information about organizing evidence, not legal or financial advice, and no outcome is promised, because issuers and merchants decide disputes under their own policies. And Zambo never holds your money and cannot reverse a charge; the record is evidence, not a refund button.
Stop the sequel
Once the case is filed, close the setup that allowed it: a spend cap on the connection the agent buys through, so a wrong purchase is bounded, and a sign-off gate on purchases above a line you choose, so a person sees the exact order before it runs. Both leave records of their own, and both are cheaper than one wrong delivery.
Frequently asked questions
My AI bought the wrong thing. What evidence do I need for a refund or chargeback?
Five pieces, in order: your instruction exactly as you gave it, with its time; the purchase record (item and variant, quantity, total, merchant, order id, and the confirmation that came back); the mismatch shown side by side, instructed versus ordered versus arrived, with a photo of what arrived; your contact log with the merchant, dates and answers; and the card statement line matching the charge. If the purchase ran through Zambo, the purchase step carries a verifiable receipt, so the order details you present are the order details saved at purchase time. This is general information about organizing evidence, not legal or financial advice.
Will a chargeback work if I told the agent to buy it?
It depends on your issuer and its policies, and nobody honest can promise the outcome. What you control is the evidence of the gap: you authorized a specific purchase, and a different purchase was made. Issuers weigh that gap, your attempt to resolve it with the merchant first, and how fast you acted. The pack on this page is built to make that gap readable in two minutes. Where the agent bought exactly what you instructed and you simply regret it, that is a return, not a dispute, and the merchant's normal policy is the door.
What if the agent booked the wrong flight or hotel instead of buying a thing?
The same pack, with booking fields: your instruction (dates, route, travelers, budget), the booking record and confirmation code, the mismatch (the dates or names as booked against the instruction), your contact with the merchant or airline, and the statement line. Booking mistakes are time-sensitive in a way boxes are not, so start the merchant contact the same day, while change windows are still open, and keep the record of every step.
How fast do I need to act?
As fast as the records are fresh. Dispute windows vary by issuer, merchant, and jurisdiction, and this page cannot state yours. What does not vary: the instruction message, the order confirmation, and the agent's step record are easiest to assemble today and hardest in a month. Build the pack now, contact the merchant first, and keep every reply. Speed is the one variable in a dispute that is entirely yours.
How do I stop my agent from buying the wrong thing again?
Bound it and gate it. A spend cap on the connection the agent buys through limits the size of any single mistake, and refusals past the cap are recorded with their own receipts. A sign-off gate on purchases above your line means a person sees the exact order before it runs, and that approval is recorded too. The Day Pass covers 24 hours of capped, gated buying for $0.99, no subscription; the Zambo Pass is $29 a month or $290 a year, and $19 a month for $ZAMBO holders.
Your AI said "done." For $0.99, prove it: https://zambo.dev/day-pass/