A login helps when a customer needs to come back. If the relationship is a single transaction, asking someone to create an account adds a step, a password to forget and a reason to give up.
The test is repetition. Will this person return to check, download, approve or update something more than once? If yes, a portal starts to earn its place. If no, email and a well made web page will serve them better.
Where portals genuinely help
- Repeated status checks, where customers otherwise ring or email to ask where something is.
- Documents that need to be available again later, such as statements, certificates or reports.
- Approvals, where a record of who agreed to what and when actually matters.
- Account specific information that differs per customer and changes over time.
- Recurring interactions such as ordering, booking or submitting the same kind of request.
- Information too sensitive to sit in an email thread indefinitely.
The common thread is that the information has a life beyond one message. Email is a conversation. A portal is a place.
Where email is simply better
- A one off enquiry, quote or purchase.
- Anything a customer would forward to a colleague.
- Short notifications that need no action beyond reading.
- Situations where the audience will not tolerate a login and does not need one.
The hidden cost of accounts
A login is not a screen. It is registration, verification, password reset, session handling, access control, an audit trail, a support route for people locked out, and a responsibility for whatever personal data sits behind it. None of that is exotic, but all of it is real work that continues after launch.
Before committing, decide who can see what. Who is a user, who is an account, and what happens when someone leaves the customer organisation? Permission questions asked at the start are cheap. Asked afterwards, they tend to require rework.
What belongs inside
Put in the things a customer would otherwise ask a person for: current status, history, documents, the details of their own account, and the actions they are allowed to take themselves.
Leave out anything that is simply your internal system with a customer coat on. A portal should answer the questions customers ask, not expose every field your operation happens to hold.
A middle path
Between public page and full account sits a useful option: a private link sent to a known recipient, showing one record such as a job, quote or order, with no password. It suits short lived information and removes almost all of the account overhead.
It is not appropriate for anything genuinely sensitive, since a link can be forwarded, and the link should expire. Used with judgement, it answers a surprising proportion of portal requests.
How to decide
- Count how many times a typical customer would return in a year.
- List the questions they currently ask your team by phone or email.
- Ask which of those questions can be answered from data you already hold reliably.
- Check whether the information is sensitive enough to require authentication.
- Consider whether a private link or a better email would remove most of the demand.
If the honest answer is that customers would log in twice a year to look at something you could have emailed them, build the email properly and keep the portal on the shelf.