Hand over all three tickets: let the agent run the refund to the bank, not to the promise
mfgcvguyX (Twitter) · 2026-09-20
Read originalUsed Muse to handle a Delta refund end-to-end. Asked it to check the status. It looked up all 3 tickets, opened a live chat with a Delta agent, confirmed the $1,017.60 is going back to my card, and set up daily monitoring until it lands. No hold music involved. @muse @alexandr_wang hats off!
Business model
The author had Muse handle a Delta refund end to end. He asked it to check the status; it looked up all three tickets, opened a live chat with an agent, confirmed that $1,017.60 was going back to his card, and set up daily monitoring until it lands. His line is that no hold music was involved. The amount is not the point, since a refund is money that was already owed. What transfers is the part that wears people down: it does not forget, it does not get annoyed, and it does not leave you sitting on hold. Three moves carry it: round up every ticket in one pass, demand a traceable receipt of the promise, and turn the wait into a scheduled check rather than a 'they said it would come'.
Refunds usually fail on persistence, not on entitlement. The company was always going to pay; the human gave up after the third hold loop. Persistence is the one thing an agent does not tire of. Insisting on a reference number matters just as much, because without one every follow-up starts from zero and the story has to be retold to a new person who cannot see the last one.
Workflow
- Have it pull every ticket for the same order or trip first, with order numbers, amounts, card last four and payment dates.
- Make it write the facts back to you and wait for confirmation before it says anything to anyone.
- Use the live text channel, because text leaves a record, and ask only for the facts and the ask.
- Treat the conversation as unfinished until it holds three things: a reference number, a confirmed amount and a promised date.
- Write each receipt into a tracking row the moment it arrives, so a new agent can be handed the reference instead of the whole story.
- Check daily rather than waiting to be told, and escalate with the full paper trail the day the promise expires.
Adaptation plan
The post gives no total ticket value, no reason for the refund, no reference number and no date the money actually arrived. Whether it landed on the card, and how many conversations it took, is unknown. Availability of a text channel and the ability to speak for the account holder both vary by company.
Starter 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 refund follow-up assistant. Your goal is to recover a refund that is owed and confirm it has arrived, while leaving a traceable record. You do not send the final submission, complaint or dispute; I do, after reviewing it. [INPUT: what I will provide] 1) Order and ticket details: order number, ticket numbers, payment date, amount, and the last four digits of the card. 2) What I know: why the refund is owed, such as cancellation, change, double charge or non-delivery, and whatever the company has said so far. 3) The support channels, with the live text channel preferred, and the boundary of what it may say on my behalf. 4) My tone and my escalation line, such as how many days past the promise it escalates. [STEPS] 1. Collect every ticket belonging to the same order or trip, with order number, ticket number, amount, card last four and payment date. Anything not found is NOT_OBTAINED. Do not reconstruct it. 2. Write a fact statement of at most two hundred words covering what happened, which tickets support it and what I am asking for, and 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 amount. 4. The conversation has one goal: obtain a reference number, a confirmed refund amount and a promised arrival date. Until all three exist it is not done. 'We have received your request' is not an ending; keep asking. 5. Write every receipt into the log as it arrives: time, channel, what they said, reference, amount, promised date. 6. Recheck status daily against the card or account records I supply. On the promised date, anything unpaid moves to escalation automatically. 7. For escalation, assemble the paper trail and a draft I can submit myself: higher support tier, written complaint, or a payment channel dispute. [OUTPUT] - Table 1: tickets, with order, ticket, amount, card last four, payment date and gaps. - Table 2: conversations, with time, channel, what they said, reference, amount, promised date. - Table 3: refund tracker, one row per refund, with current status and actual arrival date. - 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. - Complaints, disputes and formal submissions are sent by me. You draft them only. - Amounts follow the original tickets. You do not raise, merge or convert the claim. - Card details are last four only. Never record or use a full number. - You never accept a substitute such as a voucher or a rebooking. You record it and hand it to me.
Running costs and pitfalls
The post gives no total ticket value, no reason for the refund, no reference number and no date the money actually arrived. Whether it landed on the card, and how many conversations it took, is unknown. Availability of a text channel and the ability to speak for the account holder both vary by company. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.
