What problem does it solve?
Every support organization depends on its knowledge base, and almost every knowledge base is behind. Agents solve a new problem, write a few lines in the ticket and move on; the fix never becomes an article, so the next agent and the next customer start from scratch. Articles that do exist go stale when products, prices and procedures change, and nobody knows which ones, because checking hundreds of articles against reality is nobody's full time job.
This matters more now than it used to. Self service portals, chatbots and AI agents all answer from the same knowledge base, so a gap or an outdated article is repeated at scale. The work AI can take on is the drafting and the detection: turning resolved cases into structured first drafts, finding clusters of questions with no good article, and flagging articles that conflict with newer ones or have not been touched since a change. Publishing stays with a knowledge owner.
How does it work?
- Mine resolved work. When a ticket, case or chat is closed with a new or unusual resolution, the AI reads the case notes, the conversation and the resolution steps.
- Draft in the house format. It writes a first draft in the organization's article template (problem, environment, cause, resolution steps, related articles), without customer data.
- Check for duplicates and conflicts. The draft is compared with existing articles; the AI proposes an update to an existing article instead of a new one where they overlap, and flags contradictions.
- Find the gaps. Questions from search logs, chatbot conversations and tickets that retrieval could not answer well are clustered and ranked by volume, each with a proposed article.
- Flag stale content. Articles are checked against release notes, policy changes and feedback (thumbs down, reopened tickets), and the ones at risk are queued for their owner.
- Review and publish. A knowledge owner edits, approves and publishes; the article then feeds agents, self service and AI assistants alike.
- Audience
- Employee facing
- Autonomy
- Copilot
- Adoption
- Emerging
- Channels
- Internal tools, Agent desktop
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
No public deployment has disclosed a measurable outcome yet.
Value drivers: Employee productivity, Lower cost to serve, Customer experience, Speed and cycle time.
Indicative value
A support organization that publishes or revises 2,000 knowledge articles a year
USD 40,500 to USD 210,000
Authoring time value released per year
How this is calculated
Formula: articles * hoursPerArticle * timeSavedShare * authorCost. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Articles created or substantially revised per year articles, articles per year | 2,000 | 2,000 | The reference organization. |
| Author time per article without AI hoursPerArticle, hours per article | 1.5 | 3 | Editorial assumption covering research, writing and formatting. Replace with your own. |
| Share of author time saved by a reviewed AI draft timeSavedShare, fraction of author time | 0.3 | 0.5 | Editorial assumption. No public benchmark on this page quantifies it yet; review and testing time is kept with the author. |
| Fully loaded cost of a knowledge author or senior agent authorCost, USD per hour | 45 | 70 | Editorial assumption, replace with your own. |
What it leaves out: Counts only authoring time. It leaves out the usually larger effect of a more complete, current knowledge base on self service containment, first contact resolution and new agent ramp up, and the cost of the platform and of the reviewers' time.
Who already uses it?
4 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
Internal Revenue Service
United States · Government and public sector · 2025
The IRS User and Network Services IT service desk runs a generative AI pilot, described as a limited production challenge, that summarizes incident case notes for warm handoffs, writes resolution notes from the actions taken, and generates complete knowledge base articles from incident and case records. The agency expects the effort to feed its existing knowledge review and publication processes, save time on handoffs, shorten the mean time to restore and support more self service, but publishes no results.
No outcome disclosed.
U.S. National Science Foundation
United States · Government and public sector · 2025
NSF's Office of Information and Resource Management uses ServiceNow's generative AI, Now Assist, on a FedRAMP High platform to generate content for its service operation, including responses, work notes and knowledge base articles, alongside recommendations and chatbots. It shows the common pattern of knowledge article drafting switched on inside an existing service management platform rather than built separately. No outcome figures are published.
No outcome disclosed.
Centers for Disease Control and Prevention
United States · Government and public sector · 2024
CDC's National Center for Immunization and Respiratory Diseases runs SmartFind, an internal knowledge bot with a SharePoint component that helps program staff manage partner emails and lets mailbox managers use a shared knowledge base. The agency lists partner mailbox email management and knowledge base maintenance as the purpose. The bot matches free text questions to agency cleared answers and flags complex or unanswerable queries for manual review. Earlier public facing versions gave agency cleared answers to public and partner questions during the COVID-19 pandemic. No outcome figures are published.
No outcome disclosed.
Rivian
United States · Automotive · 2025
Rivian uses NotebookLM to centralize answers to frequently asked questions from verified sources and share them as a knowledge base with interactive chat. Google Cloud reports that it reduced repetitive inquiries and saved employees time, without a figure. It is a simple example of turning scattered answers into shared, grounded knowledge.
No outcome disclosed.
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Closed tickets or cases with usable resolution notes
- The current knowledge base with owners, review dates and article templates
- Search, chatbot and ticket logs that show unanswered or poorly answered questions
- Release notes and policy change records to detect stale articles
Systems to integrate
- IT or customer service management platform (for example ServiceNow, Zendesk, Salesforce)
- Knowledge base or content management system with an approval workflow
- Search and chatbot analytics
- Product release and policy change feeds
Complexity: Low
Drafting from a closed case is straightforward. The effort is in a clear article template, clean ownership of content, removing customer data from drafts and getting authors to review instead of rewrite.
- 1
Fix the template and the owners first
Agree one article template per content type and assign every article and category to an owner with a review date. Drafts without an owner never get published.
- 2
Start with case to article drafting
Trigger a draft when an agent marks a resolution as reusable. Measure how much the reviewer changes, and tune the prompt until most drafts need edits rather than rewrites.
- 3
Strip customer data from drafts
Mask names, account numbers and environment details that identify a customer before drafting, and have the reviewer confirm nothing personal remains.
- 4
Add gap detection
Cluster the questions that search and chatbots failed to answer, rank them by volume and propose articles for the top clusters each week.
- 5
Add stale content checks
Compare articles with release notes and policy changes, and use negative feedback and reopened tickets as signals. Queue at risk articles for their owner rather than editing them silently.
- 6
Close the loop with the assistants
Track whether new articles actually reduce repeat questions and improve answers from self service and AI agents, and retire articles that nobody uses.
Guardrails
- No article is published without approval by a named knowledge owner
- Customer and personal data removed from drafts before review
- Drafts cite the cases and sources they were derived from, for the reviewer to check
- Updates to existing articles are proposed as changes with a visible difference, never applied silently
- Articles on regulated topics (fees, legal rights, safety) go through the existing compliance review
KPIs to instrument
- Share of AI drafts published with minor edits versus rewritten or rejected
- Author time per published article, before and after
- Time from first occurrence of a new issue to a published article
- Unanswered question clusters closed per month
- Self service and first contact resolution on topics with new or refreshed articles
Human in the loop
Knowledge owners approve every new article and every change, and remain accountable for the content. Agents flag which resolutions are worth an article; reviewers sample published AI drafts monthly for accuracy against the source cases.
Common failure modes
- Publishing the fix for one customer
- A draft generalizes a workaround that only applied to one environment. Require the reviewer to confirm scope and prerequisites.
- Article sprawl
- Every case becomes a new article and search gets worse. Prefer updating existing articles and merge duplicates.
- Customer data in the knowledge base
- Details from the source case survive into a published article. Mask before drafting and check before approval.
- Stale content amplified by AI
- Chatbots answer confidently from an outdated article. Tie review dates and stale content checks to the release process.
What are the risks and rules?
EU AI Act
Minimal risk
Drafting internal or public help content that a person reviews and publishes is not a prohibited practice under Article 5 and is not listed in Annex III, so it is minimal risk. The articles are not a direct AI interaction, and the Article 50(4) disclosure for AI generated text published to inform the public does not apply where a person reviews the text and holds editorial responsibility. The Article 50 transparency duties do apply to chatbots that later answer customers from the articles.
Rules that apply
Guidance
- Article 50, transparency obligations for providers and deployers of certain AI systems (European Union, Europe). Paragraph 4 requires disclosure of AI generated text published to inform the public on matters of public interest, unless it has undergone human review or editorial control and a person holds editorial responsibility.
Controls to put in place
- Content ownership and review dates recorded for every article
- Approval workflow that records who approved each AI drafted article
- Personal data masking on case data used for drafting
- Periodic audit of a sample of published AI drafts against their source cases
Frequently asked questions
- Can AI write knowledge base articles on its own?
- It can produce complete first drafts from resolved cases, but publishing should stay with a knowledge owner. The IRS IT service desk runs a limited production pilot that generates knowledge base articles from incident and case records, and expects it to feed its existing knowledge review and publication processes.
- Where do the biggest gains come from?
- Less from faster writing than from a knowledge base that keeps up: fixes captured the day they are found, gaps closed by volume, stale articles flagged. That quality then flows into every self service channel and AI agent that answers from it.
- Is this a separate tool or part of the service platform?
- Often it is a feature switched on in the service platform. The U.S. National Science Foundation uses ServiceNow Now Assist to generate responses, work notes and knowledge base articles. A separate build makes sense when knowledge lives in several systems or feeds several assistants.
How to cite this page
Blits.ai AI Use Case Library, "AI for support knowledge article generation and maintenance", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/support-knowledge-article-generation. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 27 September 2026: First published