Fixing a wrong automated reply: 4 steps
In Editing a live step you tested changes before customers saw them. Some errors still reach customers unnoticed. Fixing the rule is not enough: whoever got the reply is still acting on it. The fix is four steps, in order: stop the error, find who received it, correct each group with one owner-approved message, then record the cause and add a check. Personal data sent to the wrong person is a breach, possibly with a legal deadline.
A case from the floor
A building supplies store answers price questions on WhatsApp: a contractor asks "How much is a bag of cement?" and gets the VAT-inclusive price. At 9:10 am on Monday a clerk uploaded the new price list, priced before VAT, but the reply labels prices as inclusive, so it quoted SAR 18 a bag, not SAR 20.70.
Nobody noticed until Tuesday noon, when a contractor paying at the counter saw a different price. By the 1:20 pm pause, 23 customers had the wrong price: 17 only asked, and 6 confirmed orders totalling 700 bags, two already paid by transfer.
Four steps, in order
- Stop the error before fixing it. Roll back if the saved version is still valid, or pause the step and route questions to staff until the cause is clear; no rushed patch. Note the stop time to the minute: it closes the window.
- Find the window and who got the reply. It runs from the edit logged in your automation register, or the first wrong reply if none, to the stop time. Pull every logged conversation in between and sort them: asked only, ordered, paid or delivered; each needs its own correction.
- Correct each group with one owner-approved message. Handling those affected is the owner's decision, not each employee's. The owner honoured the quoted price on the 6 confirmed orders, a SAR 1,890 difference, and sent the rest the correct price with an apology. Each correction states what was wrong, what is right, what you will do for them, and whom to contact.
- Record the cause and add a check. Log the incident in your exception log: window, recipients, cost and root cause. Here the list was right, but the reply assumed every price included VAT, so every upload now asks: inclusive or before VAT? Then resume with the restart checks.
Sizing the correction
| Error | Example | Correction |
|---|---|---|
| Confusing wording, no financial impact | A vague reply on opening hours | Fix it; if needed, tell those who asked |
| Wrong price or amount | A pre-VAT price shown as inclusive | Owner's decision per group; message every recipient |
| Wrong date or promise | A delivery day the branch cannot meet | Contact them beforehand with a set alternative |
| Personal data to the wrong person | A statement sent to another customer | Stop at once, assess harm, notify as the law requires |
When the reply carries personal data
The Implementing Regulation of the Personal Data Protection Law, published in the Umm Al-Qura Gazette on 7 September 2023, defines a personal data breach to include any incident that discloses personal data, intentionally or not, by automated or manual means. Its Article 24 requires your business to document corrective measures and, if the breach may harm the data or data subject or conflict with their rights or interests, to notify the competent authority, SDAIA (the Saudi Data and AI Authority), within 72 hours of learning of it, and the data subject without undue delay, in simple, clear language. Missing details follow as soon as possible, with reasons for the delay. Official Arabic text: https://uqn.gov.sa/details?p=23595
When the correction starts on WhatsApp
If the step runs inside your system with its messages logged, finding who got the reply is one question. The owner sends "Who got the wrong cement price?" and the system replies: "From Monday's 9:10 am list edit to Tuesday's 1:20 pm pause, 23 customers: 17 only asked; 6 ordered, 2 of them paid. Draft a correction per group for approval?" The owner's answer is the recorded decision. More on quotes and invoices over WhatsApp.
Three common mistakes
- A blanket apology. One message to all confuses those the error missed and tells those it reached nothing specific.
- Letting each employee decide. One customer keeps the quoted price, another pays the correct one and feels cheated.
- Erasing the evidence. Deleting messages or editing the log loses the window and recipients; Article 24 requires documenting a breach's corrective measures.