Notes / Client portal / 4 min read
Stop resending login instructions
WhizSuite · 2026-09-24
A guide that long usually means the path is wrong, not that the client cannot read.
Watch the first login
Sit with one client, or watch a screen recording, the first time they enter. Every place they pause is a defect. Fix those before you write a longer PDF.
The happy path should be: open link, see the post, answer it. If password resets sit in the middle of every session, something is expiring too aggressively or the link is not actually a login.
One page, five lines
If you still need instructions, keep them to five lines beside the link. A twelve-page onboarding for a yes button will not be read. It will be forwarded to an assistant who also will not read it.
Put those lines in the kickoff email and nowhere else. Multiple versions of the instructions will contradict each other by next quarter.
Access for assistants
Many approvers do not want a login. Their assistant does. Offer a second seat with a clear role instead of sharing a password. Shared passwords are how you lose the record of who said yes.
Name the assistant in the retainer so a stranger does not appear in the portal one morning.
Measure repeat asks
Count how many times your team resends access in a month. If the number is high, the portal is not easier than email yet. Believe the number.
Fix the top reason, then stop adding tips. Tips pile up. Friction needs a cut.