Classify why the answer was missing
Use separate labels for absent content, outdated content, failed retrieval and a decision requiring human approval. Adding another FAQ will not fix a broken connection or authorize an exception. Save a de-identified question, expected source and observed failure. Group equivalent questions without discarding language differences that may reveal a retrieval issue.
Prioritize impact and recurrence
Count affected conversations rather than the number of repeated messages in one thread. Review frequency, customer impact and the effort to obtain an approved answer. For a bilingual US–Saudi operation, keep a language column: an answer may exist in English while Arabic questions fail to reach it. Assign a content owner and retest a held-out question after the change.
Fictional worked example
In a fictional week, eight conversations ask whether a delivery address can change after dispatch. Six have no approved policy; two had the correct article but the search missed it. The first group needs an owner decision and new content. The second needs a retrieval investigation. Reporting all eight as 'missing articles' would hide the difference and overstate the benefit of writing more pages.
Action checklist
- Log question, language, failure type, source, owner and next action.
- Count unique affected conversations within a fixed period.
- Resolve the policy before writing an authoritative answer.
- Retest with a new wording and close the gap only after review.