Customer portal
A customer portal is a secure, logged-in web application where an organisation's customers view their own records and complete transactions themselves, instead of emailing or phoning staff to do it for them. Unlike a website, every action a customer takes writes back into the business's own systems.
Also known as: Client portal, Web portal, Self-service portal
Last reviewed
Why a customer portal matters
A portal exists to remove a manual back-and-forth. Before one, a customer who wants an order status, a copy of an invoice or a change to their details sends a message, and a member of staff reads it, looks something up and replies. That round trip costs your time and theirs, and it caps how many customers each person can serve.
A portal converts those requests into self-service. The commercial case is usually built from the volume of repetitive inbound messages rather than from the software itself, which is why scoping a portal starts with a week of your own inbox rather than with a feature list.
How a customer portal works
Four things sit behind every portal. Authentication proves who the customer is, normally with multi-factor authentication and often single sign-on against their own identity provider. Permissions decide what that person may see — a head-office user might see every site while a site manager sees one. Integration reads and writes your existing CRM, ERP or job-management system, so nothing has to be re-entered. Notifications give the customer a reason to return.
Of the four, integration is the one that decides whether the portal reduces work or duplicates it. A portal that cannot write into your systems simply moves the typing from the customer to your staff.
Customer portal vs website
A website is public and tells people about your business. A customer portal sits behind a login, shows each customer only their own data, and lets them act on it. The distinction is transactional, not visual.
The test is whether anything changes in your systems when a customer uses it. A logged-in area that only holds PDFs someone uploads by hand each month is a document store with a password, not a portal — a useful thing, but it will not reduce anyone's workload.
When you need one
Consider a portal when a small number of question types account for most of your inbound contact, when customers ask for status information you already hold, or when your partners and resellers need different views of the same data. Each of those is work a portal can take off your team permanently rather than temporarily.
It is rarely the right first project if your underlying data is scattered or unreliable. A portal publishes your data to the people least willing to tolerate errors in it, so poor data quality becomes a customer-facing problem rather than an internal one. Fix the records first, then expose them.
Customer portal: common questions
Nothing meaningful — they are the same thing under different names, and which you use tends to follow your industry. Professional services usually say client portal; product and logistics businesses say customer portal. Partner portal and reseller portal describe the same pattern serving other businesses rather than end customers.
Almost always. Without integration, whatever a customer submits has to be re-entered by a member of staff, so the portal adds work rather than removing it. Integration usually accounts for more of a portal build than the screens do, and it is the part most often underestimated.
In our projects portals are built in fixed two-week sprints, with most aiming to launch a usable first version within 2 to 8 weeks, typically across 2 to 4 sprints. Scoping comes first and normally adds a few weeks before any build starts.
Want to talk about your project?
Tell us what you’re trying to achieve and we’ll map the fastest credible path.