How do you design a self-service customer portal?

Self-service portal = customers find answers themselves rather than calling support. Right design saves money and improves experience; wrong design frustrates.

Capabilities to include:

1. Knowledge base — searchable articles answering common questions.
2. Case submission — form for issues that need human help.
3. Case status tracking — customer sees their open cases.
4. Account management — update contact info, password, preferences.
5. Community / forum — peer-to-peer help; community-driven Q&A.
6. Order / subscription history — for B2C / SaaS, customers manage subscriptions.
7. Documents — invoices, contracts, statements.
8. Chatbot — Einstein Bots for common queries; handoff to live agent if needed.

Architecture:

• Experience Cloud (formerly Communities) is the foundation.
• Customer Community / Plus license for portal users.
• LWR template for modern, fast, SEO-friendly site (vs older Tabs templates).
• Knowledge integration — articles surface based on user's question; data categories drive filtering.
• Authentication: SSO (OAuth/SAML) or Salesforce-managed login.
• Sharing model — Sharing Sets for HVPU users; case visibility filtered to user's own cases (or their account's cases for Community Plus).

Design considerations:

• Simple navigation — most users want to find an answer fast.
• Search-first — prominent search; Einstein Search for natural-language queries.
• Mobile-responsive — many users on phones.
• Branding — match the company brand, not Salesforce default.
• Accessibility — WCAG 2.1 compliance.

Metrics:

• Case deflection — % of would-be cases solved by self-service.
• Article views vs case creation — high views, low cases = good deflection.
• Search queries with no results — surface gaps in content.
• Bounce rate — users who land and leave immediately.
• CSAT for self-service paths.

Common pitfalls:

• Empty or poor knowledge base — portal launches with 10 articles. Customers can't find answers; portal feels useless.
• Over-restricted login flow — too many auth steps deter use.
• Branded but unhelpful — looks great, doesn't solve problems.
• No analytics — don't know if it's working.

A self-service portal succeeds when case volume drops while customer satisfaction rises — both metrics together.