ThinkWithPrompt by SynotticThinkWithPrompt

Audit my help center for outdated and missing articles

A prioritized review of your knowledge base that finds stale, duplicate, and missing content using search and ticket data.

Customer SupportRTFStandardWritingAnalyzeFill-in Template

The prompt

Help me audit our help center. List of articles: [PASTE titles, URLs, last-updated dates, views, and helpfulness ratings if available] Top ticket categories: [WHAT CUSTOMERS CONTACT US ABOUT, with volumes] Top help center searches, especially with no results: [SEARCH TERMS] Recent product changes: [FEATURES, UI, PRICING, POLICIES THAT CHANGED] Who can update content and how much time we have: [CAPACITY] Do this: 1. Flag articles that are likely outdated: old update dates that mention changed features, pricing, or screens. 2. Find duplicates and overlapping articles to merge. 3. Find gaps: top ticket drivers and searches with no matching article, or where the article exists but tickets still come in (meaning it may be unclear or hard to find). 4. Flag low performers: high views with poor helpfulness ratings. 5. Check structure: are categories organized around customer tasks, and are titles phrased the way customers search? Return a table: Article or gap | Issue | Evidence | Action (update / merge / rewrite / create / retire) | Priority | Effort. Prioritize by ticket volume and views. Then give a 4-week plan that fits my capacity, and a simple rule for keeping articles current after this (e.g. owner and review date per article). Don't guess article content you can't see; list what I should check.

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

  • WHAT CUSTOMERS CONTACT US ABOUT, with volumes
  • SEARCH TERMS
  • FEATURES, UI, PRICING, POLICIES THAT CHANGED
  • CAPACITY

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

Find more prompts like this