Reuse FAQs Across Help Center Articles - Article
Summary
Recurring questions often deserve a concise answer without interrupting the main procedure. Separate FAQ records let you maintain that answer once and present it beneath every article where the same explanation is useful.
A shared FAQ is still part of a reader journey. Its answer must fit each linked article, and the Help Center AI assistant can use it only through an article available to the reader.
Use this article to:
- Create and attach reusable FAQs
- Decide when one shared answer is appropriate
- Maintain associations and verify reader and AI access
Give the main article and the FAQ different jobs
Keep the full process, important conditions and decision context in the article. Use a FAQ for a recognizable follow-up question or exception, such as “Can I book for someone else?” or “Why is my certificate not available yet?”. The answer should be direct but include the condition and next action needed to prevent a misleading response.
A booking article and a team-coordinator article can share the same answer when the rule genuinely applies to both. If booking rights or actions differ by role, create distinct questions or explain the differences clearly. Reuse should reduce contradictory maintenance, not flatten meaningful differences.
Create a FAQ record
Sign in as a Help Center administrator and open Content management → FAQ. Search the existing questions before creating another answer. The list loads records in batches, so use search rather than assuming the visible rows are the full collection.
- Select Create. Enter a complete Question in the language readers use.
- Write the Answer with the relevant rich-text tools. Include a link only when it leads to a current, appropriate destination.
- Use Articles to select each article where the answer should appear. Verify every association serves the same rule and intended use.
- Select Create, reopen the saved FAQ and check its complete question, answer and article associations.
The FAQ appears below each linked article as an expandable question-and-answer panel. You can also link or unlink an existing FAQ through the article editor’s FAQ questions selection. Save the containing article after changing those selections.
Maintain shared answers as shared content
Before editing a FAQ, inspect all linked articles. A change to the shared answer affects each of them. For example, replacing a common certificate explanation with a rule that applies only to one program could silently make the answer wrong beneath other articles.
| Situation | Maintenance choice |
|---|---|
| The same rule changes for every linked article | Update the shared FAQ once, then check it beneath representative linked articles |
| One process has a different exception | Create or use a distinct FAQ for that process rather than changing the shared answer globally |
| The article already explains the main procedure | Use a concise FAQ for a recurring follow-up; avoid copying the full procedure into the answer |
| A question has no article association | Attach it to the appropriate maintained article if it is useful; an unattached record is not a reader source for the assistant |
| A draft review copy and an original share a FAQ | Check their actual associations before calling the FAQ duplicated or unused |
Keep questions distinct and complete. Two records with similar titles may contain different conditions; compare their full answers and associations before merging them. Retain useful knowledge in the canonical article or FAQ before removing an obsolete record.
Understand FAQ access and AI retrieval
A FAQ does not have an independent article-like audience selection. The Help Center AI assistant uses FAQ information only when it is attached to an article available to the reader. An unattached FAQ is not used as a source. If the association is removed, the article becomes unavailable or the content is unpublished, the reader no longer receives that FAQ through the unavailable article.
This makes the article relationship an important part of information governance. Do not put confidential detail into a FAQ attached to a public article. Likewise, saving an Administrator-only draft with FAQs is an editorial state, not proof that ordinary users can retrieve those answers.
For the wider source model and content-writing guidance, use Prepare Reliable Knowledge for the Help Center AI Assistant.
Verify a FAQ change
| Scenario or check | Expected result or evidence |
|---|---|
| The saved FAQ is reopened | The question and full answer are correct and the intended articles are selected |
| A permitted reader opens a linked article | The FAQ appears below the body and expands to the intended answer |
| A shared answer is changed | Each affected article still presents an accurate answer for its process |
| The assistant is asked the recurring question | Where enabled and eligible, the answer uses the relevant source and links to the associated article |
| A record appears unused | Its actual article associations are checked before cleanup |
Troubleshooting
| Problem | What to check |
|---|---|
| A FAQ does not appear beneath an article | Check both the FAQ’s Articles associations and the article’s FAQ questions selection, then verify the saved result |
| The assistant does not use a FAQ | Check that it is attached to a published article available to the reader and that the answer addresses the question clearly |
| A shared answer is wrong for one article | Review the rule across all associations; separate the exceptional case instead of weakening the common answer |
| Two articles with the same title appear in associations | Check their IDs and draft states; an original and a review copy can share a title without representing two public destinations |
FAQ
-
Can one FAQ appear beneath several Help Center articles?
Yes. Associate it with every article where the same answer is correct. Review all associations before editing a shared answer because the change affects each linked article.
-
Will the Help Center AI assistant use a FAQ with no article attached?
No. A FAQ must be attached to an article available to the reader. Check the article’s publication state and audience as well as the association.
-
Should FAQs repeat the complete procedure from the article?
Usually keep the complete procedure in its authoritative article and use FAQs for concise follow-up questions or exceptions. Include enough conditions and a relevant next action for the answer to stand on its own.