Freshservice knowledge base: A complete guide for IT teams in 2026

A well-organized knowledge base is the backbone of efficient IT support. When employees can find answers on their own, ticket volumes drop and agents focus on complex issues. Freshservice offers a robust knowledge base solution (formerly called "Solutions") that integrates directly with its ITSM platform. Let's break down what it offers and how to make the most of it.

For teams looking to enhance their self-service capabilities even further, AI teammates like eesel AI can connect directly to your Freshservice knowledge base to answer employee questions instantly.

What is the Freshservice knowledge base?

The Freshservice knowledge base is a self-service portal where IT teams document solutions, policies, and FAQs. It serves as the first line of support, allowing employees to resolve common issues without submitting tickets.

Think of it as a specialized library for your IT operations. Instead of agents answering "How do I reset my password?" fifty times a week, employees find the answer themselves in seconds.

The knowledge base sits at the heart of Freshservice's ITSM approach. When someone submits a ticket, the system can suggest relevant articles. When agents resolve issues, they can convert solutions into new articles. This creates a continuous loop of knowledge capture and reuse.

Key benefits include:

• Ticket deflection Employees solve issues independently, reducing support volume
• 24/7 availability Answers are accessible outside business hours
• Consistent information Everyone receives the same accurate guidance
• Agent productivity Teams focus on complex problems instead of repetitive queries

For IT teams exploring AI for ITSM, the knowledge base becomes even more powerful when paired with AI teammates that can read, understand, and act on your documentation.

Key features of Freshservice knowledge base

AI-powered content creation with Freddy AI

Freshservice's Freddy AI brings artificial intelligence directly into knowledge management. Instead of starting articles from scratch, agents can use AI to draft content from simple prompts. The system can also analyze resolved tickets and automatically suggest new articles based on common solutions.

Freddy AI reviews content tone and quality before publishing, helping maintain consistency across your knowledge base. It also powers smart response suggestions, pulling relevant information from existing articles to help agents reply faster.

The AI agent capability extends this further by handling employee questions directly in Slack, Microsoft Teams, or your service portal in over 40 languages. It uses your knowledge base content to provide instant answers without human intervention.

Hierarchical organization structure

Freshservice uses a three-level hierarchy to organize content: Categories contain Folders, which contain Articles. This structure scales with your needs. Free and Growth plans support the basic three-level structure, while Enterprise plans offer up to six levels with nested sub-folders.

This flexibility matters for complex organizations. You might structure content like:

• IT Support (Category)
  • Account Access (Folder)
    • Password resets (Article)
    • MFA setup (Article)
  • Network & VPN (Folder)
    • VPN connection issues (Article)
    • Wi-Fi troubleshooting (Article)

Multi-product and multi-brand support lets you maintain separate knowledge bases for different departments or subsidiaries while managing everything from a single Freshservice instance.

Article templates and versioning

Creating consistent content is easier with templates. Freshservice supports up to 30 article templates per account, covering common formats like How-to guides, User guides, and FAQs. You can mark a template as default so it loads automatically when agents create new articles.

Version control tracks how content evolves over time. If an update doesn't work out, you can restore previous versions. Approval workflows ensure content gets reviewed before going live, which is essential for maintaining accuracy in technical documentation.

Access control and visibility

Not all content should be visible to everyone. Freshservice offers granular visibility controls:

• All users Customers, agents, and bots can access
• All agents Internal documentation hidden from customers
• Logged-in users Requires portal authentication
• Specific companies Restrict to selected organizations
• Contact segments Target by geography, plan type, or custom criteria
• Bot-only For automated system access

Portal-specific visibility lets you show different categories on different support portals, useful if you maintain separate portals for different products or regions.

Setting up your Freshservice knowledge base

Step 1: Create categories

Start by navigating to Solutions > New Article > New Category. Give your category a clear name and description that reflects the type of content it will contain. Set the portal visibility based on who needs access.

