Keep support knowledge when people move on

A customer asks about an unusual account change. The new agent finds a help article, an old ticket, and a private note. Each gives a slightly different answer. The person who used to handle these cases has left.

The missing piece is more than documentation. The team needs to know which answer is current, when it applies, who approved it, and what to do when the case falls outside it.

Experienced agents often fill those gaps from memory. That helps today’s customer, but it leaves the next agent dependent on the same person.

A reusable support answer should explain:

• The question or situation it covers.
• The approved answer or next step.
• The conditions and exceptions that matter.
• The source and the person responsible for keeping it current.
• When the agent should ask for help.

Use a real example when it clarifies an exception, but remove customer details that are not needed. Separate the general policy from a one-off decision so the exception does not quietly become the rule.

Write for someone who did not work on the original case. If the answer depends on an unexplained abbreviation or an unwritten assumption, it is not ready to stand on its own.

Every important source needs someone responsible for it. That person does not have to write every answer, but they should know when a policy changes and how corrections are reviewed.

Agree on a review schedule that fits the material. A frequently changing product process needs different attention from a stable policy. Also review content when customer questions reveal a gap or when agents repeatedly correct the same answer.

Keep revision history where possible. It helps the team understand what changed and investigate why an older answer was used.

Give a teammate a few representative questions and ask them to find the answers using the documented sources. Include one case with an exception and one that should be escalated.

Notice where they hesitate. Are search terms different from the words in the article? Are two sources competing? Is the next step missing? These problems are easier to fix when you see them in use.

Repeat the same exercise when introducing AI assistance. A source can be accurate but still incomplete for a customer’s question. Review whether the answer uses the right information and recognises the limits of that information.

When an agent resolves an unfamiliar case, ask whether it reveals a reusable answer or an exception worth documenting. Keep the review small enough that it can happen during the working week.

Do not turn every conversation into permanent guidance. Review the proposed lesson, confirm it with the right owner, and then update the shared source. A past reply is evidence of what happened, not automatic proof of current policy.

Replofy Knowledge brings website and PDF sources together with editing, revision history, source health, and evaluations. Your team can maintain the information it uses and make that knowledge available to Aura.

Start with the questions that depend most on a particular teammate. Document the answer, name its owner, and test whether someone else can use it. That is a practical way to make support knowledge last beyond any one person.