A client needs to return one signed form. They open your email, tap the portal link, and land on a login screen. The password won't come to them, so they ask for a reset, wait, invent a new one the system calls too weak, try again, then give up and text you a photo of the page instead. Eleven minutes, a little quiet resentment, and none of it visible from your side of the desk.
You bought that portal for good reasons. Documents in one secure place, e-signatures that actually hold up, payments that don't ride on a mailed check. Then most clients kept emailing anyway, and now you're running two systems: the one you pay for and the one your inbox quietly became.
Here's the part worth sitting with. The portal isn't failing on features. It's failing on friction, the small frictions between a client and the thing they came to do. You fix friction with a few automations, not with a new subscription.
Friction is the whole story
Think about what you actually ask a client to do. Find an email from three weeks ago, remember a password they set once, get past a two-factor code, then hunt for the right folder. Every step sheds people. By the time they're logged in, the ones who'd rather just email have already emailed.
Count the taps sometime. A portal that takes eight steps to upload one PDF is competing with email, which takes two. Clients aren't lazy. They're doing the cheaper thing, and right now email is the cheaper thing.
So the goal isn't more portal. It's fewer steps to the same secure result. Three changes carry most of the weight.
Send a one-tap link, not a password reset
A magic link is a one-time, secure web link you text or email a client that logs them straight into their own portal, with no password to remember. They tap it, they're in, they see the one document that needs them. That's the whole interaction.
Most portal vendors already support this, sometimes under a name like 'secure link' or 'passwordless access.' If yours does, turn it on and make it the default way clients arrive. If yours doesn't, that's a real mark against the software, and worth raising the next time the contract comes up for renewal.
Send the link by text when you can. A portal login emailed at 4 PM competes with forty other emails and loses. A text sent the same minute usually gets read within a few minutes, and a one-tap link means the client can act on it from the parking lot. Keep the message plain: what's waiting, one link, your firm name, nothing else.
Nudge only when something is actually waiting
A reminder that fires on a schedule teaches people to ignore it. A reminder that fires because a specific document is sitting unsigned teaches people that when you message, it means something. That difference is most of the game.
Wire the nudge to the event, not the calendar. When a document has been waiting on the client for, say, two business days, one message goes out: the document's name, the one-tap link, and that's it. If they act, the nudges stop, because the thing you were nudging about is done.
A nudge worth sending has four traits:
- It names the exact item (the engagement letter, not 'a document')
- It carries the one-tap link, so reading it and doing it are the same action
- It stops the moment the task is complete
- It comes from a real number or address the client can just reply to
Figure one nudge, maybe two, for most items. If a third is needed, that's usually a sign to pick up the phone, which is a different tool for a different problem.
Log the exchange either way
Now the honest part. Some clients will email you the document no matter how clean the portal gets. Older clients, rushed clients, the ones who've done it by email for fifteen years. Fighting that habit costs you more than absorbing it does.
So build the fallback. When a client emails a document instead of using the portal, a small automation can file that attachment into the right client record, log that it arrived, and stamp the date, without anyone rekeying a thing. The client used the easy door. You still got the clean record.
This matters for the reasons your compliance habits already care about: a complete file, a timestamp on every exchange, and nothing important living only in one person's inbox. The portal was supposed to hand you that. The fallback makes sure you get it even when a client goes around the portal entirely.
What this won't fix
Automations drive adoption. They don't manufacture it out of thin air. A few things stay stubborn, and it's fair to say so plainly.
- If your portal's core experience is genuinely clunky, slow to load, confusing on a phone, menus buried three levels down, then links and nudges only get people to the door. Behind it, they still struggle, and no automation paints over that.
- Complex, multi-document exchanges still need a human to set expectations. A magic link is great for one signature and less so for 'upload three years of returns and the K-1.'
- A small handful of clients will never adopt any portal, and that's fine. The fallback exists precisely for them.
None of that is a reason to skip the work. It's a reason to aim the work where it pays back, at the routine one-item exchanges that make up most of your portal traffic anyway.
Worth doing this week
You don't need a project for this. You need an afternoon and a short list.
- Log into your own portal as a client would, from your phone, and count the taps to upload one document. That number is your problem stated in a single figure.
- Check whether your vendor supports one-tap or passwordless links. Turn it on, or put 'why not?' on the agenda for your renewal call.
- Pick the three documents clients most often owe you (engagement letter, records request, invoice, whatever yours are) and write the plain text you'd send for each.
- Turn one scheduled reminder into an event-based one, so it fires because a document is waiting and goes quiet the moment it's signed.
- Set up the email fallback for at least one document type, so an emailed attachment still lands in the right file with a date on it.
Do those five and you'll watch logins climb without buying anything new. If you'd rather have someone wire the links, the nudges, and the fallback into the portal you already own, that quiet plumbing is the kind of thing we set up for Massachusetts practices at AI Agency Mass. Either way the fix is the same: take away the friction, and the software you already pay for starts earning its keep.