Help center article gap finder
An agent compares recent support questions against your help center and lists topics with no article or an outdated one, with a draft outline for each gap.
The use case
Customers write in about things a help article could have answered, but small teams rarely know which articles are missing or stale. The help center grows by guesswork. A gap-finder agent reads a sample of recent tickets and chat transcripts, groups the questions by topic, and checks each topic against your existing help articles. It reports topics with no matching article, articles that contradict recent answers, and articles customers were linked to but still wrote back about. For each gap it drafts an article outline. A support lead prioritizes the list, writes or approves the final articles, and publishes them.
Example workflow
- A monthly run exports recent tickets and chats plus the list of published help articles with their text.
- The agent redacts personal information and groups customer questions into topics.
- It matches each topic against existing articles and marks it as covered, partially covered, missing, or contradicted.
- Claude ranks gaps by how often they appeared in the sample and drafts an outline for the top gaps.
- The support lead reviews the list, assigns articles to writers, and verifies facts with the relevant team.
- Approved articles are published by a person, and the gap list is saved to compare against next month.
Tools
- Zendesk Guide, Help Scout Docs, or Intercom Articles
- Claude
- Google Sheets
- Notion
- Make
Risks and guardrails
- Draft outlines can contain wrong instructions; have someone who knows the product verify every step before publishing.
- Ticket samples may include personal details; redact before analysis and keep raw exports access-restricted.
- Small samples can misrepresent what matters; treat rankings as directional and add judgment from the team.
- Publishing policy details too early can create commitments; route policy-related articles through the owner.
Related recipe
Support Ticket and Review Triage with Policy-Cited Draft Replies: An agent tags every helpdesk ticket and public review by intent, urgency, and sentiment, routes it, and drafts a reply that cites your help center. People approve refunds and all public replies.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- 中央社新聞 CNA TAIWAN NEWS (official page): ask.cna.com.tw/ask (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Notion MCP server (official page): developers.notion.com/guides/mcp/overview (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)