Articles · Answer quality
Before You Trust an AI Answer, Check Its Source
A practical guide to resolving conflicting business information, assigning FAQ owners and keeping the sources behind customer answers current.
A customer asks a simple question: “Is the installation included?” Your website says yes, an older brochure says it costs extra, and a team member remembers a promotion that ended last month. An AI assistant can only give a dependable answer when the business has decided which information applies.
Checking the source means more than finding a sentence that supports an answer. The information must be approved, current and relevant to the customer's service, location and circumstances. This guide explains how to build that discipline into business FAQs and everyday content maintenance. These are operating practices; the tools available to carry them out depend on your setup.
Start with four questions about the source
Before approving a customer answer, ask:
Who approved this information? Identify the person or team responsible for the policy, price or service detail.
When does it apply? Check its effective date, expiry date and any temporary exceptions.
What does it cover? Confirm the relevant branch, service, package, customer group or geography.
What is still unknown? Separate confirmed facts from details that require a quotation, availability check or staff decision.
A newer file is not automatically the correct source. A draft document created yesterday may be less authoritative than an approved policy from last month. Equally, a previously approved source can become unsuitable after the business changes its terms.
Create an approved source register
Use a small register to make responsibility visible. A spreadsheet or shared document can be enough; the important part is that staff know where to find it and who maintains it. Give each topic a stable reference rather than relying on filenames such as “final-v3-new”.
Topic and reference: A clear identifier, such as pricing: standard installation
Approved source: The controlled document or page containing the agreed facts
Owner and approver: The people responsible for updates and approval
Scope: Applicable services, branches, packages and exceptions
Effective and review dates: When the facts take effect and when they need checking again
Status and next action: Approved, awaiting clarification or retired, with the reason
Keep sensitive internal details out of material intended for customer answers. The register may contain internal ownership notes; the approved customer-facing answer should contain only information appropriate to share.
Resolve conflicts before rewriting the answer
When two sources disagree, record the conflict in plain language. Identify the exact statements, where they appear and the circumstances they cover. Avoid blending both versions into a compromise that nobody has approved.
Hypothetical example: a home-services website says “installation included”, while a price list says “installation from RM80”. The service owner confirms that standard installation is included only with Package A, at selected locations, while additional work requires a quotation. The business then approves wording that explains those conditions.
A useful resolution sequence is:
Collect both statements and the source references.
Check whether they actually describe different packages, branches or dates.
Ask the responsible owner to confirm the applicable rule and exceptions.
Update the approved source and the affected customer answer.
Correct or retire the conflicting public and internal material.
Test a question that would previously have produced the wrong answer.
If the conflict remains unresolved, do not present either version as certain. A holding answer can explain that a specific detail needs confirmation and direct the enquiry to the appropriate person. Do not promise a response time that the team cannot support.
Write answers that keep their conditions attached
Business facts often lose meaning when shortened. “Delivery is free” may originally mean “delivery is free within a defined area for orders above a minimum value”. Preserve the conditions customers need to make a decision, even when the answer is concise.
A useful answer structure is: confirmed fact, relevant condition, remaining uncertainty and next step. For example: “Standard installation is included with Package A at the listed service locations. Additional electrical work is quoted separately. Please share your location and installation requirements so our team can confirm what applies.” This is a hypothetical writing example, not an Engage AI offer.
Check promotional claims particularly carefully. An archived offer may still be discoverable online. State the applicable dates and eligibility clearly, and remove expired offers from active answer material. Avoid leaving an old price available without a visible explanation of its status.
Assign an owner and a realistic maintenance routine
“Everyone can update it” often becomes “nobody owns it”. Assign one accountable owner for each topic, with a backup where practical. The owner does not need to write every sentence, but should confirm that changes reflect the business's current position.
Use both scheduled reviews and change-triggered reviews. A routine check catches forgotten material, while an immediate review is appropriate when a price, policy, branch, service or campaign changes. Review frequency should reflect how often the information changes and the consequences of an incorrect answer. There is no useful universal interval for every business fact.
Keep a brief change log: what changed, who approved it, when it became effective and which answers were checked. Preserve actual creation and audit timestamps in your systems. An editorial article date or a business policy's effective date serves a different purpose.
Maintain one approved meaning across formats and languages
A website, brochure, WhatsApp reply template and translated FAQ may all express the same rule. Give those versions a common owner and reference so an update reaches each one. A translation should preserve exclusions, amounts and dates, rather than merely sounding natural.
After a meaningful update, test the answer using ordinary customer wording. Include a short question, a question with a mistaken assumption and a branch-specific variation. Read the resulting answer against the approved source. Confirm that it has not dropped an important condition or turned an estimate into a promise.
A source-check checklist for your next review
The source is approved, identifiable and accessible to the responsible team.
The effective period and relevant business scope are clear.
Conflicting and expired versions have been resolved or clearly retired.
The answer preserves the conditions that affect the customer's decision.
Unknown details lead to a realistic clarification or staff-confirmation step.
An owner, review trigger and record of the change are in place.
A realistic customer question has been checked after the update.
Dependable answers begin with a business that can explain what is true, where it applies and who maintains it. Start with one high-impact topic, resolve its source information and test its answer. Repeat that process as your FAQ library grows.
For product context, see how Engage AI describes approved business knowledge.