Consolidate overlapping help docs and FAQs into one knowledge base
An inventory, conflict list, taxonomy, article template, and merge plan to turn scattered help content into one reliable source.
The prompt
Help me consolidate scattered help articles, FAQs, and training materials into one clear knowledge base.
Materials: [PASTE or summarize the documents - title, audience, owner, and last-updated date for each]
Audiences: [internal staff / customers / both]
Products or platforms covered: [LIST]
Where it will live: [help center, intranet, wiki tool]
Problems today: [e.g. "contradictory answers", "a separate copy for each platform", "nobody knows which version is current"]
Steps:
1. Inventory: list every item with its topic, audience, and status (current / outdated / unknown).
2. Overlaps and conflicts: group items that answer the same question. Where they disagree, show both versions and mark [DECIDE]; don't pick an answer unless the sources make it clear.
3. Gaps: common questions nothing answers yet, based on the materials and products listed.
4. Structure: a taxonomy (category > subcategory > article) that separates internal-only from customer-facing content, writes shared content once, and shows platform differences as clearly labeled sections.
5. Article template: title phrased as the reader's question, short answer, steps, platform notes, related articles, owner, review date.
6. Merge plan: which items to merge, rewrite, retire, or redirect, in priority order (most-viewed or most-contradictory first).
7. Governance: owners, review cadence, and how new content gets added so duplication doesn't creep back.
Return a mapping table: Old item | Action (keep / merge / rewrite / retire) | New article | Notes. Then the taxonomy and the template.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- internal staff / customers / both
- LIST
- help center, intranet, wiki tool
- DECIDE
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a compliant collections call script for overdue accountsA debt collection call script with required disclosures, hardship options, and phrases to avoid under collection rules.
- Handle an overbooking and relocate a guest to another hotelA walk procedure, front desk script, and follow-up for when the hotel is oversold and a guest must be relocated.
- Write a weekly live chat support reportTurns chat data into a weekly report on volume, response times, satisfaction, top questions, and actions for the next week.
- Cut call handle time without hurting customer experienceDiagnoses what drives long calls and gives script, training, and tooling fixes that shorten them without lowering quality.