Create a small source register
For important answers, record the approved source, responsible person and last meaningful review. Start with information that can cause a wrong purchase or an unfulfillable promise if it becomes stale. Do not build a large knowledge repository merely to appear organised. A short reliable register is more useful than hundreds of copied paragraphs with no owner. Keep internal credentials and unnecessary customer information out of the answer library.
Tie reviews to actual changes
Product launches, policy revisions, pricing changes and altered contact routes should trigger a review of affected answers. A calendar review can catch missed changes, but it is not a substitute for notifying the support team when the business changes something important. Identify which canned responses and public pages rely on the same fact. Updating one location while leaving another unchanged creates conflicting guidance that agents and customers must then reconcile.
Distinguish facts from suggested wording
The approved fact may be stable while the wording needs to adapt to a particular question. Label conditions and exceptions clearly so a reusable answer does not become an unconditional claim. If the source is uncertain, do not polish the sentence until it sounds definitive. Escalate the factual gap and give responders a truthful interim answer. The quality of the knowledge is more important than the apparent fluency of the response.
Retire and verify
When an answer is replaced, remove or clearly archive the obsolete version through the supported process. Test a representative search or shortcut to confirm that agents reach the current answer. Review later conversations for the same misunderstanding and correct the website where appropriate. This is an evidence-based improvement loop, not a promise that a knowledge tool will maintain itself. Someone remains responsible for noticing when the underlying business reality has changed.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- LiveChat canned responses — Merchant documentation · livechat.com · Merchant-controlled · checked 2026-09-19