# Best Practices for Knowledge Base Content

**T**he purpose of this section is to provide you with best practices and recommendations to author & maintain Knowledge Content in Knowledge Bases and Document Repositories that can be leveraged by Support Agents and Knowledge Analysis Solutions.

### **General Knowledge Base Guidelines** <a href="#j1y4thr6huk" id="j1y4thr6huk"></a>

1. Use Knowledge Bases from the System of Record as preferred option (such as a ServiceNow knowledge base or JIRA Confluence)
2. Web/HTML & Wiki, Confluence or SharePoint like knowledge repositories should be next preferred option
3. If knowledge bases and knowledge repositories are not available, then use file formats such as HTML, PDF

Note: There are known challenges with PDF format parsing that includes limitations on content extraction from PDF on images, multimedia, tables etc.

1. Microsoft Office Documents such as Word, PowerPoint and Excel are not preferred for Help Desk & Customer Support Solutions

#### **Knowledge Content Guidelines** <a href="#pvkzuvrg0l42" id="pvkzuvrg0l42"></a>

* [Leverage KCS v6 methodology](https://library.serviceinnovation.org/KCS/KCS_v6/KCS_v6_Practices_Guide) for techniques on content creation from title, section, sub-section, paragraph of knowledge document
* Use Standard KB Templates that are available in Knowledge Bases such as FAQ, How-to, Issue-Resolution available in Service
* Ensure all Meta-data fields related to Knowledge Articles are captured. This includes – Category, Article Type etc.
* Ensure Knowledge Article Titles are appropriately capturing Symptoms and not just Solutions. This helps in improving search accuracy in finding relevant content and articles.
* Ensure Article content is simple and consistent:
  * Use plain English: Avoid big words. Use less syllables for a higher impact.
  * Define Acronyms: Acronyms are not intuitive or easy to follow. The first time you use an acronym in an article, spell it out and follow it with the acronym in parentheses. *(E.g., Virtual Private Network (VPN))*. The next time you use it in the article just use the acronym.
  * Avoid Jargon: Not everyone understands the jargon used. Keep content simple.
  * Use Active Verbs: In your sentences use the active voice not passive. *Example:*
    * \- passiv&#x65;*: The files will be deleted by clicking on Delete.*
    * *-* activ&#x65;*: Click Delete to delete files.*

#### **Knowledge Content Formatting** <a href="#id-7a8do6vsewrh" id="id-7a8do6vsewrh"></a>

* Use Single Column Layout for formatting documents
* Use headings and subheadings to distinguish sections (use H1, H2, H3 tags) with consistent branding across pages
* Ensure images and video content can be rendered in most browsers
* Avoid using nested lists within documents

*Example: Zendesk Knowledge Article Section and Subsection formatting with Aisera’s Conversational AI result below.*

<figure><img src="https://aisera.gitbook.io/aisera-product-documentation/05T7Y6PhrzglAXbQzVA8/~gitbook/image?url=https%3A%2F%2F3281977978-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FvBFXjH9S1CAy9f5hzg5Q%252Fuploads%252Fyi4iItwOqNs1mJjrCeX4%252Fkb_demo.png%3Falt%3Dmedia%26token%3D6d0ffb7d-f1c6-4dd6-b6d4-34040bf4a6c6&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=9057dca8&#x26;sv=2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.aisera.com/workflow-best-practices/best-practices-for-knowledge-base-content.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.