The Freshdesk Knowledge Base
Freshdesk calls them solution articles. Customers call them the reason they did not have to contact you.
How it is structured
Freshdesk organises content as categories, folders and solution articles. Folders control visibility, which is the useful part: an article can be public, restricted to logged-in users, restricted to specific companies, or internal to agents.
That means your agent runbooks and your public documentation live in the same system without leaking into each other, and agents can insert a solution article into a reply without leaving the ticket.
What to write first
Not a content plan. Your own ticket data.
Export a month of tickets, group by subject, and write the ten most repeated answers. Then check the search terms in your portal that returned nothing, because that list is written by your customers and is more useful than anything you would brainstorm.
Write each article so the answer is in the first two sentences. People scan to check they are in the right place before they read anything.
Making it deflect
Publishing is half the job. The other half is placement.
What documentation cannot fix
Someone who emailed an hour ago and has now filled in the portal form is not missing information, they are missing a reply. No article prevents that second contact, and it arrives as a duplicate rather than a new question.
Frequently asked questions
Can I restrict Freshdesk articles to certain customers?+
Yes. Folder visibility can be public, logged-in users, specific companies, or agents only.
How do I know if the knowledge base is working?+
Watch ticket volume for the documented topic and the failed-search report. Article views tell you almost nothing.
The contacts no article prevents
Impatience creates duplicates, not knowledge gaps. Ticket Merger removes them before an agent replies twice.
Start free trial14-day free trial. No credit card required.