Initial training is a starting point. Hours change, services expand and a temporary offer can outlive its intended end date in a forgotten document. Knowledge maintenance gives the business a repeatable way to approve those changes and check the answers callers hear afterward.
Keep this process focused on the company’s actual rules. An assistant should not learn a new public promise merely because one caller requested an exception. Conversation review can reveal a question worth answering; an authorized person still decides the answer.
Give every important answer an owner
Identify who approves services, prices, availability wording, payment instructions and escalation routes. The same person need not own every subject. Record where the accepted answer comes from and which business it applies to. When several brands share a team, a correction for one brand should not silently change another brand’s policy. Keep unresolved disagreements out of the live answer set until the responsible people decide.
Separate a proposed change from an approved one
A useful change request contains the old wording, proposed wording, reason, affected business and intended effective date. Ask whether existing estimates or bookings follow the old rule. Preserve the distinction between a future policy and the answer that applies today. Use whatever review and versioning workflow the installation actually supports; do not assume that editing an external document automatically updates the live phone agent.
- What changed, and for which company?
- Who approved it?
- When should the answer apply?
- Which exceptions or previous commitments remain?
Test the questions around the change
Testing a new price answer requires more than asking for that exact price. Ask about the minimum, excluded services, discounts and a customer who received an older estimate. If office hours change, rehearse an after-hours caller and the human fallback. Use fictional details. Compare the spoken response with the approved wording and confirm that it stays concise while offering more detail when requested.
Use conversation review to find gaps
Look for repeated uncertainty, conflicting answers, unnecessary repetition and requests that routinely reach a human. These are signals for investigation rather than instructions to add more text automatically. A missing answer may need a new policy; a confusing answer may only need clearer wording. Summarize themes without copying private customer details into a public knowledge document or a demonstration. Keep audio-quality complaints distinct from factual knowledge problems.
Maintain a small review routine
Consider a fictional equipment-rental company that adds a new collection window. The operations owner approves the window, explains which existing reservations are unaffected and supplies a fallback when availability is uncertain. The team tests collection questions, late-return questions and a caller requesting an exception. A representative confirms that the updated version is the one used by the activated receptionist before the old answer is retired.
Choose a review rhythm appropriate to how often the business changes, and add an immediate review when a meaningful policy changes. Keep a short list of unresolved questions with owners. Confirm deployment or activation status after edits, because a correct saved draft can coexist with an older running agent. Rehearsal results are useful evidence, but they do not prove live CRM delivery or provider routing.