A knowledge base earns trust by being right, fresh, and findable. Most Freshdesk Solutions instances I audit fail at one or more. The product gives you the tools; you need the governance.
Category architecture
Three levels max: Category, Folder, Article. Categories are product or audience (“Billing,” “Account Setup,” “API”); folders are subtopics (“Invoices,” “Refunds,” “Tax”); articles are tasks (“How to download an invoice”).
Avoid flat structure. A 200-article folder is impossible to scan; a 12-article folder per subtopic is browsable. Aim for 8 to 15 articles per folder.
Article ownership
Every article needs a named owner, not “the team.” Without ownership, no one updates when the product changes. Add a custom field “owner_email” to the article (via the article API or frontend customization) and surface it in the article footer for internal users.
Owner change happens when the responsible team changes; do not orphan when an employee leaves.
Review cadence
Tag every article with last_reviewed date. Build a report of articles not reviewed in 180 days and assign owners to either confirm currency or rewrite. Without a forced cadence, half your articles will be stale within 18 months.
For high-traffic articles (top 20 by views), drop the cadence to 90 days. For low-traffic articles, 365 days is fine.
Visibility levels
Solutions supports four levels: All users, logged-in users, agents only, and selected companies. Set the right level on creation; do not default everything to “All users.” Internal-only articles (“How to escalate to engineering”) leaking public is embarrassing; external articles set to internal-only mean customers cannot self-serve.
Audit visibility quarterly with the article export.
Search and findability
Freshdesk search ranks by article title weight, then body, then tags. Front-load article titles with the user’s actual phrase (“How to reset your password,” not “Password reset procedures”). Tags should be alternative phrasings (“forgot password,” “lock out,” “reset PW”) not topic descriptors.
Track failed searches via Solutions Analytics. Each failed search is either a missing article or a tagging gap. Add monthly.
Translation discipline
If you maintain Solutions in multiple languages, the parent-child translation model means a non-English article cannot be edited independently of the English source. Update English first, then trigger translation review. Without that order, translations drift.
Use the translation_status field to flag stale translations after the English changes. A workflow triggered on english_article.updated sets all linked translations to “needs_review.”
Article-to-ticket linkage
Configure agents to insert a Solutions article link into a reply with one click. Track which articles get linked into which ticket categories; high-link articles indicate good coverage, zero-link articles indicate they are not solving real problems.
Deprecation, not deletion
When a feature retires, do not delete the article. Mark it deprecated, add a banner pointing to the replacement, and keep it indexed. Customers still bookmark old URLs; a 404 is worse than a “this is outdated, see X” notice.
What to do this week
Pull your top 20 articles by view count. Confirm each has an owner and a last_reviewed date in the past 90 days. Fix the gaps; this is the highest-leverage hour you will spend on KB this quarter.
