Facebook-f Twitter Instagram

Your Customer Portal Is Priced to Fail

Your Customer Portal Is Priced to Fail

Gartner has now published two findings that, read together, should change how you build customer self-service on top of your CRM. In a survey of 5,728 customers, only 14% of service issues were fully resolved in a company’s own self-service channel. In a later survey of 5,801 customers, 51% of service journeys began somewhere else entirely — Google, YouTube, ChatGPT — and only 22% of customers started, stayed, and resolved inside first-party channels. Most CRM buyers read that as a content problem or a UX problem. It is usually neither. It is a pricing problem: every major CRM platform meters authenticated external users and gives away public ones, and that single fact quietly determines how much of your knowledge ends up behind a login where neither your customers nor an AI assistant can reach it.

Key Takeaways

  • Gartner found only 14% of service issues are fully resolved in company self-service channels, while 43% of users said they couldn’t find content relevant to their issue.
  • 51% of service journeys now start on third-party platforms, and customers report a 62% success rate finding answers on places like Google and YouTube — higher than they report on vendor sites.
  • Authenticated external access is the metered resource: Salesforce Customer Community Plus runs $15 per login or $35 per member per month, while HubSpot gates its portal behind Service Hub Professional at $90 per seat per month plus a $1,500 onboarding fee.
  • Unauthenticated access is effectively free on every platform — Salesforce guest users consume no external licenses at all, and Zoho Desk’s Help Center can be fully public and search-indexable.
  • NetSuite is the outlier: its Customer Center role gives external customers portal access without consuming user licenses.
  • AI service agents are now priced per outcome — HubSpot’s Breeze Customer Agent at $0.50 per resolved conversation since April 2026, Salesforce’s Agentforce at $2 per resolved case or $0.10 per Flex Credit action — which only pays off if the agent can reach your content.
  • The right architecture separates public knowledge (unmetered, indexable, AI-readable) from authenticated account data (metered, deliberately narrow).

The login wall is almost never a design decision

Walk into any mid-market CRM implementation and ask why the knowledge base sits behind a login. You will rarely get a security answer. You will get some version of “that’s how the portal was set up.” And the portal was set up that way because the portal is the licensed object. The vendor sold a portal; the implementation partner configured a portal; the portal has a login page; the content went inside it.

That sequence is backwards, and it is expensive in two directions at once. You pay per external identity for people who are just looking for a troubleshooting article, and you simultaneously hide that article from the 51% of journeys that begin on a search engine or an AI assistant. Gartner’s 2024 study is blunt about the consequence: 43% of self-service users said they couldn’t find content relevant to their issue. Some of that is genuinely missing content. A meaningful share of it is content that exists, is accurate, is maintained — and is unreachable without credentials the customer never created.

Eric Keller, a senior director of research at Gartner, framed the gap plainly when the study was published: 73% of customers use self-service at some point, yet so few fully resolve there. The uncomfortable follow-on is that customers report a 62% success rate on third-party platforms. Your competition for the first click is not another vendor. It is a YouTube video someone else made about your product.

What external access actually costs in 2026

Before you can design around the economics, you need the real numbers. These are the published figures as of October 2026, and they differ by more than an order of magnitude across platforms.

Platform How external access is licensed Published price
Salesforce Experience Cloud (Customer Community Plus) Per login or per named member, billed annually $15 USD/login/month or $35 USD/member/month
Salesforce Experience Cloud (Partner Community) Per login or per named member, billed annually $20 USD/login/month or $50 USD/member/month
Salesforce guest (unauthenticated) users Shared guest user profile per site No external licenses consumed
HubSpot customer portal Feature gated to Service Hub Professional/Enterprise; external portal users not separately licensed $90/seat/month (Pro, annual) + $1,500 one-time onboarding; $150/seat/month (Enterprise)
Zoho Desk Help Center Agent seats; Help Center itself can be public or registered-only Roughly $7–$40 per agent/month by edition; KB and community from Standard up
Zoho CRM Portals Portal user types with a free allowance, then paid packs Up to 5 portal user types and 1,000 portal users free; Enterprise and Ultimate editions only
NetSuite Customer Center Dedicated external role Unlimited external customer access, free to assign

Read that table as a strategy document, not a price list. Salesforce charges you per external identity, so every authenticated page view has a marginal cost and every unauthenticated one does not. HubSpot charges you nothing per external user but puts the portal behind a tier jump — and its portal is deliberately narrow, showing only tickets, not conversations that were never converted into tickets. Zoho sells you agent seats and lets you choose whether the Help Center is open to the world. NetSuite, which almost nobody thinks of as a portal platform, is the only one of the four where scaling external self-service to 10,000 customers costs the same as scaling it to 100.

