The short answer
Look at what your team spends time answering. Order status, invoice copies, delivery dates, document uploads. A portal that handles the top few, reliably, earns its place. Breadth without depth does not get adopted.
The measure of success is a fall in routine contact, not the number of features shipped.
Start from the phone calls
- Log what people actually contact you about for a fortnight.
- Group it and count.
- Take the top three that have a factual answer.
- Build those properly, including the awkward cases.
- Measure whether contact about them falls.
This is unglamorous and it beats a requirements workshop. The calls tell you what people want, without anyone having to imagine it.
What belongs in a portal
| Good fit | Poor fit |
|---|---|
| Status of something they care about | Anything needing negotiation |
| Documents they need copies of | Exceptions with no clear rule |
| Submitting a request or upload | First-time onboarding, usually |
| Updating their own details | Complaints and disputes |
| Self-serve reporting on their own data | Anything emotionally charged |
The right column is not a limitation to fix. Some things are better handled by a person, and routing them to a human quickly is a feature.
Access control comes first
A portal exposes your data to people outside your organisation. Who can see what is the first design decision, not a late one.
- One login per person, not one shared per company
- Roles, so an accounts contact and a site manager see different things
- A clear rule for what a user can see across a company's records
- An audit trail of who saw and changed what
- A way for the customer to manage their own users, or a process for you to
Shared company logins are the common shortcut and they remove accountability entirely. When someone leaves that company, you have no way to revoke only their access.
Why adoption fails
Usually because the portal is slower than emailing you. If finding an invoice takes four clicks and a password reset, people will email, and the portal becomes a cost with no saving.
Log in without a password reset, find the top task in one or two clicks, and make it work on a phone. Those three decide adoption more than the feature list.
Keep one door open
Always leave a route to a person, clearly. A portal that traps people in a self-service loop damages the relationship it was meant to improve.
The goal is to remove routine contact so your team has time for the contact that matters, not to remove contact altogether.