An auto-reply rule is a claim about your catalog at a moment in time. Written in September, it says the bundle costs 89 and ships in two days — and it will keep saying that, fluently and instantly, long after the price moved and the courier changed. When the catalog changes, the automation does not notice on its own. Teams that run chat automation reliably treat rule maintenance as part of catalog operations: the same event that updates the price sheet also updates the rules that quote it. Stale rules cause more wrong replies than bad grammar or thin knowledge ever do, because they sound confident while being out of date.
A Wrong Answer From a Stale Rule Costs More Than Silence
A missing answer costs one follow-up question. A wrong answer costs more, in three ways. First, money: a customer who booked the price you quoted last week has a screenshot, and "the page was old" reads as a retraction, not an excuse. Second, fulfillment: an upbeat "yes, in stock" on an item that sold out overnight produces conversations about orders that cannot ship. Third, trust in the channel itself — once customers learn the bot's numbers drift, they stop believing its correct answers too. Speed and consistency are what automation is good at, and those strengths are precisely what make an outdated reply sound authoritative.
Three Kinds of Change, Three Blast Radii
Price edits are narrow but sharp. Every rule, template, and knowledge entry that quotes a number inherits the change. This is why price belongs in a table, not in prose: a library of ready-to-use reply templates for online sellers keeps quotes coming from a price sheet — with discounts beyond your authority escalated to a human — so the sync job becomes updating one sheet instead of hunting through forty scripts.
Stock changes are binary flips — in stock, sold out, restock date — plus the quieter drift of shipping times during a surge. Both directions matter: a stale "yes" oversells, and a forgotten "sold out" rule keeps turning away buyers after the restock lands.
Promotion switches have two halves, and teams forget the second one. Adding the new campaign rule is half the job; retiring the old one is the other half. A specific rule outranks a default, so an expired promotion keeps firing until it is removed, not merely superseded.
The Change-Day Checklist
Run this list on the day the catalog changes, before the first customer asks:
- Find every dependent rule. Search the script library and knowledge base for the SKU, the old price, and the campaign name. Quoted numbers hide in greetings and follow-ups, not just in pricing rules.
- Update the source of truth first, then the rules that read from it. Editing the price sheet and the scripts in separate sittings is how they diverge.
- End-date the old rule. Retire the previous promotion explicitly, in the same stroke that adds the new one.
- Sweep for time-bound phrasing. "Until Sunday," "this week's offer," "while stocks last" — anything that expires with the event.
- Tell the humans the same day. Staff quote from memory when the system is slow, and they need the new numbers even more than the bot does.
- Log the change with a date, so a wrong reply three weeks later can be traced to what was known when.
Keep the Layers, Sync the Differences
If your replies are tiered by customer segment, a price change should touch one master figure plus each segment's difference points — not ten near-copies. A guide to tiered reply scripts keyed to customer tags structures this with a three-column mapping table — tag, scenario, differentiation point — where differentiation means swapping names, cases, entry points, and tone rather than rewriting the whole script. The table is what makes a change-day edit small: the price lives once, and the segments carry the wording around it.
Audit the Week After
The week after any catalog change, pull reply hit rates and handoff counts for the affected topics. A spike in escalations usually means a rule is answering wrongly or has gone quiet; a spike in repeated questions means the update missed a template. The same tiered-scripts guide recommends re-reading the mapping table on a monthly rhythm, so drift gets caught between catalog events instead of accumulating underneath them. Rule maintenance is not glamorous, but it is the difference between an assistant that quotes the shop you have and one that quotes the shop you were running last month.
Top comments (0)