Support fielding questions a portal could answer once
Partners and dealers ordering by email
Members or clients with nowhere to self-serve
A community that was built and then abandoned
The best portal answers a question your team never hears about.
Experience Cloud portals for customers, partners and members: self-service, case deflection, document access, account hierarchy and partner enablement.
Customers, partners and members phone in to ask things the system already knows. Every one of those calls is somebody on your side reading a screen aloud. The cost is not the call itself, it is that your team quietly becomes the search interface for your own data, and nobody can see the queue of questions forming behind it.
So we scope the portal around the handful of things people genuinely log in to do, and we build it small enough that your team can run it without us. A portal nobody adopts is worse than no portal at all, and the usual reason for that is a login that asks more effort of someone than just picking up the phone.
Where it breaks
Order history, invoices, open requests, what was installed and when — all of it exists, and none of it is reachable without asking someone.
Distributors and dealers send orders as attachments that somebody re-keys, with no visibility of stock, pricing or status in between.
Contracts, drawings, statements and reports scattered across drives and inboxes, so the answer to where is that depends on who you ask.
New partners, members or clients are set up by hand, and every step that is forgotten becomes a support case later.
Built once, never maintained, and now the thing everyone points at when portals come up.
No practical way to give one person a narrow view, so people are either locked out or shown too much.
What we build
Nine portal problems we keep being handed, roughly in the order they have to be solved.
The line item on every portal we have built: profiles, permission sets and sharing so each outside organization sees only its own records, with internal fields such as margin and internal notes invisible rather than merely hidden.
Branding sets, theme layouts, navigation and button styling, plus custom login, forgot-password, profile and 404 pages with the Salesforce furniture removed, so the portal reads as the client’s own property.
Letting outside users act rather than look: updating purchase orders and lines in a guided modal, ordering by building, floor, unit and room, running an event and booking lifecycle, or placing an order on a customer’s behalf.
Customers opening, tracking and closing their own cases, seeing the history for their whole organization, reading published articles, and getting notified at every status change, replacing an email queue nobody could report on.
Customers maintaining their own contacts and details, adding and removing their own users, adjusting access levels without a support call, and getting prompted when their information has gone stale.
The portal work we are proudest of: giving partner coordinators the dispatch console inside the portal to schedule their own technicians, with accept and reject on an expiry clock that reroutes to the next partner on silence.
Reusable related-list and share components, inline line editors, find-or-create widgets and flow plugins, built when the standard component gets close but not close enough.
Registration gated to validated business domains where access rules are strict, profile assignment at the moment of sign-up, welcome and reset templates, and onboarding steps that fire on day one.
A portal is rarely a standalone deliverable. The useful ones read from and write to the ERP, so a customer sees their real order, their real invoice and their real balance.
Beyond phase one
Each one came out of delivery work rather than a product roadmap. In most cases the client did not know to ask for it.
A portal is usually judged on logins. The better measure is the call that did not happen, which means tagging the case types you intended to deflect and watching whether their volume actually falls.
Real customers sit on two boards, own three properties or buy for two divisions. Modelling that before launch is routine. Retrofitting it after a thousand accounts have registered is not.
Sharing that follows the account hierarchy rather than a folder structure. It is the difference between a portal your legal team tolerates and one they trust.
If every copy change needs a deployment, the portal goes stale in a quarter. Put the text, the banners and the link lists somewhere an administrator can edit without raising a ticket.
When somebody gives up and clicks contact us, everything they already typed should travel with them. Most portals throw it away and make the agent start the conversation from nothing.
Integrations
The value is not the pages. It is what those pages can reach. These are the categories we most often connect behind a portal.
Live order, stock and pricing information rather than a nightly export.
Invoices, statements and card payment handled inside the login, securely.
Drawings, contracts and reports reachable from the record they belong to.
Single sign-on against the directory your users already have.
Dues, registrations and attendance for member organizations.
Job status and history visible to the customer whose site it happened on.
Community Cloud · Knowledge · Order Management · SSO
Eighteen university partners exchanging participant data through spreadsheets, with state funding compliance riding on it. An Experience Cloud community portal replaced the spreadsheets with secure, structured sharing the nonprofit staff can administer themselves.
Experience Cloud · Sales Cloud · Einstein Activity Capture
Community Cloud · Sales Cloud · Syspro ERP
They are almost always things the customer could have answered themselves if a portal let them. That list is your requirements document, and it is already written.
