vs
HelpDocs vs Salesforce Knowledge
One is a knowledge module inside a CRM. The other is a knowledge base that happens to be the whole product.
The verdict
These are not really the same kind of purchase.
Salesforce Knowledge is a module inside Service Cloud, so it is the obvious answer if your cases, agents, and reporting already live in Salesforce and you want articles in the same console. HelpDocs is a standalone knowledge base, so it is the obvious answer if what you actually need is a fast, well-branded public help center and you do not want to buy a CRM to get one.
HelpDocs is best for
Teams who want a customer-facing help center live this week, priced flat, without a Salesforce admin, a consultant, or an Experience Cloud site in the plan.
Salesforce Knowledge is best for
Organizations already standardized on Salesforce, where agents work cases in the Service Console all day and knowledge needs to sit inside that workflow, feed Agentforce, and report through the same platform.
Feature by feature
How they stack up, feature by feature
A side-by-side look at what HelpDocs and Salesforce Knowledge each include, grouped by the job you're trying to do.
Setup & onboarding
How quickly you can go from signup to a live, branded knowledge base.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| Free trial without talking to salesYou can start a Salesforce trial, but standing up Knowledge plus a customer-facing site is a configuration project rather than a signup. | Yes | Limited |
| Published, self-serve pricingService Cloud edition prices are published per user per month, but totalling up a help center means pricing several things: Knowledge read/write is an extra $75/user/mo on Enterprise, self-service portal logins are priced on a separate page, and Agentforce credit consumption sits on top of both. | Yes | Limited |
| Standalone knowledge base (no support suite required)Knowledge is a module of Service Cloud. You buy the CRM and the seats, then configure knowledge inside it. | Yes | No |
| Live help center the same daySalesforce lists Help Center from Enterprise up, but standing one up means connecting Knowledge to a site and building it. HelpDocs is live the same day. | Yes | No |
| Starter templates and sample contentExperience Cloud ships site templates, including a help center template, but they are templates to configure rather than a finished help center. | Yes | Limited |
| Guided migration from other toolsHelpDocs: Built-in importers for Zendesk Guide, Intercom Articles, Help Scout Docs, Document360, GitBook, ReadMe, Notion, Google Drive and more, plus GitHub: point it at a repo and its Markdown and MDX files become articles.Importing articles means data loading or an integration partner. HelpDocs has one-click migrations from Zendesk, Intercom, Help Scout, ReadMe, Helpjuice and ProProfs. | Yes | No |
Authoring & editing
The day-to-day writing experience for the people who maintain your docs.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| WYSIWYG editorLightning Knowledge has a rich text editor, though it is a CRM record editor rather than a writing tool. | Yes | Yes |
| Custom HTML blocks in articlesRich text fields accept a restricted set of HTML. Salesforce sanitizes markup, so arbitrary embeds are constrained. | Yes | Limited |
| Reusable snippets and content variablesHelpDocs: Clips are reusable blocks of content, static or dynamic, and Variables hold a single piece of text like a product name or support email. Both are on every plan, and a Variable dropped into a Clip can be overridden per article.Achievable with quick text, templates, or custom development, but there is no first-class reusable snippet for article bodies. | Yes | Limited |
| Category and nested navigation managementData categories and category groups are genuinely powerful, and drive both agent visibility and site navigation. | Yes | Yes |
| Version history with side-by-side diffKnowledge has draft, published and archived versions with version history, but no side-by-side visual diff. | Yes | Limited |
| Review and approval workflow builderThis is a real Salesforce strength. Approval processes on Knowledge articles are mature, configurable and auditable, and Workflow and Approval is listed from Enterprise up. | Limited | Yes |
AI & search
How well the knowledge base answers questions and deflects tickets on its own.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| AI answers from your articlesAgentforce and Einstein answer from Knowledge, and this is one of the strongest reasons to keep knowledge in Salesforce. Agentforce for Service is available for purchase on Enterprise and Unlimited and included on Agentforce 1 Service. | Yes | Yes |
| AI included in the base subscriptionAI for Customer Service starts at Enterprise, where Agentforce for employees is marked Flex Credits Required. Agentforce 1 Service at $550/user/mo is the edition that includes it unmetered, with 2.5M Flex Credits per org per year. HelpDocs bundles AI credits into every plan. | Yes | No |
| AI drafting and rewriting in the editorEinstein can draft and summarize article content, gated by edition and Agentforce entitlement. | Yes | Yes |
| AI style and tone enforcementTone can be steered through prompt configuration, but there is no simple style-guide enforcement toggle. HelpDocs enforces writing style with AI on Bloom and up. | Yes | Limited |
| AI meta descriptions and SEO helpersNo AI SEO helpers for knowledge articles. SEO on an Experience Cloud site is configured by the site builder. | Yes | No |
| Full-text search with failed-search reportingSearch is strong inside the console and on the site, but failed-search reporting for a public help center is something you build in reports rather than open out of the box. | Yes | Limited |
| AI-powered semantic searchHelpDocs: Ask AI draws on your monthly AI credits each time a reader uses it, so semantic search consumes the same pool as AI authoring.Einstein Search and Agentforce retrieval are semantic, and at Salesforce's scale this is well proven. | Yes | Yes |
| AI agent that resolves live conversationsAgentforce resolves live conversations end to end. HelpDocs is a knowledge base and does not do this at all. | No | Yes |
Branding & customization
Making the help center look and feel like your own product, not a vendor template.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| Custom domainAn Experience Cloud site can run on your own domain, which requires configuring domains and certificates in Salesforce. | Yes | Yes |
| No-code color, font, and layout stylingExperience Builder is genuinely capable no-code theming, with branding sets and page-level layout control. | Yes | Yes |
| Custom CSSExperience Builder supports custom CSS, and Lightning Web Components for anything beyond it. | Yes | Yes |
| Custom JavaScriptAvailable through Lightning Web Components, which is a development workflow rather than pasting a snippet. | Yes | Yes |
| Full HTML template controlYou control components and layout, but you are inside the Experience Cloud rendering model rather than authoring the page template. | Yes | Limited |
| Remove vendor branding (white-label)An Experience Cloud site on your own domain carries your branding. Note HelpDocs cannot remove its own branding on any plan. | No | Yes |
| Multi-brand help centersHelpDocs: Additional custom domains give each brand its own logo, colors, navigation and SEO over the same articles (2 included on Harvest, an extra fee otherwise). Brands that need different content run as separate accounts on one bill.Multiple Experience Cloud sites can serve multiple brands with different content from one org. HelpDocs brands share one set of articles across domains, or run as separate accounts. | Yes | Yes |
Access & permissions
Who can read and edit what, and whether the platform meets security reviews.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| Private or internal knowledge baseInternal-only knowledge for agents is the default mode, and no external site is needed for it. | Yes | Yes |
| Unlimited free reader accountsHelpDocs: Anonymous readers of a public help center are unlimited and free. Gated or authenticated readers can cost extra.Anonymous public visitors to the site are free. Authenticated readers are licensed separately, and Salesforce's self-service pricing page lists $4 per login or $10 per member per month. HelpDocs includes unlimited free anonymous readers on every plan. | Yes | Limited |
| Content-level permission groupsProfiles, permission sets, sharing rules and data categories give very fine-grained control. Few tools match this. | Yes | Yes |
| SSO and SAMLMature SAML and SSO support. On HelpDocs, SSO is on Harvest. | Yes | Yes |
| SCIM user provisioningHelpDocs: HelpDocs has limited SCIM provisioning, alongside SAML, OIDC, and JWT SSO.Salesforce supports SCIM provisioning. HelpDocs SCIM support is limited, and this is a real gap on our side. | Limited | Yes |
| Audit trailField history, setup audit trail and optional Shield event monitoring. HelpDocs has an audit trail on Bloom and up. | Yes | Yes |
Analytics
Understanding what readers search for, what works, and where content is failing.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| Article views and engagementArticle view and rating data is reportable, and Knowledge has its own reporting objects. | Yes | Yes |
| Search and failed-search reportingSearch activity is reportable with configuration, rather than a ready-made failed-search view. | Yes | Limited |
| AI answer and deflection analyticsAgentforce and case deflection can be measured, but assembling the reporting is a project. HelpDocs ships deflection reporting. | Yes | Limited |
| Reader feedback and ratingsArticle ratings and feedback are supported on both the console and the site. | Yes | Yes |
| Contributor and team performance reportsReports and dashboards over Knowledge objects are a genuine strength and go well beyond what HelpDocs offers, though the advanced reporting features start at Enterprise. | Yes | Yes |
| Reporting data exportReports export, and the platform APIs give full data access. | Yes | Yes |
Integrations & API
How the knowledge base plugs into the rest of your stack, and whether it doubles as a support suite or developer docs.
| Feature | HelpDocs | Salesforce Knowledge |
|---|---|---|
| Public REST API and webhooksHelpDocs: HelpDocs has a read/write REST API, plus Slack webhooks for publish, feedback, and team events. It does not have general-purpose outbound webhooks.Comprehensive REST and Bulk APIs, plus platform events and outbound messages. The Web Services API is included from Enterprise and costs an extra $25/user/mo on Pro Suite. HelpDocs has a read/write REST API but no outbound webhooks. | Limited | Yes |
| IntegrationsAppExchange is the largest ecosystem in the category by a wide margin. | Yes | Yes |
| Help desk integrations (Intercom, Zendesk)Salesforce is the help desk, so integrating a competing one is possible but beside the point. | Yes | Limited |
| Embeddable in-app help widgetEmbedded Service deployments put chat and knowledge in your product. | Yes | Yes |
| Built-in live chat and messengerSalesforce's edition table prices Enhanced Messaging as an extra $75/user/mo on both Enterprise and Unlimited, included only on Agentforce 1 Service, with Einstein Bots the same $75 extra on Enterprise. HelpDocs has no live chat. | No | Yes |
| Built-in ticketing and shared inboxCase management is the core of Service Cloud, and HelpDocs does not do ticketing at all. | No | Yes |
| OpenAPI and Swagger reference renderingNot a developer documentation tool. Neither is HelpDocs. | No | No |
Pricing
Pricing, side by side
Service Cloud edition prices below are from Salesforce's own pricing page as of September 2026, shown in USD per user per month. Two things sit outside the edition price and both matter for a help center: Knowledge read/write costs extra on Enterprise, and the self-service portal licenses that let customers log in are priced on a separate page. Agentforce credit consumption beyond what your edition includes is a third.
Sprout
$99/mo billed annually (23% off). 5 editors, 1,000 AI credits/mo, AI meta features, AI drafts and rewrites, Ask AI, 3 languages, the Lighthouse widget, custom CSS and JavaScript, unlimited free public viewers.
Bloom
$239/mo billed annually (20% off). 15 editors, 5,000 AI credits/mo, AI meta features, AI drafts and rewrites, Ask AI, AI improve, AI style enforcement, 20 languages, audit trail, advanced permissioning, embedded SSO (JWT), the Lighthouse widget, custom CSS and JavaScript, custom HTML templating, unlimited free public viewers.
Harvest
$399/mo billed annually (20% off). 25 editors, 10,000 AI credits/mo, AI meta features, AI drafts and rewrites, Ask AI, AI improve, AI style enforcement, unlimited languages, audit trail, advanced permissioning, SSO with anonymous mode, IP restriction, the Lighthouse widget, custom CSS and JavaScript, custom HTML templating, unlimited free public viewers.
Starter Suite
Starting price. Transaction fees apply. Billed monthly or annually. A CRM suite, not a service desk.
Pro Suite
Starting price, transaction fees apply. Billed annually, contract required. Adds enhanced real-time chat, more customization and automation.
Enterprise
Billed annually. Salesforce lists AI for Customer Service, Self-Service Help Center and Workflow Automation as the headline features, and this is the first edition with Help Center. Knowledge is read-only here.
Knowledge read/write on Enterprise
Salesforce's edition table gives every edition Knowledge read-only, and charges an extra $75 per user per month on Enterprise for the read/write access authors need. Unlimited and Agentforce 1 Service include it.
Unlimited
Billed annually. Everything in Enterprise plus Chat and Bots, Salesforce Knowledge read/write included, and the Premier Success Plan with a full sandbox.
Agentforce 1 Service
Billed annually. Full AI suite, unmetered Agentforce for employees, and 2.5M Flex Credits per org per year. It also includes the authenticated portal and Customer Community that Enterprise and Unlimited buy separately.
Agentforce Service Portal
Or $10 per member per month with unlimited sessions. Licenses authenticated customer readers on the self-service portal that exposes your Knowledge articles. Anonymous public reading is included with the site, so this applies when readers log in.
Help Agent Resolutions
Salesforce's out-of-the-box AI service agent for self-service channels, priced per resolution, with unmetered Agentforce actions and Data 360 queries inside each resolution.
The bottom line: The shape of the bill is the real difference, not the headline number. Salesforce charges per user per month on an annual contract, so five support people on Unlimited is $1,750 a month before the help center exists, and five on Enterprise is $1,250 once you add the $75 Knowledge read/write seat your authors need. Then it stacks: if your customers log in to the portal, Salesforce prices that separately at $4 per login or $10 per member per month, so growing readership grows the bill. HelpDocs is flat: $129/mo on Sprout for five editors, and public readers are unlimited and free, forever.
Switching
Switching from Salesforce Knowledge
Moving articles out of Salesforce Knowledge is mostly a data export problem, and it is very doable. Articles live as records, so you can export them with the standard data tools or the API, then bring the content into HelpDocs. The part that takes thought is not the content, it is deciding what stays behind. If agents rely on knowledge inside the Service Console, or Agentforce answers from those articles, you are choosing to split the internal and external halves of your knowledge rather than simply moving it. Plenty of teams do exactly that on purpose, keeping internal runbooks in Salesforce and putting the customer-facing help center somewhere built for customers. Be deliberate about which one you are doing. Once exported, the records come in as a CSV, which is one of several routes depending on what you can get out.
- 1Export your published Knowledge articles and their data category assignments using Data Loader or the REST API.
- 2Decide the split: which articles are genuinely customer-facing, and which are internal agent runbooks that should stay in Salesforce.
- 3Rebuild your data category structure as HelpDocs categories, which is usually a simplification rather than a like-for-like copy.
- 4Import the customer-facing content, then fix internal links and images.
- 5Map every old Experience Cloud article URL to its new HelpDocs URL and set up redirects before you switch the domain, or you will lose the search traffic those pages earned.
- 6Point your help center domain at HelpDocs, and leave the Experience Cloud site up until the redirects are verified.
Honest trade-offs
Why teams pick one over the other
Why teams choose HelpDocs
- Live the same day. A branded public help center on your own domain, with no CRM to configure, no admin, and no implementation partner. Salesforce lists its Self-Service Help Center from Enterprise at $175/user/mo up, and it is still a site you build.
- Flat, published pricing: $129/mo Sprout for 5 editors, $299/mo Bloom for 15, $499/mo Harvest for 25, or $99, $239, and $399 billed annually. Every editor can write, where Salesforce charges an extra $75/user/mo on Enterprise for the Knowledge read/write access authors need.
- Public readers are unlimited and free on every plan. Salesforce prices logged-in portal readers at $4 per login or $10 per member per month, so a growing readership grows the bill.
- AI credits are included in every plan rather than metered, from 1,000 a month on Sprout to 10,000 on Harvest, with Ask AI plus AI drafting and rewriting on every plan.
- Built for the reader as well as the agent: failed-search reporting, article ratings and deflection reporting come as standard, and the V5 templates score 100/100 for SEO and accessibility in PageSpeed.
- One-click migrations from Zendesk, Intercom, Help Scout, ReadMe, Helpjuice and ProProfs, so switching is a task rather than a project.
- The Lighthouse widget drops into any web app with a short snippet on every plan, with no Embedded Service deployment to configure.
Why teams choose Salesforce Knowledge
- If your team already lives in Salesforce, knowledge inside the Service Console is a genuinely better agent experience than any external tool can offer.
- Agentforce resolving live conversations end to end is something HelpDocs does not attempt. If AI-first case resolution is the goal, this is the platform for it.
- Approval workflows, permission sets, sharing rules and data categories give governance that very few knowledge base products come close to.
- Case management, live chat, telephony and field service in one platform, where HelpDocs is only ever the knowledge base.
- Reporting and dashboards over knowledge data, plus SCIM provisioning and Shield event monitoring, are all areas where Salesforce is straightforwardly ahead of us.
- Several brands with different content from a single org, and full white-labelling. HelpDocs does neither: its extra domains share one set of articles.
FAQ
Questions about HelpDocs vs Salesforce Knowledge
Is Salesforce Knowledge included in Service Cloud?
Do I need Experience Cloud to have a public knowledge base in Salesforce?
Is HelpDocs cheaper than Salesforce Knowledge?
Can I keep Salesforce and use HelpDocs for the help center?
What does HelpDocs not do that Salesforce does?
Not decided yet
Still building a shortlist?
A head-to-head is the wrong shape when you have not narrowed the field yet. Our roundup compares twelve knowledge base tools on setup, search, branding and real pricing.
Ready to switch to HelpDocs?
Create, organize, translate, and connect your docs without the admin sprawl of a support suite.
No credit card required.