If you are a Salesforce shop evaluating the login-versus-member metric, the practical rule is that member licenses are predictable but punishing for sporadic users, while login pools look cheap until a seasonal spike burns through them. We have seen both failure modes. The one worth planning for is the second, because it fails during your busiest week.

Public is free, and that is the whole insight

Salesforce documents this directly: if you intend to use an Experience Cloud site as a public knowledge base for unauthenticated visitors, you do not have to purchase community licenses, and guest users do not consume external licenses. Every public site has a single guest user profile shared across all unauthenticated sessions, and since Summer ’20 you must explicitly grant guest record access through sharing rules rather than relying on org-wide defaults — which is exactly the control you want.

Zoho Desk gives you the same lever in one setting. Under Setup > Channels > Help Center > Access settings, turning off “Customers must register to access Help Center” opens the knowledge base and community to anyone and lets unregistered visitors submit a request (with CAPTCHA to keep bots out). Those visitors can’t view ticket history without logging in — which is correct, and is precisely the boundary you should be drawing.

HubSpot lets you set visibility per article: available to all visitors, or visible only to registered users. One detail worth knowing before you assume you’re indexed: HubSpot’s setting to block knowledge base pages from search engines applies to knowledge base search result pages, not individual articles. Verify your own article-level indexing rather than trusting the default.

The conclusion writes itself. The content that answers “how do I reset this,” “what does this error mean,” and “what are your return terms” has no business behind a login. It costs you license consumption, it costs you organic discovery, and it costs you presence in the AI answer layer where half of all journeys now begin.

Where AI agents change the math — and where they don’t

Both Salesforce and HubSpot have moved their customer-facing AI agents to outcome-based pricing in 2026, and the numbers are specific enough to model.

  • HubSpot Breeze Customer Agent: as of April 14, 2026, a resolved conversation costs 50 credits, or about $0.50 — down from $1.00 per conversation billed whether or not the issue was solved. Credits are bundled by tier (500 on Starter, 3,000 on Professional, 5,000 on Enterprise), reset monthly, don’t roll over, and overage bills at roughly $0.01 per credit. On Professional, the included allowance covers about 60 resolutions a month.
  • Salesforce Agentforce: Flex Credits run $500 per 100,000 credits, with 20 credits ($0.10) per standard action and 30 credits ($0.15) per voice action. The alternative conversation metric is $2 per conversation, and Help Agent is sold at $2 per resolved case. You pick one consumption model, not both.
  • Zoho Desk: AI Agents are available from the Express edition up, with access to pre-built agents and up to 30 million free tokens per month — a genuinely different posture from per-resolution billing.

Here is the part most buyers miss. An AI agent priced per resolution is only cheap if it resolves. And it resolves based on the same content your human-facing knowledge base uses. If 43% of your customers can’t find a relevant article, your agent will fail on roughly the same questions — except now each failed attempt either bills you (under per-conversation and per-action models) or escalates to a human (under per-resolution models). Outcome-based pricing protects you from paying for failure. It does not protect you from the failure.

Don’t benchmark these against a vendor’s cost-savings slide. Take your own fully loaded support payroll plus tooling, divide by tickets handled last quarter, and compare that to $0.50 or $2.00 per resolution. Then multiply by a realistic containment rate — and let Gartner’s 14% figure discipline your optimism about what that rate will be in month one.

The architecture we actually recommend: three tiers, three cost profiles

Stop designing “a portal.” Design three layers with different access models and different economics.

  1. Tier 1 — public, indexable, AI-readable knowledge. Product documentation, troubleshooting, policies, pricing explanations, how-tos. Unauthenticated. Crawlable. On a domain you control. Zero license consumption on every platform discussed here. This is the layer that competes for the 51% of journeys starting on Google and ChatGPT, and it is the grounding content your AI agent will cite. Write it for a machine reader as well as a human one: clear headings, explicit question phrasing, no critical information trapped in images or PDFs.
  2. Tier 2 — authenticated, account-specific transactions. Order status, invoices and payments, open cases, entitlements, returns, contract documents. This is the only layer that genuinely requires identity, and therefore the only layer that should consume metered external licenses. Size it from real transaction volumes, not from your total customer count. On NetSuite, Customer Center already covers much of this — cases, order history, quotes, invoice payment, return authorizations — at no per-user cost, though be realistic that native NetSuite rarely automates payment posting or case routing end to end without additional work.
  3. Tier 3 — assisted and human. AI agent first, with a clean, instrumented handoff to a person. Log every escalation reason. Those reasons are your Tier 1 content backlog, and reviewing them monthly is the single highest-return habit in self-service operations.

