An FAQ makes the answer directly available.
A good FAQ gives a visitor an answer without requiring a conversation. Group questions around actual needs, link to the complete policy or explanation, and keep any dates and conditions next to the statement they qualify.
It is especially useful when wording must be easy to review and share. Someone should still own each answer: a static page can become stale just as easily as a saved chatbot response.
Conversation helps with navigation and context.
A visitor may not know which FAQ category or page contains the answer. A website assistant can accept a natural-language question, retrieve relevant information, and provide a concise response connected to the source.
It can also record an unanswered question or collect contact details for follow-up when configured to do so. Those are useful additions around the content, but they do not establish facts that the business has never published or approved.
| Need | FAQ or source page | Website assistant |
|---|---|---|
| Read a complete policy | Provides stable, reviewable wording and conditions. | Can help locate or explain supported details, with source review. |
| Ask using different wording | Depends on navigation and the page’s wording. | Can retrieve relevant material for a natural-language question. |
| Share a link with someone | Directly links to the published information. | Should preserve a route back to the underlying source where available. |
| Ask an unpublished question | May provide the established contact route. | Can acknowledge the gap and record a follow-up need. |
| Maintain the facts | Requires a content owner and updates. | Requires the same source discipline plus conversation review. |
Build one maintained source of truth.
For important public information, make the website useful first. Let the assistant retrieve that content rather than turning chat into the only way someone can learn a basic service condition.
Use saved answers where explicitly approved wording is useful, and record when those answers need review. Avoid maintaining a conflicting policy in the FAQ, a second version in a saved answer, and a third version in a confirmed fact.
Example: returns conditions
Publish the complete conditions on a source page, link to it from the FAQ, and test the assistant against questions about the relevant conditions. A request for an exception should go to the business’s actual review process.
Use chat questions to improve the page.
Review recurring unanswered questions and confusing phrasing. Decide whether the website should explain the issue more directly, whether navigation makes the page hard to find, or whether the request is genuinely case-specific.
After improving the source, refresh the indexed content and retest the original question. The same change can benefit someone reading the website and someone asking the assistant.
Test both routes with the same visitor task.
Pick a task such as finding the service area or understanding the first step of an enquiry. Try it using the website navigation and then through the assistant. Check the accuracy, conditions, clarity, and route to more detail.
Keep an ordinary contact route available. Some visitors prefer reading or contacting the team directly, and some questions should never require a generated response.