Give the agent one authorised instruction and let it negotiate the bill
Invest-4-Tomorrow with KayeX · 2026-09-22
Read originalWell... that escalated quickly. 😂 Less than 24 hours after posting this, I actually gave Muse the job. “Negotiate my Verizon internet bill.” It logged into my account, reviewed the existing discounts, chatted with Verizon and negotiated: $89.99 → $69.99/month for 12 months +$100 gift card Total value: $340. I basically watched. This is the first AI product in a while that has given me that original ChatGPT “holy shit” feeling. ChatGPT showed consumers that AI can ANSWER things. Muse is showing consumers that AI can DO things. Still very early, but if $META can bring this experience to the mass market, I think people are underestimating how big consumer agentic AI could become.
Business model
Kaye gave Muse a single instruction: negotiate my Verizon internet bill. It logged into her account, reviewed the discounts already applied, spoke to Verizon's online support and moved the monthly charge from $89.99 to $69.99 for 12 months, plus a $100 gift card, which the author values at about $340 in total. Her line is that she basically watched. What transfers is not the amount. It is the shape of the delegation: one instruction with account authority, a target price and a stop condition beats ten variations of 'help me save money'.
The barrier to bill negotiation is not wording, it is willingness to sit in a support queue. Hand that time cost to the agent and the number becomes reachable. What makes the agent effective is the fact list underneath it: without current discounts and expiry dates, the conversation never gets past 'can you make it cheaper'.
Workflow
- Write the delegation as one task with three constraints: you may log into my account, here is my target monthly price, and if you cannot get it, report back rather than pushing.
- Make it produce a fact list first: plan, current discounts with expiry dates, contract end date, and competitor pricing in the area.
- Negotiate in order: can the existing discount be renewed or stacked, is there a competitor price-match or loyalty policy, and only then name the target price.
- Confirm four things yourself before accepting: how many months the price lasts, whether it binds a new contract term, what the early termination penalty is, and what the price reverts to.
- Archive the outcome, the ticket number and the confirmation wording, and set a reminder one month before the discount expires.
- For a later review, reuse the confirmed fact list and update expiry dates and competitor quotes; do not assume another negotiation will be faster or successful.
Adaptation plan
The discount terms, contract status and whether the gift card actually arrived are not in the post. Whether identity verification (an SMS code, typically) required the author mid-flow is not stated. Whether the same outcome is reachable with providers that offer no online chat is untested.
Starter prompt
Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.
You are my bill negotiation assistant. I will authorise you to log into my provider account and talk to online support. Your goal is a lower monthly charge, but you must give me a fact list first, and you must report honestly if it fails. You may not accept worse terms in order to close.
[INPUT: what I will provide]
1) Provider name and account access, authorised while I am present.
2) What I pay now: plan name, monthly charge, discounts I believe are applied.
3) My target monthly price and the longest contract term I will accept.
4) Published competitor pricing for comparable service, which I will supply or you may look up; if you cannot find it, write NOT_OBTAINED.
5) My hard limits: changes I will never accept, such as a pricier speed tier, a longer term, or add-ons I do not use.
[STEPS]
1. After logging in, first output a fact list: plan and monthly charge, each active discount with its expiry, contract end date, early termination fee, unused credits or rewards. Mark anything unavailable as NOT_OBTAINED.
2. Send me that list and wait. Do not contact support until I confirm.
3. With online support, go in this order: can the existing discount be renewed or stacked, is there a competitor price-match or loyalty policy, and only then state my target price. Keep everything in text and preserve the transcript.
4. For every offer, ask three things: how many months the price holds, whether it binds a new term and what the penalty is, and what the price becomes afterwards. If they will not say, record it as UNCONFIRMED, not as obtained.
5. If any offer requires changing plan, adding services or extending the term, stop and report to me. Do not accept it yourself.
6. Output a result table: new monthly charge, discount validity, any new contract, compensation form such as a gift card or bill credit, and when to negotiate next.
7. Record ticket numbers and the exact wording support used to confirm.
[OUTPUT]
- Table 1: pre-negotiation fact list including NOT_OBTAINED items.
- Table 2: negotiation summary, what was offered, what was refused, how many transfers.
- Table 3: result table with the five fields above.
- A closing list of things only I can confirm or supply.
[CONFIRMATION REQUIRED BEFORE IT COUNTS AS A WIN]
- I confirm discount validity, any new contract and the post-expiry price myself; verbal promises do not count.
- Any offer that requires a plan change, add-on or longer term is my decision, not yours.
- You may not cross any hard limit I listed in order to get a result.
- Gift cards and credits are not cash reductions and must be listed separately with their conditions.
[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": {
"currency": "USD",
"current_monthly_price": 89.99,
"target_max_monthly_price": 70,
"max_contract_months": 12,
"support_response": null,
"discount_expiry": null,
"gift_card_terms": null
},
"expected_output": {
"current_monthly_price": 89.99,
"target_max_monthly_price": 70,
"new_monthly_price": "not obtained",
"discount_term": "not obtained",
"contract_penalty": "not obtained",
"reversion_price": "not obtained",
"gift_card": "not obtained",
"savings_realised": 0,
"contract_accepted": false,
"next_action": "draft questions and wait for an actual written support offer; do not invent a negotiated result"
},
"mode": "synthetic_read_only_reference_not_model_execution"
}Running costs and pitfalls
The discount terms, contract status and whether the gift card actually arrived are not in the post. Whether identity verification (an SMS code, typically) required the author mid-flow is not stated. Whether the same outcome is reachable with providers that offer no online chat is untested. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.