Turn repeat support tickets into knowledge base articles automatically
Weekly, Doe reads all resolved tickets in Freshdesk, identifies recurring questions that don't have knowledge base articles, and drafts the missing articles in Notion. Also flags existing articles that are outdated based on how tickets were actually resolved.
Recurring support questions identified, missing knowledge base articles drafted in Notion, and outdated articles flagged every week from resolved Freshdesk tickets. Doe turns your best agent responses into self-service documentation so customers find answers before they open tickets.
What changes
| Dimension | Before | With Doe |
|---|---|---|
| KB article production | Written when someone has spare time (rarely) | Draft articles generated weekly from actual ticket resolutions |
| Time to identify gaps | Months. Gaps are felt, not measured | Flagged weekly with ticket volume and impact data |
| Ticket deflection | Unmeasured. KB coverage grows slowly or not at all | Quantified per topic with estimated tickets preventable |
| Article freshness | Outdated articles discovered by frustrated customers | Stale articles flagged when agent answers diverge from published content |
How Doe finds knowledge gaps and drafts articles
FreshdeskDoe ingested 214 resolved tickets: questions, agent responses, resolution steps, tags, and customer segments
Doe found 5 recurring topics with 8+ tickets each and no corresponding article: data export formatting, SSO setup for Okta, API rate limits, team permissions, and billing plan changes. 47 tickets this week alone
Notion5 draft articles created with step-by-step instructions, common edge cases from ticket history, and links to related tickets for context
Doe flagged 3 outdated articles: the data export article references a deprecated UI, the integrations article is missing the new Slack connector, and the pricing page links to an old plan structure
Slack5 new articles drafted with Notion links, 3 outdated articles flagged with specific discrepancies, and an estimate that 47 tickets could have been deflected
Your support team is answering the same question for the 50th time
A customer asks "how do I export my data?" An agent writes a thoughtful, detailed response, resolves the ticket, and moves on. Next week, a different customer asks the same thing. The next agent writes a slightly different version of the same answer. And again. And again. Everyone on the team knows a knowledge base article would prevent this, but writing documentation always loses to answering the next ticket in the queue. The backlog never shrinks, and the KB never grows.
The other side of the problem is articles that exist but are wrong. The product shipped a new export flow three months ago, but the KB article still describes the old one. Agents know the article is outdated and work around it, writing the correct steps from scratch every time. Customers who find the article on their own follow the wrong instructions, get confused, and open tickets, creating more work, not less. The documentation that was supposed to reduce volume is actively generating it.
Get started in under 10 minutes
Connect your tools
One-click OAuth for each integration. No API keys, no engineering.
Describe what you need
“Read last week's resolved Freshdesk tickets, find any question that came up 5+ times without a matching KB article, and draft the missing articles in Notion using the best agent response as the starting point.”
It runs on schedule
Every Monday, the gap analysis and draft articles land in your support ops channel.
Support Knowledge Gap Finder FAQ
Yes. The same workflow connects to Zendesk, Intercom, or any ticketing system with an API. Freshdesk is shown here as the example, but Doe reads tickets from whichever platform your support team uses.
Stop doing the work your tools should do for you.
Set it up once. Doe runs it every time.
