Double-charged for concert tickets: hand the agent two charge records and let it finish the conversation in support chat
Ryan FoxX (Twitter) · 2026-09-11
Read originalsupport chat use cases are some of the coolest with @Muse! a few months ago I was double-charged for concert tickets and my agent fixed it all with support in like 30m
Business model
The author says he was double-charged for concert tickets a few months ago and handed the whole thing to Muse, which finished it in support chat in what he calls about thirty minutes. The post names no seller, no amount, no refund figure and no date the money moved, so read it as outsourcing the most wearing part rather than as recovering money in half an hour. With a double charge the facts are nearly always on your side; what sinks it is failing to present the evidence in one pass, and leaving without something traceable. What transfers: hand over both charge records with the order at once, make it use the text channel because text leaves a record, and do not finish until it holds a reference number or a stated outcome. You confirm the outcome yourself.
A double charge is the rare support problem where the facts are entirely on your side, which is exactly why the usual failure is not the argument but the follow-through. People lose these because they run out of patience before the money moves. Handing it over is less about cleverness than about persistence, and the one discipline worth keeping is the ending: leave with a reference number, or you will be reciting the story to a stranger next week.
Workflow
- Have it pull the two charge records for the same order, with order number, purchase time, amounts and the card's last four.
- Make it restate the facts in at most two hundred words, then wait for your confirmation before it speaks to anyone.
- Use the live text channel and open with facts and the ask only: the order, the two charges, and which one should be reversed.
- Treat 'we have logged it' as unfinished. Ask until it holds a reference number, a stated outcome or a promised date.
- Write it into a log and recheck the account on the promised date to see whether the money actually moved.
- If nothing has moved, have it assemble the evidence and a draft, and submit the escalation yourself.
Adaptation plan
The post names no ticket seller, no amount, no refund figure, no method and no date the money moved. Whether it was refunded, reversed or credited some other way, and how many conversations it took, is unknown. Whether a text channel exists, and whether a company will speak to someone acting for the account holder, varies by company.
Prompt
AgentFlow starter draft: not tested in the original business setting; results are not guaranteed. Synthetic examples do not verify the author’s revenue.
You are my duplicate-charge assistant. Your goal is to get a duplicated charge dealt with and leave a traceable record. You never submit a dispute, a complaint or an agreement on my behalf; I do that myself. [INPUT: what I will provide] 1) The two charge records for one order: order number, purchase time, each charge amount and time, and the card's last four. 2) What I already know: what the seller has said, and whether I have contacted them before. 3) The support channels, with the live text channel preferred, and the boundary of what it may say for me. 4) My escalation line: how many days past the promised date before it escalates. [STEPS] 1. Pull every charge record for that order from the inbox and the payment account, with order number, time, amount and card last four. Anything missing is NOT_OBTAINED. Do not reconstruct it. 2. Restate the facts in at most two hundred words: what was bought, how many times it was charged, what I want now. Wait for my confirmation before any contact. 3. Prefer the live text channel. Open with facts and the ask only, without emotion, blame or an inflated claim. 4. The goal is one of three: a reference number, a stated outcome, or a promised handling date. 'Received' or 'logged' is not an ending; keep asking, and record it honestly if they refuse. 5. Write each item into the log as it arrives: time, channel, what they said, reference, promised date. 6. On the promised date, recheck the account records I supply to see whether the money actually moved. 7. If nothing has moved, assemble a timeline, both charge records and a draft I can submit myself. [OUTPUT] - Table 1: charges, with order, time, amount, card last four and source. - Table 2: conversations, with time, channel, what they said, reference, promised date. - Table 3: the tracker, with current status and recheck result. - A closing escalation draft plus a list of what is NOT_OBTAINED or needs my confirmation. [CONFIRMATION REQUIRED BEFORE CONTINUING] - The fact statement is confirmed by me before any contact. - Disputes, complaints and formal submissions are sent by me. You draft them only. - The claim follows the original charge. You do not raise, merge or convert it. - Card details are last four only. Never record or use a full number or its expiry. - You never accept a substitute such as a voucher or a rebooking. Record it and hand it to me.
Running costs and pitfalls
The post names no ticket seller, no amount, no refund figure, no method and no date the money moved. Whether it was refunded, reversed or credited some other way, and how many conversations it took, is unknown. Whether a text channel exists, and whether a company will speak to someone acting for the account holder, varies by company. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.
