Changes in your services
The agent does not only read data from connected services, it also changes it: prices and stock, product cards, deal and contact fields, replies to reviews, emails and messages. This is the most useful part of the work — and the only one where a mistake costs more than the time spent.
The difference from a report is simple: a bad report you just redo, a bad edit has to be undone inside the service.
The three-step rule
Any change that touches more than one record is worth doing in three moves.
- The list, with no changes. "Show the products with stock under 5 whose price has not changed since May. Do not change anything." You see what actually matched the condition before anything happens.
- A pilot on 2–3 records. "Apply the new price to the first three items from that list." Open them in the service and confirm that what changed is what you expected.
- The rest, in groups. "Now apply it to the next twenty." Groups of 10–20 — not because the agent cannot handle a hundred, but because a mistake across twenty records is still one you can fix by hand.
“Update all the cards” is taken literally
"All", "everywhere", "the whole catalogue", "every customer" are exact instructions, not figures of speech. If 900 cards match the condition, all 900 are changed. Instead of "all", name the filter and the limit: "only items in Footwear with stock above 10, no more than 20 items at a time".
How to phrase it
| Instead of | Write |
|---|---|
| Update the product cards | Show the cards with no description in Footwear — a list, no changes |
| Raise prices by 10% | Raise the price by 10% on three items from the list above, then show me the result |
| Reply to the reviews | Draft replies to new reviews rated below 4 and show them as text — I will send them myself |
| Email the customers | Collect the customers unpaid for over 30 days and a draft email; send only after my "go ahead" |
What is always worth asking for
- An export before the edit — "first export the current prices and stock to a spreadsheet". That is your point of return.
- A report after it — "show a table: SKU, before, after". It shows both the result and what to restore if something went wrong.
- The exact account — name the service with
@and say which store or legal entity if there are several. An edit that landed in the wrong account is the most common way to damage data that was not yours to touch.
Actions that cannot be undone
A sent email, a message to a customer, a published reply to a review, a completed payment, a deleted record — none of these come back. For work like that, phrase the agent's role as preparation: "collect", "draft", "show me the list" — and keep the sending to yourself, or allow it with a separate message in the same chat.
Scheduled tasks that change things
A task runs without you, and there is no one to check with along the way. If a task changes data, put the limits into its wording — how many records and under what condition — and run it once by hand to see the result before it starts running on a schedule.
If too much changed
Say so in the same chat: "show me exactly what you changed in the last step" — the agent will list the records and their previous values while they are still in the conversation. From that list, and from the export made before the edit, the values go back the same way any edit is made: in groups, starting with a few records.
There is no "undo everything" button in the interface: the changes go straight into your service and live by its rules.