The Reply You Keep Sending: One Thread Per Client
Client chasing isn't one big problem — it's a hundred scattered threads. A portal that holds every request in one place is how you stop repeating yourself.
Most client chasing doesn't feel like chasing. It feels like a normal Tuesday: a reply to an email you sent last week, a follow-up text about the receipt that's still missing, a phone call to confirm you got the signed form, another email because the first one landed in someone's junk folder. None of it is dramatic. All of it is you, doing the same small thing over and over, across a dozen disconnected places.
The real cost isn't any single message. It's that the conversation has no home. Every request lives in its own thread, in its own channel, and half of them go unanswered because the client genuinely can't find where you asked. Fixing this isn't about chasing harder or faster. It's about giving each client one place where the whole conversation lives — and making that place the default.
Why the chase never actually ends
Think about how a single query travels through a typical practice. You email the client for last quarter's bank statements. They reply with three of the four. You reply asking for the fourth. They forward it — but to the wrong person, or as a photo of a screen, or two weeks later attached to an unrelated question about their super.
Now multiply that by every open job. Your inbox becomes a filing system you never chose, where the status of any request is buried somewhere in a thread you have to reconstruct from memory. When a client rings to ask "did you get what you needed?", nobody can answer quickly, because the answer is scattered across email, SMS, a shared drive and someone's head.
This is the trap of managing client work through general-purpose tools. Email was never built to track outstanding items. It has no concept of "still waiting" versus "received and actioned." So the chase repeats — not because clients are difficult, but because the system forgets.
One thread, not twenty channels
The fix is structural. Instead of a request being an email that disappears into a stream, it becomes an item in a shared space that both you and the client can see. A client portal does exactly this: it gives each client a single, persistent place where every outstanding request, document and message lives together.
When a request has a home, three things change:
- The status is visible to both sides. The client can see what's outstanding without emailing to ask, and you can see what's received without digging.
- Documents land where they belong. Instead of attachments scattered across threads and inboxes, files arrive attached to the request they answer.
- The conversation is continuous. A reply three weeks later still sits under the original question, so nobody has to reconstruct context.
This is the difference between good accounting client management software and a shared inbox with your firm's name on it. The portal isn't a nicer email — it's a shared record of what each client owes you and what you owe them.
Making the portal the default, not the exception
A portal only reduces chasing if it's where the work actually happens. The common failure is having a portal that clients log into once during onboarding and never again, while the real conversation carries on over email because that's easier in the moment.
To make the portal the default, be deliberate about it:
Route every request through it
When you need something from a client, the request should originate in the portal, not in your email drafts. In Finye, document requests and messages are tied to the client's record and their work items, so the ask, the reminder and the received file all sit in one linked place. The client gets notified, but the request itself lives somewhere permanent.
Stop answering the same questions manually
A large share of "chasing" is actually clients chasing you — asking where their return is up to, whether you've received their documents, when something's due. A portal that shows the current status of their work answers those questions before they're asked. That's a two-way saving: fewer status emails from them, fewer interruptions for your team.
Set the expectation early
New clients should learn during onboarding that the portal is how you work together — this is where you'll send requests, this is where they'll upload, this is where they can check status. When the norm is set at the start, you don't spend the next two years pulling clients back from email.
What this does to your firm's workload
The obvious win is fewer emails. The bigger win is that outstanding items stop being invisible. When every request lives in one system, you can see across your whole client base what's still waiting — which jobs are stuck on a missing document, which clients have gone quiet, which requests have been sitting for a fortnight.
That visibility is what turns chasing from a reactive scramble into a managed process. Instead of individual staff remembering to follow up on individual threads, the practice can see the full picture and act on it. Reminders can go out automatically for overdue items. Work items don't quietly stall because the person who sent the request went on leave and took the context with them.
This is where a portal connects to the rest of client accounting: the request isn't a loose email, it's part of the job. When the document arrives, the job can move. When it doesn't, the job — and the reason it's stuck — is right there on your board rather than lost in someone's sent folder.
The point isn't to chase better
It's tempting to treat client chasing as a discipline problem — if we just followed up more consistently, sent reminders on a schedule, kept better notes. But more disciplined chasing is still chasing. The real goal is to remove the conditions that make chasing necessary: scattered threads, invisible status, documents with no home, and no shared record of what's outstanding.
A client portal that becomes your default does that quietly. Each client gets one thread. Every request has a place. Both sides can see where things stand. And the reply you used to send five times a week — "just following up on the below" — becomes the exception rather than the rhythm of your day.