Help desk software with a knowledge base on the free tier: what you get and how to start

A knowledge base is the cheapest way to make a small support team feel bigger. Every question you answer once in writing is a question you never type out again. So it is frustrating that on many help desks the knowledge base is exactly the feature that sits just above the free plan.

This guide covers two things: which free tiers actually include a knowledge base (and what the caps look like), and a practical method for filling one with your first ten articles using the tickets you already have.

Why the knowledge base is the first feature small teams miss

Most free help desk plans give you a ticket queue and email. What they tend to hold back is anything that reduces ticket volume. That is a reasonable business decision for the vendor, but it hits small teams hardest: with two or three people answering everything, repeated questions are the main source of load.

If you are choosing a tool mainly on this criterion, the useful question is not “does it have a knowledge base?” but “can I publish an article today, on the plan I’m actually paying for, without a sales call?” The sections below check that against vendors’ live pages.

What three vendors say about the knowledge base, as of 2026-10-19

Pricing pages change and some render differently by region, so treat these as a snapshot and confirm before you buy.

Help Scout: a docs site on the free plan, with a small article cap

Help Scout’s pricing page (as of 2026-10-19) says Docs, its knowledge base product, is included in every plan, including Free. The Free plan is described as including 5 users, 1 inbox, and 1 Docs site, and the page lists a cap of 10 articles on Free, with unlimited articles on paid plans. Paid plans are listed at $25 (Standard), $45 (Plus), and $75 (Pro) per user per month; the page doesn’t make clear whether those figures assume annual billing. Extra Docs sites cost $20 per month beyond what each plan includes.

The honest read: this is the most generous free knowledge base of the ones I checked, but ten articles is a ceiling you will hit quickly if you use the method below.

Zoho Desk: not on the free plan

Zoho Desk’s pricing page (as of 2026-10-19) lists three user licenses on the Free edition and shows no knowledge base or self-service features for it, or for Express. The knowledge base appears at the Standard tier, alongside a self-service widget, an answer bot, and a community forum. The page rendered in INR for this check (Standard at ₹800 per user per month, billed annually); convert at your own rate or switch the currency selector. Its FAQ also says Standard allows 5 users, so the tier that unlocks a knowledge base is also the one that caps your team.

Freshdesk: no free plan, knowledge base from the entry paid tier

Freshdesk’s pricing page (as of 2026-10-19) lists Growth, Pro, and Enterprise at $19, $55, and $89 per agent per month on annual billing. It mentions a 14-day trial of the Enterprise plan and does not mention a free plan. The customer portal and knowledge base are bundled into Growth; multilingual articles, portal customization, and article versioning move up to Pro, and an approval workflow for publishing sits at Enterprise. The tier split is read from the page’s comparison table, so check it with the vendor if it matters to you.

For a team of three, that is about $57 per month before any add-ons just to have a knowledge base at all.

Where ITSM fits

ITSM includes a knowledge base alongside incidents, requests, problems, changes, a CMDB, and SLA tracking. The free tier is 2 seats at $0 with instant signup at /register; Basic is $29 per month with 3 seats included and $5 per extra seat. If you need more than two seats, you move to Basic rather than to a per-agent price that multiplies. I haven’t verified a published per-article cap comparison against the vendors above, so check the current limits when you sign up rather than taking this paragraph as a spec sheet.

How to seed your first ten articles from real tickets

The mistake most teams make is writing a knowledge base from imagination. Write it from evidence instead.

Step 1: Pull the last 30 days of closed tickets

Export or scan resolved tickets and sort by subject. You are looking for repeats, not importance. Wi-Fi, password resets, printer setup, “how do I get into the shared drive” are the usual suspects.

Step 2: Rank by how often, not how interesting

Count each topic. The top ten by frequency are your first ten articles. If you are on a capped plan like Help Scout’s free tier, this ranking is also how you decide what earns one of your ten slots.

Step 3: Write from the resolution notes

Whatever the technician actually did to fix it is the article. Copy the steps, remove client-specific details, and add the symptom as the title. A title that matches what the user types (“Printer shows offline”) beats a tidy internal name (“Print spooler recovery”).

Step 4: Use a fixed template

Keep every article to the same shape:

• Symptom: one sentence, in the user’s words.
• Cause: one sentence, only if it helps.
• Fix: numbered steps, no more than eight.
• If that didn’t work: how to reach you.

Consistency makes articles faster to write and faster to scan.

Step 5: Link the article in the reply, then measure

The knowledge base only deflects tickets if people see it. Paste the article link into the reply the next time the question arrives, and add the link to your auto-acknowledgment email. After a month, recount: if the same topic is still in the top ten, the article is either hard to find or does not solve the problem. Rewrite the title first.

Keeping the knowledge base honest

Two habits keep a small knowledge base useful:

1. One owner per article. Put a name and a review date on each. Stale instructions are worse than none.
2. Close the loop on every ticket. When a technician closes a ticket that needed a workaround, they ask: is this in the knowledge base? If not, it goes on the list.

This pairs well with a proper ticket workflow. If you are still working out of a shared inbox, how to move from a shared inbox to a help desk covers the migration, and free help desk software with instant signup shows how to tell a genuine free tier from a trial. If your articles start covering hardware and software your clients own, help desk software with a CMDB explains why linking articles to assets pays off, and affordable help desk software with SLA tracking covers the other feature that tends to get gated.

A short checklist before you commit

• Can you publish an article on the exact plan you will pay for?
• What is the article or site cap, and does it fit your first 30 articles?
• Does the plan that unlocks the knowledge base also cap your seat count?
• Can you export your articles if you leave?
• Is article search good enough that a customer finds the answer before they open a ticket?

Run that list during a trial, with real content, not the demo data.

ITSM is a small product with a free tier, so test it against your own tickets before deciding.