Set up a portal and clients still email you? These nine client portal mistakes explain why, with a simple fix for each one.
Edin Abazi9 min read
On this page
Most client portal mistakes come down to one thing: the portal gets built, but email keeps running as the real system. Clients go where the work already happens, so a portal only works if it's easier than sending an email. Here are the nine mistakes small agencies make most often, and how to fix each one.
The short answer: a client portal fails when it adds a place to check instead of removing one. Fix that, and most of the other problems follow.
Why a Built Portal Still Goes Unused
A portal that exists is not the same as a portal that clients use. As one widely shared post on the problem puts it, you can invest in a client portal and your clients still never log in.
CloudRadial makes a related point: the portal exists, but the experience doesn't. It becomes another place someone has to keep updated, instead of the place that keeps them updated.
Small agencies feel this more than large ones. You don't have a dedicated account manager to nudge clients into the portal, so every design choice has to do that work for you.
Practitioners ask about this constantly. Threads like this one on r/Bookkeeping and this one on r/business show people trying to streamline client communication and process flow, and wondering whether portals actually help.
The nine mistakes below are the usual reasons they don't.
How to read this list
Each mistake has a short description of what goes wrong, a realistic example, and a fix you can do this week. The examples are hypothetical, not customer stories.
Mistakes 1 to 3: Making the Portal Hard to Start Using
The first three mistakes happen before a client submits anything. They decide whether the first visit feels easy or like homework.
1. Offering too many request types
A form with fifteen request categories makes clients stop and think. LinkedIn's roundup of common portal frustrations lists cognitive overload from too many options as a recurring complaint.
For example, a five-person design studio might list "Brand refresh", "Logo tweak", "Social graphic", "Social carousel", "Banner" and ten more. The client opens it, gets confused, and emails "Can you make a banner?" instead.
Fix: start with three to five request types that match how clients actually ask. Add more only when a type shows up repeatedly. Let clients describe the rest in plain words and let the brief step ask for what's missing.
2. Opening to a cluttered first screen
If the portal opens to menus, folders, and widgets, clients won't know where to click. CasePulse's guidance for law firm portals says the first screen should show current status and next steps, not clutter.
Fix: make the landing view answer two questions: what's waiting on me, and what's in progress. Everything else can sit one click away.
3. Asking clients to create another password
Every login step loses some clients. A client who can't remember a password will go back to email, and you've lost the habit before it formed.
Fix: use sign-in by email link. In Dora, clients sign in with an email link and can reply from their inbox, so the branded client portal never feels like a gate.
Mistakes 4 to 6: Running Email as a Second System
This is the mistake that matters most. If email still works for everything, clients will keep using it, and your team will keep copying things between two places.
4. Leaving email running as a parallel system
The point of view here is simple: don't ask clients to stop emailing you. Make email feed the portal. Telling clients to "please use the portal" creates friction for them and a favor you have to keep asking for.
The trade-off is that clients keep their old habit. The benefit is that nothing falls outside the system.
Fix: give each client a dedicated address that turns messages into requests. Dora's email intake does this, and Dora versus email walks through what changes when you stop running clients from your inbox.
5. Letting records drift between systems
Moxo notes that when a portal and other records diverge, you risk data mismatch, lost records, and duplicate entries. In an agency, this looks like the brief in the portal saying one thing and the Slack thread saying another.
Fix: pick one place where the current version of a request lives. Everything else points to it.
6. Ignoring how the portal fits your other tools
ClickDo lists integration with other business systems as a common implementation pitfall. A portal that doesn't connect to how your team actually works becomes extra admin.
Be honest about the split. A tool like ClickUp is better for planning your team's internal work. The portal should handle the client-facing side: requests, files, approvals.
Fix: decide what the portal owns and what stays in your internal tools. Write it down in one sentence.
A Three-Step Audit to Find Your Leak
Before fixing anything, find where work still escapes the portal. This simple three-step audit takes about an hour.
Count the channels. Look at the last 20 client messages. Note how many arrived by email, chat, call, or portal.
Trace each one. For each message, ask whether it ended up as a request with a brief and a thread.
Name the leak. Group the misses. Usually two or three causes explain most of them.
Mini example: the scattered feedback
Baseline: a studio gets feedback on one landing page from an email, a Slack DM, a PDF comment, and a call. Two notes contradict each other.
Intervention: all feedback goes to one thread per request, and email replies land there automatically.
Expected outcome: one source of truth and fewer conflicting revisions. Measure it over four weeks by counting revision rounds per request before and after.
An action checklist for this week
Cut your request types to five or fewer.
Rewrite the portal's first screen to show only what's waiting and what's in progress.
Turn on email-to-request for every active client.
Tell clients they can keep emailing.
Pick one home for the current brief on each request.
Mistakes 7 to 9: Skipping the Parts That Keep Work Moving
The last three mistakes show up after the portal is live. They're why a portal looks fine in week one and gets ignored by month three.
7. Collecting requests without writing a brief
A portal that only stores requests moves the vague email into a form. "Can we freshen up the homepage?" is still vague in a text box.
For example, a designer ships a new hero when the client meant the copy. A brief first, covering which section, the goal, references, and the deadline, gets the first version right.
Fix: ask for what's missing before work starts. Dora, the AI account manager, asks for what's missing and writes the brief, and every suggested change waits for a person's click. Our guide on creative briefs clients will fill in covers the questions worth asking.
8. Having no plan for quiet clients
Work sits "in review" for two weeks and nobody wants to nag. This is the silent client problem, and a portal alone doesn't solve it.
Fix: make approval a one-click action and set a rule for silence. With one-click approvals, quiet clients' work approves itself after the days you choose. Our client approval process guide explains how to pick a sensible window.
9. Not showing clients what's happening
If clients can't see status, they email "Any update on this?" three times a week. The portal then feels like extra work with no payoff.
Fix: show what's waiting on whom, and send a summary so clients don't have to look. Weekly summaries do that, and a monthly recap also answers the renewal question: what did we get for our retainer?
Common Pitfalls When You Fix These
Fixing a mistake can create a new one. Watch for these.
Over-correcting on forms. Cutting request types is good. Cutting the questions that make a brief useful is not.
Forcing a switch. A hard deadline for "portal only" tends to push clients back to email, quietly.
Hiding trust signals. Digitalist's overview of portal headaches covers security and trust as a common concern. Be plain with clients about how their files are handled. Dora doesn't train on customer content.
Skipping a measurement plan. Pick a baseline, like the share of requests that arrive by email without a brief. Set a target, such as halving it in six weeks. Check it every Friday.
Slow document collection and repetitive requests are the problems portals exist to solve, as Uku describes for accounting firms. If your portal isn't reducing them, one of the nine mistakes is probably the reason.
What to expect from Dora on cost
Your first client is free, forever. Each client after that is $10 a month, with unlimited team seats and every feature included. That makes it cheap to test these fixes on one client before rolling them out. See Dora pricing for details.
If you want to see how these fixes work in practice, try Dora with your first client or book a demo and bring your messiest client request.
FAQ
Why don't my clients use the client portal?
Usually because email is still easier. Too many request types, a cluttered first screen, and extra logins all push clients back to their inbox. Make the portal the path of least effort and let email feed into it.
How many request types should a portal have?
Start with three to five that match how clients actually ask. Add a new one only when the same kind of request keeps coming up. Fewer choices reduce the overload clients report in portal frustration roundups.
Should I make clients stop emailing me?
No. Turn email into requests instead, so clients keep their habit and nothing falls outside your system. Pushing a hard switch often creates resistance.
How do I handle clients who never approve work?
Make approval one click and set an automatic approval window. For example, work that sits for 7 days approves itself. Tell clients about the rule up front so it isn't a surprise.
How do I know if my portal is working?
Track the share of requests that arrive with a complete brief, the number of status emails per week, and revision rounds per request. Take a baseline now, then compare after four to six weeks.
References
Questions
Usually because email is still easier. Too many request types, a cluttered first screen, and extra logins all push clients back to their inbox. Make the portal the path of least effort and let email feed into it.
Start with three to five that match how clients actually ask. Add a new one only when the same kind of request keeps coming up.
No. Turn email into requests instead, so clients keep their habit and nothing falls outside your system. A hard switch often creates resistance.
Make approval one click and set an automatic approval window, such as 7 days. Tell clients about the rule up front so it isn't a surprise.
Track the share of requests with a complete brief, status emails per week, and revision rounds per request. Take a baseline now and compare after four to six weeks.
Sources