The Case of the 'Client Portal' That Became a Support Desk
We built a portal to save time. We ended up spending all our time resetting passwords. Here is why 'Self-Service' is often a trap.
The “Forgot Password” Strategy
I once worked with an agency that spent £50,000 building a bespoke Client Portal. It was slick. It had dark mode. It had animated transitions. It was the pride of the technical director.
Three months after launch, I looked at the usage logs.
- Logins by Agency Staff: 450
- Logins by Client: 3
The only time the client interacted with the portal was to email us: “Hi, I can’t remember my login, can you just attach the PDF?”
It was dodgy. We had built a tool for ourselves, not for them. We wanted to feel high-tech. The client just wanted to know if the campaign was working.
By forcing them to log in, we had introduced a “Tax” on the relationship. Every time they wanted to know the answer, they had to pay the tax: find the URL, remember the password, navigate the menu.
Eventually, they stop paying the tax. They stop looking. And when they stop looking, they stop valuing your work.
The Drag: The “Self-Service” Myth
“Self-Service” is a lie we tell ourselves to save work. We think, “If I put the data there, they can answer their own questions, and I won’t get bothered.”
This is rubbish. Clients pay you fees specifically so they don’t have to answer their own questions. They are paying for your brain, not your database.
When you push a portal, you are essentially saying: “Here are the ingredients; cook your own dinner.” A busy executive doesn’t want to cook. They want the meal plated up.
The drag on the team was immense. Instead of analyzing data, my account managers were acting like a Help Desk. “Click the top right icon.” “No, the other top right.” “Try clearing your cache.”
This is not consulting. This is tech support. And nobody pays premium rates for tech support.
The Answer: The “Zero-Login” Policy
We made a radical change. We kept the portal for the analysts (the warehouse), but for the decision-makers, we switched to Push Delivery.
We summarized the key insights into the body of an email. Not an attachment. The body text.
- Subject: Oct Results: CPA down 10% (Target Hit)
- Body:
- Good News: We hit the CPA target due to the new creative.
- Bad News: Volume is slightly capped.
- Action: We need approval to expand the audience.
- Attachment: The full PDF for the archives.
[TO EDITOR: Illustration showing a “Wall” vs a “Door”. Image 1: A client standing in front of a locked door labeled “Client Portal”. They look frustrated. Image 2: An open letter labeled “Email Summary” with the key stats visible. The client looks happy.]
The response was immediate. “Thanks, Oliver. Sorted.”
The support tickets vanished. The strategic conversations returned. We realized that the most “user-friendly” interface in the world is not a dashboard; it is an email that tells you exactly what you need to know without making you click anything.
If you want to be indispensable, don’t build a maze. Build a bridge.
FAQs
But don't clients expect a portal these days?
They expect the *answer*. They don't care if it comes via a portal, a pigeon, or a PDF. The medium is less important than the message.
Portals are more secure than email, aren't they?
Theoretically. But if the client never logs in because it's too hard, the data is perfectly secure because nobody is looking at it.
How do I wean them off the portal?
Start sending the 'Executive Summary' via email. They will stop logging in naturally because you gave them the gold upfront.