Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
You getTable 1, table 2 and 3 bullets
Prompt
You are a support operations analyst who audits help centers for self-service gaps.
Right after this prompt I will paste two things: (1) a batch of support tickets (subjects, summaries or full text) and (2) the list of article titles in our help center. Find which ticket reasons have no good article and tell me what to write first.
Rules:
1. Group tickets into contact reasons written in the customer's words, and count tickets per reason. Each ticket goes in exactly one reason.
2. Mark a reason Covered only if an article title clearly answers it, Partial if an article exists but likely misses what customers ask, and Gap if nothing fits.
3. Rate deflection potential High, Medium or Low. High only if a customer could fix it alone with clear steps; Low if an agent must act on the account (refunds, bugs, account changes).
4. Rank articles to write by ticket count times deflection score (High 3, Medium 2, Low 1), not by count alone.
5. Use only the tickets and titles I paste. Do not invent volumes or articles.
Output format:
- Table 1: Contact reason | Tickets | Matched article | Status
- Table 2: Priority | Proposed article title | Reasons covered | Tickets | Deflection | Score | Why
- 3 bullets: quick fixes for Partial articles
End with one line on what this ticket sample cannot show.Example output
Tips and common edits
Why this works
- Covered, Partial and Gap statuses catch weak existing articles, not just missing ones.
- Scoring count times deflection stops you writing articles for issues that always need an agent.
- Writing reasons in customer words gives you article titles that match what people search.
Use when ticket volume is rising or before a help center refresh. Have 30-200 recent tickets and your full article title list ready to paste into ChatGPT, Claude or Gemini.
Common edits
- Add a column for suggested search keywords or synonyms for each new article.
- Ask for a one-paragraph outline of the top-priority article after the tables.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Turn Support Ticket Topics into a Help Center Category Structure and Article List
Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Turn a Resolved Support Ticket Thread into a Help Center Article
Paste a solved ticket thread and get a ready-to-publish help article with customer details removed, verb-first fix steps, and symptoms written the way customers search.
Turn Pasted Customer Questions into a Clear FAQ Page with Short Answers
You get a ready-to-publish FAQ page with duplicate questions merged, answers under 60 words drawn only from your facts, and a list of gaps.