Self-Service
Self-Service (the Self-Service Portal) was a retired Salesforce feature that gave customers a branded web page where they could log support cases, check the status of cases they already raised, and search public Solutions for answers, all without contacting an agent.
Definition
Self-Service (the Self-Service Portal) was a retired Salesforce feature that gave customers a branded web page where they could log support cases, check the status of cases they already raised, and search public Solutions for answers, all without contacting an agent. It was one of Salesforce's earliest customer-facing channels and was part of Service Cloud's original support toolset.
The feature is retired. Starting with the Spring '12 release, the Self-Service Portal stopped being available to new Salesforce orgs. Organizations created after that point had to use the Customer Portal with Salesforce Knowledge instead, and today the recommended way to deliver self-service is an Experience Cloud site. Existing orgs that turned it on before Spring '12 kept access, but no new setup is possible.
From Self-Service Portal to Experience Cloud
What the Self-Service Portal actually did
The Self-Service Portal was an online support channel that let customers resolve questions on their own. After an admin enabled it, customers got a login to a Salesforce-hosted page tied to the company's org. From there they could submit a new case, view the cases they had already opened, add comments to keep a case moving, and search a library of published answers. Those answers came from Solutions, the original Salesforce knowledge feature that predated Salesforce Knowledge. The portal removed the need for a phone call or an email for common, repetitive questions. It worked closely with the Case object, so anything a customer logged became a normal case that agents handled inside Salesforce. Self-Service users were a distinct user type, not full Salesforce licenses, and admins managed them from a single screen with bulk edit support. The look of the pages could be branded with fonts, colors, and custom logos so the portal felt like part of the company's own website rather than a generic Salesforce screen.
Why Salesforce retired it
The Self-Service Portal carried real limits that newer options removed. The biggest one was data. Self-Service could only show standard support records like cases and Solutions. It could not expose custom objects, so a company that tracked orders, assets, or subscriptions in custom objects had no way to surface that data to customers. The portal also relied on Solutions rather than Salesforce Knowledge, which meant no article types, no data categories, and weaker search. Branding was limited to fonts and colors on a fixed page layout, so the experience always looked dated next to a modern website. As Salesforce built the Customer Portal and then Communities, those products supported custom objects, richer Salesforce Knowledge, and far more control over layout and access. Keeping a second, weaker portal made little sense. So Salesforce closed Self-Service to new orgs in Spring '12 and pointed customers at the Customer Portal plus Salesforce Knowledge. Existing portals kept working, which is why some long-running orgs still reference Self-Service today even though no one can stand up a new one.
What replaced it: Customer Portal, then Experience Cloud
The replacement path runs through two products. First came the Customer Portal, the direct successor that new orgs had to use after Spring '12. The Customer Portal could show custom objects, used Salesforce Knowledge instead of Solutions, and gave admins more control over which records a customer could see. It paired self-service with the security model that already governed internal users. The Customer Portal itself later folded into Communities, which Salesforce now markets as Experience Cloud. Experience Cloud sites are the current answer for customer self-service. They are built with Lightning templates such as the Help Center, Customer Service, and Customer Account Portal, and they support Salesforce Knowledge, case management, contact requests, and Q&A in one place. A company moving off the legacy portal would rebuild the experience as an Experience Cloud site, map the old case and Solutions data into Knowledge, and migrate Self-Service users to community user licenses. The concept of letting customers help themselves never went away. Only the implementation changed.
How it connected to cases and Solutions
Self-Service was tightly wired to two parts of Service Cloud. Cases were the spine. Every question a customer submitted through the portal created a case, which routed into the same queues and assignment rules agents used for phone and email. Customers could reopen the portal later to read agent replies and post a follow-up comment, so a single case thread spanned both sides. Solutions were the knowledge side. Admins marked certain Solutions as public, and those public Solutions appeared in the portal's searchable answer library. A good Solution could deflect a case entirely, because a customer found the fix before logging anything. This pairing of case logging with searchable answers is the same pattern modern self-service still uses, just with Salesforce Knowledge articles instead of Solutions and an Experience Cloud site instead of the fixed portal. Admins could start fast with a Jump Start option that applied default settings, or run the full Self-Service setup to control branding, page content, user management, and the login HTML they embedded on their own website.
Recognizing legacy Self-Service in an existing org
Because Salesforce left existing portals in place, an admin inheriting an older org may still find Self-Service active. Signs include a Self-Service Portal section under Setup, a population of Self-Service user records that are not standard Salesforce or community users, and public Solutions configured for portal display. Login HTML pointing at a Salesforce self-service endpoint embedded in the company website is another tell. If you find this, treat it as technical debt rather than something to extend. You cannot create a new Self-Service Portal, and Solutions is itself a legacy feature that Salesforce no longer recommends. The right move is to plan a migration to an Experience Cloud site, convert public Solutions into Salesforce Knowledge articles, and move customer logins to community user licenses. Document the old setup first so you do not lose the list of who had access and which Solutions were public. A clean cutover keeps customers from losing their case history during the move.
Why the self-service idea still matters
The product is gone, but the strategy it represented is now a core part of how teams run support. Self-service lets customers answer their own questions at any hour, which lowers case volume and frees agents for harder work. Salesforce calls the win from this case deflection, and it is one of the main reasons companies invest in an Experience Cloud site, a Help Center, and a well-tended Salesforce Knowledge base. The Self-Service Portal proved the model early: give customers a way to log a case and search answers without waiting in a queue. Modern tools add features the original never had, like AI-suggested articles, chatbots, and the ability to show order and asset data from custom objects. When you read older Salesforce documentation or certification material that mentions the Self-Service Portal, read it as the historical root of today's self-service stack. The vocabulary moved from Solutions to Knowledge and from portal to site, but the goal of deflecting routine questions stayed the same.
Trust & references
Cross-checked against the following references.
- Set Up Your Self-Service PortalSalesforce
- Provide Self-Service in an Experience Cloud SiteSalesforce
Straight from the source - Salesforce's reference material on Self-Service.
- Set Up Your Self-Service PortalSalesforce
- Self-Service Portal Implementation GuideSalesforce
Hands-on resources to go deeper on Self-Service.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What was the legacy Salesforce Self-Service portal designed to let customers do?
Q2. Which modern Salesforce platform replaces the retired Self-Service portal?
Q3. Is the broader self-service strategy still important even after the Self-Service portal was retired?
Discussion
Loading discussion…