Freshdesk Solution Articles
Freshdesk solution articles are where the knowledge base lives: three levels of hierarchy, four of visibility, and one decision that determines whether anyone finds anything.
Categories, folders and Freshdesk solution articles
Freshdesk organises solutions in three levels and you can't skip one.
The structural mistake almost everyone makes is building the hierarchy around their org chart. Categories named after internal teams, folders named after systems nobody outside the company has heard of. Customers do not know your team structure and will never guess which folder holds their answer.
Build it around what customers are trying to do instead. Getting started, Billing and invoices, Troubleshooting, Account and login. Boring names win, because search and browsing both reward predictability. And keep the count low: a category list that fits on one screen without scrolling is a category list people will read.
Visibility, and the folder that leaks
Freshdesk sets visibility at the folder level, with roughly four options: everyone including anonymous visitors, logged in users only, agents only, and selected companies or contact segments.
Each has an obvious use. Public for anything you want indexed by search engines. Logged in for content that is only relevant to customers with an account. Agents only for internal procedures, escalation paths and the phrasing you use when telling someone their data is gone. Company-specific for content that belongs to one client under contract.
The internal article that leaks is almost never mislabelled. It's a correctly labelled article that somebody later moved into the wrong folder.
Two habits prevent it. Put the audience in the folder name, so "Internal: escalation procedures" cannot be confused with a customer folder at a glance. And audit visibility quarterly by opening your public portal in a private browser window and reading what an anonymous visitor sees. It takes five minutes and it is the only check that tests reality rather than settings.
One more thing worth knowing: internal articles are still useful to agents even when they never face a customer. Canned responses cover phrasing, articles cover procedure, and having both keeps your agent answers consistent.
Writing an article people finish
The structure that works is the same everywhere, and Freshdesk gives you the fields to support it.
Fill in the meta fields, the SEO title and description, if the article is public. A large share of help centre traffic arrives from search engines rather than your portal navigation, and those fields are what the results page shows.
Tags on articles help search inside the portal and are worth a light touch. Keep them consistent, the same way you would with ticket tags.
Drafts, approvals and keeping it current
Articles are drafts until published, which sounds trivial and is the thing that saves you. Draft, review, publish, and on higher plans a proper approval workflow where a reviewer signs off before anything goes live.
Whether you need approvals depends on the size of the team. Two people writing? A shared convention is enough. Twelve people, including support agents documenting fixes as they go? Approvals stop the knowledge base filling with half-finished notes.
The maintenance problem is bigger than the creation problem, and nobody plans for it. An article written two product releases ago that describes a screen which no longer exists is worse than no article, because the customer follows it, fails, and then contacts you annoyed.
Three low-effort habits. Review the least helpful articles by feedback score every quarter and either fix or delete them. Whenever a release changes a screen, search the knowledge base for the old label before the release ships. And when an agent has to explain around an article on a live ticket, that is a signal, so give them a fast way to flag it.
Wiring articles into the workflow
An article nobody links to is a document, not a knowledge base.
Surface them in the support widget and the portal search so customers meet them before submitting. Put the top five into your auto-reply. Have agents send links rather than retyping answers, which keeps the wording consistent and drives traffic that tells you which articles matter.
Then read the feedback. The helpful and not-helpful counters are crude, but an article with a lot of views and a poor score is telling you something specific and fixable. Pair that with your reporting on ticket volume by reason: the gap between your top ticket reasons and your top articles is your content backlog, already prioritised.
Frequently asked questions
Are solution articles the same as knowledge base articles?
Yes. Freshdesk knowledge base articles is the generic name; Freshdesk calls them solutions, and they live in categories and folders under that label.
How are Freshdesk solution articles organised?
Three levels: category, then folder, then article. Visibility is set on the folder, and in a multi-portal account categories are what you map to each portal.
Can I make an article visible only to agents?
Yes. Folder visibility includes an agents-only option, along with public, logged in users, and selected companies or contact segments.
Do solution articles get indexed by search engines?
Public articles can be, and a large share of help centre traffic arrives that way. Fill in the SEO title and description fields, and write titles that match what people search for.
Is there an approval workflow for articles?
Draft and published states exist on all plans. A formal approval workflow with reviewers sits on the higher tiers, so check your plan if you need sign-off before publishing.
How many articles should we start with?
Five. Take your most common ticket reasons from a month of real tickets and write those properly. Breadth without accuracy makes search worse, not better.
Fewer articles, fewer duplicate tickets
Good self-service cuts repeat contacts, but not all of them. Ticket Merger merges the duplicates that still arrive, automatically.
Start free trial14-day free trial. No credit card required.