Guide

Almost every firm we talk to has a client portal. Almost every firm we talk to also has a mailbox full of tax documents that arrived as email attachments. The portal exists, the clients were told about it, and the documents came by email anyway.

The usual explanation is that clients are not technical. It is a comfortable explanation because it puts the problem outside the firm. It is also, in our experience, wrong. The same client who "cannot manage a portal" moves money in a banking app, checks a flight status, and uploads a photo of a check to deposit it. What they will not do is spend eleven minutes solving a password problem in order to send you a W-2 that would take forty seconds to attach to an email.

Adoption is a friction problem. Below are the five sources of friction that matter most, roughly in order of how much they move the number.

What we cover

  • The first-login cliff, and why most portals lose people there
  • Asking for "your documents" versus asking for a specific thing
  • What the client sees when they land — and why less is more
  • The email that arrives when the firm sends a message
  • The firm's own back door, and why it has to close

1. The first login is where most portals lose the client

Count the steps between "I got an email from my accountant" and "my document is uploaded". In a lot of deployments it looks like this: open the invitation email, click a link, create a password meeting rules you are told about only after failing them twice, confirm the email address by finding a second message, sign in again, set up two-factor authentication, scan a QR code with an app you have to install first, enter a code, land on a dashboard, find the upload area, choose a category from a dropdown you do not understand, and upload.

That is thirteen steps, three of which can fail silently, one of which requires installing software. And critically, the client is doing all of it before they have received any value from the system. They are paying the entire setup cost up front for a benefit they have not yet seen.

You cannot remove all of that — 2FA on an account holding tax documents is not negotiable, and we would argue with anyone who says otherwise. But you can change where it sits and how it feels:

  • Make the setup guided and visibly finite. A three-step flow with a progress indicator reads as a task. The same three steps without one read as an unbounded process, and people abandon unbounded processes.
  • Put a copyable setup key next to the QR code. A meaningful share of first-time users are reading the email on the phone that is supposed to scan the code. Without a copy-paste path, they are stuck.
  • Tell them the password rules before they type. Not after the first rejection, and certainly not one rule per rejection.
  • Let them land on something with their name on it. If the first screen after setup shows their documents and their deadlines rather than an empty state, the cost they just paid feels bought rather than spent.

Worth measuring

Invitations sent versus accounts activated, and activation versus first upload. If the first number is healthy and the second is not, your problem is the setup flow. If both are healthy and usage still dies, your problem is further down this list.

2. "Please upload your documents" is not a request

It is an assignment with no definition of done. The client does not know what counts, whether they have everything, or whether the thing they are missing is the thing you are waiting on. So they wait until they are sure they have all of it — which for many people means they wait indefinitely, then send everything by email in one panicked batch in April.

A tracked document request changes the shape of the interaction. Instead of an open-ended ask, the client sees a list: W-2 from employer, 1099-INT from the bank, mortgage interest statement, prior-year return. Each line has a state. They can send three now and the fourth next week, and both sides can see exactly what is outstanding without anyone having to ask.

This is the single highest-leverage change on this list for most firms, because it fixes both sides at once. The client stops guessing. Your staff stop reconstructing what has been received from a mailbox.

3. Show the client their own three things, not your twelve

A portal dashboard built by a software vendor tends to show everything the system can do. A portal dashboard built for a client should show what they need to act on, and very little else.

In practice that is a short list: what needs your attention, what is new from the firm, what is coming up. Unread messages, documents awaiting review, outstanding requests, the next deadline. Everything else — full history, the resource library, the calendar, their organization profile — should exist, and should be one click away, and should not be competing for attention on the landing screen.

The instinct to surface more is understandable. You built a lot; you want it seen. But every element on that first screen is a small tax on the client's ability to find the one thing they came for, and the clients whose adoption you are trying to win are precisely the ones with the least patience for it.

4. The notification email decides whether they come back

Almost nobody logs into a client portal spontaneously. They come back because something told them to. That something is an email, which means the email is doing more work than the portal in determining whether the portal gets used.

Two rules, and they pull against each other slightly:

  • Say enough that the client knows why they should click. "You have a new message from your accountant" is fine. "You have a notification" is not — it is indistinguishable from every other automated email they ignore.
  • Do not put the content in the email. If the message body arrives in the email, the client has no reason to log in, and will reply by email, and you are back where you started with a conversation split across two systems. Notify, summarize, link — do not deliver.

The other thing that matters here is the sender. An email from your firm's name, with your logo, from an address at your domain, gets opened. An email from a software vendor the client has never heard of gets filed as spam — sometimes literally, by a filter, and then you have an adoption problem you cannot even see.

5. Close the firm's own back door

This is the one nobody wants to hear, and it is usually the reason the other four did not work.

If a client emails a document and someone at the firm processes it, the portal is optional. If the portal is optional, the clients who find it marginally harder than email will use email, and that is most of them. Every time a staff member accepts an emailed document to be helpful, they teach that client that the portal is decorative — and they do it far more persuasively than any onboarding message teaches the opposite.

We are not suggesting you bounce a client's email in filing season. That is a good way to lose a client over a process preference. What works is narrower and less confrontational:

  • Accept the document, then upload it to the portal on the client's behalf, and reply from the portal. The next message in the thread is now in the right place.
  • Make "upload on behalf of the client" a two-click action for staff. If it is tedious, it will not happen, and the exception becomes permanent.
  • Set the expectation at engagement, not at deadline. A sentence in the engagement letter costs nothing and does more than a reminder in March.
  • Watch for the staff member who is quietly running a parallel process because they find it faster. They usually have a legitimate complaint about the tool underneath it — go find out what it is.

The uncomfortable version

Portal adoption is mostly a measure of how consistently the firm uses its own system. The client behavior follows. If adoption is low and you have fixed the first four items on this list, the fifth is where the answer is.

What good looks like

A firm with healthy adoption is not one where every client is enthusiastic about the portal. Most clients will never think about it at all — which is the point. It looks like this: invitations convert, document requests close without a phone call, the mailbox stops being the system of record, and staff stop being able to tell you how many documents are outstanding off the top of their heads, because they no longer have to hold it in their heads.

None of that requires clients to become more technical. It requires the path of least resistance to run through the portal instead of around it.

How Kveldo approaches this

The client portal in Kveldo is built around the five points above: a guided three-step setup with a copyable 2FA key beside the QR code, tracked document requests rather than open-ended asks, a "needs your attention" dashboard rather than a feature tour, notification emails that carry your firm's name and branding and link back rather than delivering content, and a two-click "upload on the client's behalf" action so staff never have to choose between being helpful and keeping the record straight.

Client portal access is free at every plan tier, and clients are never counted as seats — because a portal that costs more the more people use it is a portal designed to stay unused.

See how the client portal works →
Read next: chasing documents is a process problem →