Plan your category structure around IT services rather than organizational hierarchy. Categories like "Account Access," "Software Support," and "Hardware Issues" work better than department names because employees think in terms of problems, not org charts.

Step 2: Organize with folders

Within each category, create folders to group related articles. When creating a folder, you'll select its hierarchy level and parent folder if applicable. Configure visibility permissions per folder to control who sees what.

Consider how employees search for help. A folder structure that mirrors common ticket categories will make content easier to find. If 30% of your tickets are about password issues, that deserves prominent folder placement.

Step 3: Create and publish articles

Use the rich text editor for most content, or switch to HTML if you need precise formatting control. Add relevant tags to improve searchability. Tags should include common search terms employees might use.

Set the article status to "Draft" while writing, then change to "Published" when ready. You can also schedule articles to publish later or set expiration dates for time-sensitive content.

Best practices for organizing your knowledge base

Structure content around your most common IT issues. Password resets, VPN access, and software requests typically top the list. Start there and expand based on ticket analytics.

Use clear, searchable article titles. "How to reset your password" works better than "Password reset procedure" because it matches how employees actually phrase their searches.

Include keywords and tags for discoverability. Think about the different ways someone might describe the same problem. A VPN article might need tags like "remote access," "work from home," and "network connection."

Run regular content audits using the Insights tab. Articles with low usefulness scores or high downvote rates need attention. Update outdated screenshots and procedures quarterly.

Understand the difference between workarounds and permanent solutions. Document both, but clearly label temporary fixes so agents know when a better solution exists.

For multilingual teams, plan your translation strategy early. Freshservice supports multiple languages, but maintaining synchronized content across languages requires discipline.

Analytics and continuous improvement

Freshservice provides knowledge base reporting to track performance metrics. The usefulness score combines views, helpful votes, and downvotes to identify which articles serve employees well and which need work.

The Insights tab lists articles requiring improvement, sorted by usefulness score. This gives you a prioritized backlog of content to update.

Track which articles get attached to tickets. High attachment rates indicate content that agents find valuable. Low attachment rates might mean agents don't know the article exists or it doesn't address the issue effectively.

Freddy AI can identify knowledge gaps by analyzing ticket trends. If employees keep asking about a topic you haven't documented, the system flags it for new article creation.

Integrating your Freshservice knowledge base with eesel AI

Here's where your knowledge base investment pays off exponentially. AI teammates like eesel AI can connect directly to your Freshservice knowledge base and start answering employee questions immediately.

Instead of employees browsing articles manually, they simply ask questions in natural language. The AI reads your knowledge base, understands the context, and provides accurate answers in seconds.

Benefits of this integration include:

• Faster resolution Employees get answers instantly instead of searching through articles
• Consistent responses Every employee receives the same accurate information
• 24/7 availability AI handles questions outside business hours
• Automatic learning When you update your knowledge base, the AI learns immediately

We integrate with Freshservice to pull in your existing knowledge base content, past tickets, and help center articles. There's no manual training required. Connect your account and we start learning your business within minutes.

Our AI Agent can handle frontline support directly in Freshservice, using your knowledge base to resolve tickets autonomously. Start with drafting replies for review, then expand to full automation as confidence grows.

Getting the most from your Freshservice knowledge base

Start with your highest-volume ticket topics. If password resets generate 20% of your tickets, that's your first article. Quick wins build momentum.

Encourage agent contributions by making article creation part of the ticket resolution workflow. When an agent solves a novel problem, prompt them to document it.

Establish regular review cycles. Assign article owners who check their content monthly for accuracy. Outdated documentation frustrates employees and undermines trust.

Promote your self-service portal actively. Include links in email signatures, onboarding materials, and Slack channels. Employees won't use what they don't know exists.

Consider AI enhancement when you're ready to scale. A well-organized knowledge base is the foundation. Adding AI on top transforms it from a reference library into an active support channel.