How to Build a Freshdesk Knowledge Base (2026): Step by Step

Everything below was verified against Freshworks' own documentation in June 2026. Plan names and gating are accurate as of writing, but Freshworks revises packaging periodically — confirm current details on freshworks.com before you rely on them. New to the product entirely? Start with what is Freshdesk.

Before you start: a 5-minute terminology check

Inside Freshdesk, the knowledge base lives under a tab called Solutions. "Knowledge base," "Solutions," and "Help Center articles" all describe the same content store — Freshworks uses Solutions for the agent-side authoring area and Help Center (or portal) for the customer-facing site that renders those articles. Don't let the naming trip you up; you author in Solutions, customers read in the Help Center.

The structure is a three-tier hierarchy: Categories (broad topic) hold Folders (sub-sections), which hold Articles (the actual content). A customer reads top-down: Category → Folder → Article. That's the whole mental model. Now let's build it.

Step 1: Plan your taxonomy from real ticket data

Don't design your structure around your org chart or product spec — design it around the questions customers actually ask. Open your Freshdesk ticket reports (or your inbox) and pull your top 10–15 ticket reasons. Group them into a small handful of broad themes; those become your categories.

A simple e-commerce example:

Two rules to save yourself pain later:

• Shallow beats deep. Freshdesk lets you nest sub-folders up to five levels via its flexible hierarchy (Freshdesk docs), but most teams should stay at two or three. Deep nesting is where help centers go to die.
• Name folders the way customers phrase the problem, not in internal jargon. "Tracking & delivery" beats "Fulfilment status taxonomy."

Sketch this on paper or a spreadsheet first. Restructuring later is a chore; ten minutes of planning now is worth it.

Step 2: Enable and brand your Help Center (portal)

The Help Center is the public website your articles render into. A self-service portal with a knowledge base is included on every Freshdesk plan, including the Free program (Freshdesk pricing) — what scales with tier is customization depth, not whether a KB exists at all.

To set up or edit the portal, go to Admin → Channels → Portals → new portal and click Start Setup (Freshdesk docs). Toggle the portal on to make it visible to agents and customers, then brand it:

• Portal Settings tab — set the portal name and URL, add portal languages, and upload your logo (Freshworks recommends ~60×60, 1:1 aspect ratio) and favicon (~16×16) (Freshdesk docs).
• Appearance tab — pick a theme and set colors and fonts with no code: primary color (headers, buttons, nav), body colors and link/hover states, and header/footer colors (Freshdesk docs).
• For deeper control, Freshdesk offers an advanced code editor and lets you import and manage up to 10 custom themes per portal — useful when you want pixel-level control of how articles, buttons, and filters look (Freshdesk docs).

You don't have to perfect this now. Get your logo and brand color in, then come back once you have articles to look at.

Step 3: Create your categories

In the agent view, open Solutions. Click New Article → New Category, give it a clear name and a short description, and set its visibility by choosing the relevant portal (Freshdesk docs). Repeat for the handful of categories you mapped in Step 1.

Keep descriptions human and benefit-led — "Track orders, manage delivery, and cancel" reads better on the portal than "Order management."

Step 4: Create folders and set visibility

Inside a category, click New Article → New Folder. Enter a name and description, and select the hierarchy (this field is mandatory) — you can place a folder directly under a category or nest it inside another folder to build deeper hierarchies (Freshdesk docs).

This is where one of the most useful — and most overlooked — settings lives: folder visibility. A folder can be visible to:

• Everyone — public, indexable, shown in the Help Center.
• Logged-in users only — gated behind a customer login.
• Agents only — an internal-only knowledge base your customers never see.

That last option is the trick that lets one Freshdesk account hold both your public help center and your private internal SOPs, escalation playbooks, and known-issue notes — separated purely by folder visibility. Set this deliberately on every folder as you create it.

Step 5: Write your highest-impact articles first

Resist writing an exhaustive manual. Start with the ~20 articles that would deflect the most tickets — your real top ticket reasons from Step 1. On the Solutions page, click New Article, add a title and body in the rich-text (or HTML) editor, and you're writing (Freshdesk docs).

A reusable article template that works:

1. Title = the customer's question. "Why is my order stuck on processing?" beats "Order status definitions." People search in their own words; match them.
2. One-line summary up top so a skimmer gets the answer in five seconds.
3. Numbered steps for anything procedural — short, imperative, one action per step.
4. A screenshot or two at the moments people get stuck.
5. One job per article. A focused article ranks better, answers cleaner, and — importantly — is far easier for any AI to use accurately.
6. A "still need help?" line at the end pointing to the contact/ticket form.

Write plainly. The best KB article is the one a stressed customer understands on the first read.

