Key takeaways
- Move one service, not the whole firm.
- Explain the client benefit before the client sees the new link.
- Run both channels for one period, then make the portal the default.
- Keep a small exception process for the clients who cannot use the portal.
Pick one service
Start with the service that has the most repetitive requests, usually the monthly close or the tax organizer. The client already expects the request, so the change is about the channel, not the work.
Do not start with the most complicated client or the largest service. Start with a client who is responsive and a checklist that is already stable.
Write down what the portal will replace: the email request, the attachment, the reminder and the download folder. The migration is a replacement, not an addition.
Explain the client benefit
Tell the client why the portal is better for them: one link, no password, progress saved, a phone-friendly checklist and reminders that stop when everything is in.
Do not lead with the firm's efficiency. The client cares about their own experience, even when the firm's efficiency is the reason for the change.
Send the explanation before the first portal request, not in the same email. A short note in advance reduces the chance that the client ignores the new link.
Run both channels for one period
For the first period, send the portal link and accept the documents by email if the client prefers. The goal is to prove the portal works, not to win every client in the first month.
Track which clients used the portal and which used email. The clients who used the portal are the proof for the next period; the clients who did not are the ones who need a call.
Do not run both channels forever. A parallel period is a transition, not a permanent process.
Make the portal the default
After one period, make the portal the default for the service. The email request can still introduce the request, but the documents go through the link.
Keep a small exception process for a client who cannot use the portal, such as a client with no email or a client whose system blocks the link. The exception should be documented, not improvised.
Tell the client what happens if they reply with an attachment. A short, polite auto-reply or a line in the email can redirect them to the link.
Train the team
The team needs to know what the client sees, how to resend a link, how to mark an item as received and how to send back one file. A portal that the team does not understand becomes another inbox.
Run one internal session with a test client. Have each person open the link on a phone and finish one item. The team's confidence shows in the client's experience.
Write a one-page internal guide with the five actions the team uses most. Keep it next to the portal link.
Measure and retire the old channel
Measure the portal use, the time to complete and the number of manual follow-ups. Compare the first portal period to the last email period.
When the portal is working, retire the old channel for that service. A firm that keeps every channel open keeps every inbox open.
Do not retire the email address. The client still needs a way to ask a question. Retire the attachment process, not the conversation.
Handle the clients who resist
Some clients will resist any change. Ask what specifically is hard: the link, the login, the phone or the upload. The answer may be a simple fix, such as a one-time code or a phone call.
For a client who truly cannot use the portal, keep the exception process and a manual checklist. Do not let one client block the migration for the rest.
Review the exceptions after three months. Some clients will move when they see the other clients using the portal.