Customer portals, employee portals and partner portals promise self-service: fewer emails, fewer calls, faster answers. Many deliver the opposite. People cannot find what they need, give up and pick up the phone — and the organisation now maintains a portal and a support queue.
The difference between a portal people use and one they avoid rarely comes down to technology. It comes down to a handful of design decisions.
Design around top tasks
Every audience visits a portal for a small number of reasons. A customer may want to check an order, download an invoice or log a request. An employee may want to view a payslip, apply for leave or find a policy. Identify these top tasks through support logs, interviews and analytics, then make them the most prominent things on the page.
Show status, not just forms
Many support calls are simply people asking “where is my request?”. Showing clear status — submitted, in review, approved, completed — with dates and next steps removes that uncertainty. It is often the single most effective feature for reducing follow-up contact.
Make access simple and secure
- Use single sign-on for employees where possible, so there is no extra password to remember.
- Keep registration for external users short, and explain why each piece of information is needed.
- Apply role-based permissions so each person sees only what is relevant to them.
- Make password resets self-service and quick.
Write for the person, not the organisation
Internal terminology leaks into portals easily: department names, system codes, process jargon. Use the words your audience uses. Test labels with real users — if they hesitate before clicking, the label is not clear enough.
Design for mobile from the start
Many people will reach your portal on a phone, particularly frontline employees and customers on the move. Design the top tasks to work comfortably on a small screen first, then expand for larger screens.
Plan for ownership after launch
Portals decay when documents go out of date and nobody is responsible for them. Assign content owners for each section, set review dates, and monitor search terms and drop-off points to see where people are getting stuck.