Step 6: Add SEO fields to each article

Because the Help Center is a public website, its articles can rank in Google — and Freshdesk gives you the levers. Each article has dedicated SEO fields: an SEO/meta title, a meta description, and keywords/tags (Freshdesk docs). Freshworks' own guidance: keep the title around 50–60 characters and the description around 150–160, both keyword-relevant and readable.

Practical wins: fill in the meta description on every public article (don't leave it to auto-generate), put the customer's actual phrasing in the title, and keep URLs and headings clean. A well-optimized help center quietly becomes a top-of-funnel traffic source, not just a deflection tool.

Step 7: Publish — and know your plan's workflow

Articles move through a lifecycle: Draft → (In Review → Approved) → Published. Here's the part that confuses people, stated precisely:

• The In Review and Approved statuses only appear when the formal approval workflow is switched on, which is an Enterprise-only feature.
• On all lower plans, the lifecycle is simply Draft → Published — there's no software-enforced review gate, so any agent with permission can publish directly (Freshdesk docs).

So if you're not on Enterprise, run your review as a manual checklist before hitting Publish: title in customer language, summary present, steps tested, screenshots current, SEO fields filled, visibility correct. When it's ready, set the article to Published and it goes live on the Help Center.

A few list-management conveniences in the Solutions area are themselves plan-gated: manual reordering works from the Free program, automatic reordering from Growth, and filters and bulk actions from the Pro plan (Freshdesk docs).

Step 8: Go multilingual (Pro and up, optional)

If you serve customers in more than one language, Freshdesk's multilingual knowledge base lets you publish the same article in multiple languages on one portal, with the Help Center auto-detecting a visitor's preferred language by login or browser setting. This is available from the Pro plan onward (Freshdesk docs). Translations are managed per article, and each translated version carries its own status — so a German draft can sit unpublished while the English original is live.

Running several brands or products? Multi-product knowledge bases (each with its own categories, folders, and articles in one Freshdesk account) also kick in from the Pro tier (Freshdesk docs). Skip this step entirely if you're single-language and single-brand.

Step 9: Surface articles where people actually are

A KB nobody finds deflects nothing. Two places to wire it in:

• The Help Center search and widget — make sure the support widget/feedback widget on your site or app surfaces relevant articles before a customer reaches the contact form. The whole point is to answer before a ticket is opened.
• Inside tickets, for agents — from the reply editor, an agent can type /s to insert a solution article (as full text or a link) and /c to drop in a canned response (Freshdesk docs). Freshworks' Freddy AI can also suggest relevant articles and canned responses based on the ticket's content. This is the underrated payoff of a good KB: it makes every human reply faster and more consistent, even on tickets that do reach a person.

Step 10: Measure, then maintain and prune

Freshdesk closes the loop with built-in measurement so you're not guessing:

• Article feedback — readers mark an article helpful or not, and Freshdesk surfaces "not helpful" feedback (it can even raise it as a ticket via the Article Feedback view) so weak content gets fixed.
• KB analytics — reporting on views, feedback, and ratings shows your most-read articles, your worst performers, and the searches that returned nothing.

Build a monthly habit: read the "not helpful" feedback and fix those articles, write new articles for the zero-result searches, and prune or merge anything stale or duplicated. Outdated screenshots and dead steps erode trust fast. A knowledge base is a living asset, not a one-time setup — the teams that win treat their search-and-feedback data as a free content roadmap.

Your starter checklist

Copy this and work top to bottom:

• [ ] Pull top 10–15 ticket reasons; group into 4–6 categories
• [ ] Sketch the category → folder taxonomy (shallow, customer-worded)
• [ ] Enable the Help Center portal (Admin → Channels → Portals → Start Setup)
• [ ] Add logo, favicon, brand colors and fonts
• [ ] Create categories (Solutions → New Article → New Category)
• [ ] Create folders and set visibility (everyone / logged-in / agents-only) on each
• [ ] Write your top ~20 deflection articles using the template
• [ ] Fill SEO title + meta description on every public article
• [ ] Review (Enterprise workflow or manual checklist), then Publish
• [ ] Add multilingual / multi-product versions if on Pro+
• [ ] Surface articles in the widget; brief agents on /s and /c
• [ ] Set a monthly feedback-and-analytics review on the calendar

What real users say (and where it bites)

Worth a reality check before you invest a week in it. Across the two largest review platforms, Freshdesk lands solidly above average — G2 4.4/5 from roughly 3,700 reviews (G2) and Capterra 4.5/5 from ~3,400+ reviews (Capterra), where self-service ranks among the most-used features. Narrowed to the KB specifically, the sentiment is consistent: reviewers praise that authoring lives in the same interface (turning a good ticket reply into an article is quick), while the recurring gripes are that the editor feels dated next to modern writing tools and that search accuracy degrades once the KB gets large. Plan around that: keep articles focused and your structure shallow, both of which directly counter the search problem.

(On sourcing: we re-verified every build step and plan-gating boundary against Freshworks' live pricing and support docs in June 2026. We don't hold a configured Freshdesk login, so the in-product Solutions UI isn't screenshotted here — the steps and gating are sourced to Freshworks' own documentation rather than a captured admin panel. Confirm packaging on freshworks.com before relying on plan names.)

The honest part: a KB is what powers AI deflection

Here's the connection most setup guides skip. Everything above — clean structure, customer-worded titles, fresh articles, gaps filled from search data — isn't just good for human self-service. It's the single biggest input into how much an AI can deflect. Both Freshdesk's native Freddy and any AI agent layer you add on top draw their answers from your knowledge base. Stated plainly: an AI layer is only as good as the KB you connect it to. Garbage KB, garbage answers.

That's where a dedicated AI agent layer like Macha fits — and what it is not. Macha isn't a help desk and it isn't a knowledge base. It runs on top of the Freshdesk (or Zendesk) you already use, reading the customer's actual question, pulling from your connected knowledge base and conversation history, resolving the issue in the same thread, and handing off to a human with full context when it isn't confident. It catches the tickets a static help center misses — the customer who emails instead of searching, or whose question needs an answer stitched from a few articles plus their order history.

But the order matters: build the Freshdesk KB right first; the AI rides on top of it. If your ticket mix is mostly repetitive questions your help center could answer, you can 7-day free trial, no credit card required once your KB is in shape and see how far a connected knowledge base takes you. For the native side, see how to automate Freshdesk with AI.

Frequently asked questions

How do I create a knowledge base in Freshdesk? Open the Solutions tab in the agent view, then build top-down: New Article → New Category for broad topics, New Article → New Folder (with a mandatory hierarchy and a visibility setting) for sub-sections, and New Article for the content itself. Enable and brand the Help Center portal under Admin → Channels → Portals so customers can read what you publish.

Where do I set up the Help Center portal? Go to Admin → Channels → Portals → new portal and click Start Setup, then toggle the portal on. Brand it from the Portal Settings tab (name, URL, languages, logo, favicon) and the Appearance tab (theme, colors, fonts). A self-service portal is included on every plan, including the Free program.

Is the knowledge base available on the Freshdesk free plan? Yes. A knowledge base and self-service portal are included on every Freshdesk plan, including the Free program. Advanced extras — multilingual KBs, multi-product portals, deep customization, and the formal approval workflow — require higher tiers (Pro or Enterprise).

How do I control who can see an article? Visibility is set at the folder level: Everyone (public), Logged-in users only, or Agents only. The agents-only option lets you keep internal SOPs in the same Freshdesk account as your public help center.

Can I require article approval before publishing? A software-enforced approval workflow (Draft → In Review → Approved → Published) is Enterprise-only. On lower plans the lifecycle is simply Draft → Published, so you should run review as a manual checklist before publishing.

Does Freshdesk support a multilingual knowledge base? Yes, from the Pro plan onward. You publish articles in multiple languages on one portal, and the Help Center auto-detects a visitor's preferred language by login or browser setting.

How do agents add KB articles to ticket replies? In the reply editor, type /s to insert a solution article (full text or link) and /c to insert a canned response. Freddy AI can also suggest relevant articles automatically based on the ticket.

How do I measure if my knowledge base is working? Use Freshdesk's article feedback (helpful / not helpful, surfaced via the Article Feedback view) and KB analytics (views, feedback, ratings). Review them monthly: fix "not helpful" articles, write new ones for zero-result searches, and prune stale content.

The bottom line

Building a Freshdesk knowledge base is genuinely an afternoon's work for a useful first version, not a quarter-long project: plan a shallow, customer-worded taxonomy from real ticket data, enable and brand the Help Center portal, build categories → folders → articles in Solutions with deliberate folder visibility, write your top ~20 deflection articles with SEO fields filled, publish (Enterprise approval workflow or a manual checklist on lower plans), surface articles in the widget and via /s, and review feedback and analytics monthly. Get those right and you deflect real tickets on day one — and you've built exactly the clean, fresh, well-structured knowledge base that sets the ceiling on how much any AI layer can resolve on top of it. Build it well, keep it fresh, and let the data tell you what to write next.

Verified against Freshworks' official Freshdesk documentation, June 2026. Freshworks revises packaging and plan gating periodically — confirm current details on freshworks.com before relying on them.