Support knowledge gap
Find the gaps in your knowledge base from this week's struggle tickets — auto-draft starter articles for each gap.
Eluu — support-knowledge-gap
Shown in preview 
Runtime ~5 min per run
Tokens ~18K per run
Owner a support enablement colleague
Works with
Pick whichever tool your team already uses.
- Messaging Slack
Teams - Support Zendesk
Intercom 
Help Scout 
Front - Docs Notion
Google Docs 
Confluence
What it does
The knowledge base never quite keeps up with what customers are actually asking — and the gaps are hidden in tickets where customers struggled before getting an answer. This recipe pulls those struggle tickets, clusters them, identifies true KB gaps versus stale-article problems, and drafts starter articles for each gap.
How it works
- Pull struggle tickets. Tickets with resolution over 24 hours, 4+ customer messages, or KB-search misses are pulled.
- Gap analysis. Tickets are clustered by topic; each cluster gets matched against existing KB articles; clusters with no KB hit are true gaps; articles last edited 6+ months ago are flagged stale.
- Draft starters. A 200-word starter draft is composed per true gap and saved to the KB-Drafts folder. Gap report posts to #support-enablement.
Setup
- Connect a support tool (Zendesk, Intercom, Help Scout, or Front).
- Connect a docs destination (Notion, Google Docs, or Confluence) for the KB.
- Connect a messaging channel (Slack or Teams).
Variations
- Run product-area-scoped versions (billing, integrations, onboarding).
- Auto-assign drafted articles to subject-matter experts for review.
- Add a stale-article rotation that schedules reviews on a quarterly basis.