Two platform-specific notes. If you are on Zoho Desk and running more than one brand, multi-brand Help Center and Guided Conversations are Enterprise-edition features — plan the edition around the architecture, not the reverse. If you are on Zoho CRM and want a lightweight client portal rather than a full support desk, CRM Portals supports up to five portal user types with 1,000 portal users included, but only on Enterprise and Ultimate.

CRM Experts Online’s Perspective

When a client asks us to “build a customer portal,” our first question is never about branding or page layout. It is: which of your top 20 inbound questions require knowing who the customer is? In most engagements the honest answer is four or five. The other fifteen are general knowledge that has been sitting behind a login for years, invisible to search engines, invisible to AI assistants, and quietly inflating a license line item.

We have also learned to be skeptical of portal projects that start with license procurement. Buying a block of Customer Community Plus member licenses before you know your authenticated session volume is how organizations end up with a $35-per-member price tag on users who log in twice a year. The reverse mistake is just as common: choosing login-based licensing for a high-traffic site and discovering in Q4 that the pool is exhausted. Model both metrics against twelve months of real ticket and web-session data before you sign anything.

On the AI side, our position is unambiguous. Do not pilot a customer-facing agent before Tier 1 is clean. An agent grounded on thin, stale, or login-gated content will produce exactly the outcome Gartner measured — and now you’ll be paying per attempt for the privilege. Spend the first six weeks on content consolidation and deflection instrumentation. The agent deployment that follows will be cheaper, faster, and far easier to defend in a renewal conversation.

Finally: measure the right thing. Ticket volume reduction is a lagging, noisy metric. Track resolution rate within self-service, escalation reasons by category, and the share of organic landings on your knowledge base that came from outside your own site search. That third number tells you whether you are actually competing where your customers start.

FAQ

Does making our knowledge base public create a security risk? Not inherently, but it requires deliberate configuration. On Salesforce, guest user record access must be granted explicitly through sharing rules or sharing sets — org-wide defaults no longer grant it automatically. The discipline is the same everywhere: publish articles, never records. Account-specific data stays in Tier 2.

Will a public help center hurt us competitively? Occasionally, for genuinely proprietary methodology. For troubleshooting and policy content, hiding it mostly means a third party writes the answer instead, and ranks for it. Gartner found nearly three-quarters of Gen Z customers start with a third party before reaching an official channel.

Login-based or member-based Experience Cloud licenses? Model both against twelve months of actual authenticated sessions. Logins suit infrequent, bursty access; members suit a predictable set of regular users. The failure mode to protect against is a login pool exhausting during a seasonal peak.

We’re on HubSpot. Is the customer portal enough? It depends on scope. HubSpot’s support portal is login-protected and shows tickets — and only tickets, so email or chat conversations never converted to tickets won’t appear. There is no per-external-user charge, but it requires Service Hub Professional ($90/seat/month annual, plus a $1,500 one-time onboarding fee) or Enterprise.

Can NetSuite really give unlimited customers portal access for free? The Customer Center role is free to assign and unlimited for B2B customers, covering cases, order and quote history, invoice viewing and payment, and return authorizations. Expect to invest in workflow automation around it — native NetSuite often leaves payment posting and case routing partly manual.

How do we know whether an AI service agent will pay for itself? Divide your fully loaded support cost by tickets handled, then compare to $0.50 per resolved conversation (HubSpot Breeze Customer Agent) or $2 per resolved case (Salesforce Help Agent), multiplied by a conservative containment assumption. Run the model again after a 60-day pilot with real containment data.

Which Zoho Desk edition do we need for a real self-service portal? Knowledge base, community, and the ASAP self-service widget start at Standard. Answer Bot is Standard and above, Zia is Professional and above, and multi-brand Help Center plus Guided Conversations are Enterprise only. AI Agents are available from Express with up to 30 million free tokens per month.

What’s the fastest first move if we already have a portal nobody uses? Audit which articles are registered-user-only, move everything that isn’t account-specific to public, confirm article-level search indexing is actually enabled, and start logging escalation reasons. That sequence usually takes two to three weeks and costs nothing in licensing.

Conclusion

Self-service isn’t failing because customers dislike it — 73% of them use it. It is failing because the commercial structure of CRM portals pushes knowledge behind a metered login, at exactly the moment when half of all service journeys begin on a platform that can only see what’s public. The fix is architectural and it is available on every platform discussed here: make general knowledge free, open, and machine-readable; reserve authenticated, licensed access for the handful of things that genuinely require identity; and only then layer an AI agent on top, where it has something solid to stand on.

If you’re budgeting a portal project, renewing Experience Cloud licenses, weighing a Service Hub tier jump, or trying to decide whether your NetSuite Customer Center can carry real self-service volume, we can model the license economics and the content architecture together before you commit. Schedule a consultation with CRM Experts Online and bring twelve months of ticket data — that’s where the real answer is.

Further Reading