A customer’s AI asked to change the order. That line is not a signature
On 24 September 2026 Business Insider described people handing hold music, bill arguments, and cancellations to their own agents, and support staff starting to wonder who was on the line. The article cites a 2026 Accenture survey of more than 25,000 people in 16 countries: about three quarters would hand a routine complaint to an agent, and under one in ten would let it buy on its own. That is stated intent, not your inbound mix this month. It is enough to set a rule. The sentence in front of you may not have been typed by the account holder.
Most small firms do not run a call center. The message arrives on LINE, a form, or email. The rule is the same as on a phone line: that sentence is not a signature yet. If it says “cancel 1044 and ship to this new address,” the person on duty does not edit that order on the spot. The cost of a wrong edit is freight and a complaint, not one extra reply. Later the account holder says they never cancelled, and all you hold is a text that does not prove who sent it. What you can check is the email already stored on the account, the last digits they left at checkout, and the confirm already in the member record. If those three do not match this message, do not change the order. Stock and the address stay as they were.
The duty sheet does not need a new product. First, both the assistant and the person on shift only state status they can read: where the order is, what it cost, when it is due to leave. Read that from your system, not from the sender’s story. Second, cancel, refund, address, and line items land in a pending queue, not in done. Third, the confirm goes to the email or the in-site thread already on the order, not to a new account pasted into this LINE chat. Fourth, stock and payment stay as they were until that confirm returns. Those four steps are the scope the person on duty and the assistant keep together. They do not change because a different model shipped this month. Cancel and address changes still land in pending, not in done.
Your own support assistant follows the same rule. If it can look up an order, it only states status the back office can read. If it wants to write onto the order, it shows the fields and waits for the person on duty, or for the inbox already on the order, before it writes. Low confidence goes to a human, with a note of who took the thread. That is the scope on AI support: knowledge approved first, a confirm before a record is kept, a handoff that names someone. The rollout order is in the LINE note. Whether the other side uses their own agent does not change the rule: before a write lands on the order, confirm on the email stored with the account.
Do not put “detect whether this was written by AI” at the door. Detectors block real people and miss careful sentences. The door is permission: may this message change this order. If it does not match the email on the order, reply that a confirm is on its way to the email stored with the order. That reply is cheaper than shipping the wrong goods. The “under one in ten would let an agent buy” line is a reminder, not a target. Most people in that survey were not ready to let a machine pay. You should not treat an inbound text as a new order that is already paid.
If the LINE official account already answers by itself, the admin checks one thing this week: does that assistant’s tool list include cancel-order or change-address. If those two write tools are on the list, the admin removes them from the list and leaves the assistant able only to open a ticket a person can see. The ticket stays pending until the person on duty decides whether to change the order. If the list has no write tools and the assistant can only talk, the chance of a wrong order is much smaller. It still must not say “I have cancelled that for you.” The buyer will treat that sentence as done. Who may turn writing on, and how far a write may go, is the other note, leave the assistant off until an admin enables it.
Two lines a shift actually gets
Evening on the official LINE account: “I am Mr Wang’s assistant. Move tomorrow’s booking to the day after, and use the new door number in this message.” The email on Mr Wang’s booking does not match this chat. The person on duty does not move that booking on the calendar. They ask the sender to answer the mail already on the booking. Next day he writes that he was busy and did not ask to move it. Because the calendar never changed, you do not owe a second apology for a booking you did not move.
The other message is a smaller case, and it looks like your own form talking, not someone claiming to be an assistant. Three submits in ten minutes, the same items, the recipient name off by one character each time. That might be an agent, or a person tapping submit. Treat them the same way: all three stay pending, and you do not ship all three. The person on duty asks the email stored on the first submit which of the three to keep. Until that inbox replies, stock does not move.
Questions
How do we detect an agent?
Often you cannot tell whether an agent wrote it. A human tone, a fast reply, and three fields at once are not proof. The check is whether this message matches an order you already have, and the contact stored on that order. If it does not match, do not change that order. Do not spend the shift guessing whether the sender is a bot.
May our own assistant promise a cancellation?
No. Cancel, refund, a new address, and a price change wait for the person on duty, or for the confirm step you already use. The assistant may look up order status and may draft a reply. It may not treat that sentence as a signature and mark the order cancelled.
Does this apply to our LINE bot?
Yes. Your assistant is answering on the official account, and the other side may be asking through their own assistant. Both sides use one rule: before anything is written onto the order, confirm on the email already stored on the account, or on the in-site thread. If that confirm does not come back, the order stays as it was.
Set what the assistant may write How AI support is wired
Source: Business Insider, 24 Sep 2026. The Accenture figures are as that article reports them, not ZhuYun’s inbound stats.