The repeated question became an entry once, not an answer every time.
A small support team knew most calls by the opening sentence: hours, documents, prices, preparation, delivery or how a policy worked. The answers were familiar but varied slightly by person, and the genuinely unusual requests waited behind them.
The team approved a concise entry for each repeated question. SayTrue answers from that set across phone, chat and social channels, logs the source used, and records the questions it could not answer. Those gaps become the next editing queue rather than an invitation to improvise.
The support lead can inspect which entry supported a reply and which phrase still failed to find one. Editing remains a small operational loop: approve the fact, test the hardest wording, publish it, and watch whether the same question disappears from the gap list.