Published November 4, 2026

A review routine that finds stale support articles, macros, and saved replies after a policy change before an agent sends the old answer. The notes below keep the customer request, the approved source, and the next owner in one reviewable place. They are written for a support team that may hand the case to another shift. Use the routine to review one ordinary case and one exception before changing the workflow.

Name the change and its scope

A policy change can affect a refund window, a cancellation rule, an eligibility test, or a safety instruction. The review should start with the approved change notice, the effective date, and the customer scenarios it touches. Without that scope, the team will either update too little or rewrite the entire knowledge base. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

List the articles, macros, saved replies, and training notes that mention the affected rule. Include the pages that link to those articles, because a correct article can still be reached through an outdated summary. The list should show the owner and the last review date for each item. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Separate customer-facing text from internal procedure. The article may need new customer wording, while the internal note may need a new approval path. Both should be reviewed, but they should not be mixed into one document that agents cannot scan during a call. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Check the live version, not the draft

A draft update is not a live answer. The reviewer should open the article in the same system the agent uses and confirm the published version, the effective date, and the audience. If the team uses variants by region or product, check the variant that applies to the affected customer. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Record the article version and the review time. If a macro links to the article, test the link in the live queue. A broken link or a redirect to the homepage is a failed update even when the new text is correct. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Ask an agent who did not write the update to read the article as a customer would. They should be able to state what changed, who it applies to, and what the customer should do next. If they need the policy memo to explain it, the article is not ready. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Retire the old answer

Leaving the old macro available because someone might still need it creates a second source of truth. Retire the old version from the live queue, mark the replacement, and keep the history in the archive. The agent should see only the current approved answer. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

If an old answer must remain for a transition period, label the dates and the conditions in the title. A note buried in the body is easy to miss during a busy call. The queue should make the current version the obvious choice. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Check saved replies in personal or team templates as well as the central library. A local copy can survive a central update and be sent months later. The review should include a way for agents to report stray copies without editing them alone. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Route exceptions to the owner

A policy change may create cases the article cannot answer, such as a purchase made before the effective date or a customer who was given the old promise. The article should name the exception owner and the information needed to review the case. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

The agent can record the facts and route the question, but should not invent a transition rule. If the customer was told the old policy in writing, preserve that message and let the owner decide whether it applies. The record should show the promise and the date. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Track exceptions during the first weeks after the change. A cluster of similar cases may mean the article is missing a transition note or the customer communication was unclear. The pattern should lead to a targeted update, not a longer general article. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Review the library after launch

After the change has been live for a short period, sample calls and messages that used the new article. Check whether customers asked follow-up questions that the article should have answered, and whether agents added local explanations that belong in the approved text. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Compare the old and new answer for the same scenario. If the new answer is correct but much harder to use, the wording may need another pass. A policy can be accurate and still fail as a support tool. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

End the review with one owner, one change, and one date for the next check. A knowledge base is never finished, but it can be kept current with a small, repeatable routine. The goal is a customer answer the team can stand behind. Record the evidence and the next owner before the case leaves the queue. Keep the note usable by the next reviewer.

Sources