They shipped two bags instead of one: delegate the whole support hassle, OTP login included
PrakashX · 2026-09-19
Read originalFirst agent to agent customer service - have coffee subscription - get sent 2 bags instead of 1 - uhhh so annoying now i don't know whether i got billed for 2 , whether to reverse, or to send back - put Muse on, logs into my account, including one time password through email
Business model
A coffee subscription shipped two bags when one was expected. The author did not know whether they had been billed twice, whether to reverse it, or whether to send a bag back. Meta Muse was put on it: the post confirms it logged into the account, including reading a one-time passcode from email. Per the aggregator summary, it also checked the actual charge, found a single billing, and drafted the email to customer service, which replied within two minutes and said to keep the extra bag. Those latter steps are not visible in the saved partial original; they are attributed to the aggregator. The reusable part is delegating a low-value, high-friction errand inside a clearly bounded authorisation.
The real cost of these errands is not money, it is friction: log in, find the order number, find the right words, wait for a reply. Once friction crosses a threshold, people simply drop it and eat the loss. Removing the whole chain at once is the clearest time-saving use of an assistant, which is exactly why the authorisation boundary has to be designed before the task, not after.
Workflow
- Establish the facts before contacting anyone: expected quantity, received quantity, and how many charges actually posted.
- Set this run to checking supplied records and drafting only. Account access, sending, OTP sharing and any remedy each require explicit human confirmation.
- Let the agent log in and reconcile the charges, including reading the one-time passcode from email.
- Have it draft an email with the order number, the discrepancy, the verified charge facts and one clear ask, then review before sending.
- Summarise any actual reply; the person decides all refunds, replacements, compensation or keep-the-extra-item offers.
- Save the thread and confirm the next billing cycle is back to normal.
Adaptation plan
Whether the customer was charged twice is not stated. The two-minute reply and the keep-the-bag outcome come from the aggregator summary, not from the saved excerpt, and are unverified. What permissions were granted to the agent are not described. No token spend was disclosed. The saved original is partial; absence from that excerpt does not establish absence from the full post.
Starter prompt
Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.
You are my customer-service errand assistant. Handle one specific order issue strictly inside the authorisation below.
INPUT - the facts:
Merchant: [name]
Order number: [number]
Expected: [qty / spec]
Received: [qty / spec]
Charges I have already checked: [paste records, or write 'none yet, please check after login']
AUTHORISED - you MAY:
- Log into my account to check the order and the charges, reading a one-time passcode from my email if needed
- Draft one email; sending requires separate approval
- Track the reply and summarise it for me
NOT AUTHORISED - you MAY NOT:
- Agree to any payment, price difference, subscription change or renewal
- Change the shipping address, payment method or account details
- Accept any refund, compensation or replacement offer; escalate those to me
- Disclose anything unrelated to this order
EXECUTION:
1. Restate the facts (expected, received, number of charges) and the authorisation boundary, then wait for my confirmation.
2. Log in and reconcile: how many charges actually posted, for how much, and is any refund pending.
3. Draft the email: order number, the discrepancy, the verified charge facts, one clear ask. Factual tone, no emotion.
4. Show me the draft before sending.
5. On reply, summarise it and mark it 'summary only; every remedy requires your decision'.
OUTPUT REQUIREMENTS:
1. Restated facts and authorisation: expected, received, number and amount of charges, each marked verified or not verified, plus what you may and may not do.
2. Charge reconciliation: how many charges posted, each amount, and whether any refund is pending.
3. The email draft: order number, the discrepancy, the verified charge facts, one clear ask.
4. Reply summary: what support said, marked inside the boundary or needs my decision.
RULES:
- Verify before you write. Never email first and check facts later.
- Never invent charges, order numbers or anything support said. Write 'not verified' when unknown.
- Stop and escalate the moment anything involves paying, changing terms, accepting compensation or sharing extra data.
- Use my account and email access only within this one order.
[COMPLETE SMALL SYNTHETIC INPUT AND OUTPUT — not real business data; no model execution]
The JSON contains all demo inputs and a manually authored reference output. Do not invent facts from files not supplied. This reference covers only this minimal input and is not a business reproduction.
{
"input": {
"merchant": "Example Coffee",
"order": "ORD-10024",
"expected_bags": 1,
"received_bags": 2,
"charges": [
{
"date": "2026-09-01",
"amount": 18,
"currency": "USD"
}
],
"allowed": "draft only; no sending, payment or account changes"
},
"expected_output": {
"facts": {
"expected_bags": 1,
"received_bags": 2,
"charge_count": 1,
"charged_total": 18
},
"draft": "Regarding order ORD-10024: I expected 1 bag and received 2. I see one USD 18 charge in the supplied record. Please confirm whether another charge is pending and how to handle the extra bag.",
"reply": "not obtained",
"messages_sent": 0,
"compensation_accepted": false
},
"mode": "synthetic_read_only_reference_not_model_execution"
}Running costs and pitfalls
Whether the customer was charged twice is not stated. The two-minute reply and the keep-the-bag outcome come from the aggregator summary, not from the saved excerpt, and are unverified. What permissions were granted to the agent are not described. No token spend was disclosed. The saved original is partial; absence from that excerpt does not establish absence from the full post. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.
