Setting up a client service desk for your accounting practice

A step-by-step guide to standing up boards, statuses and queues so every client request becomes tracked work that nothing slips past.

Most accounting practices do not lose work because the team is careless. They lose it because client requests arrive everywhere at once: an email here, a phone note there, a quick question in a corridor, a document dropped into a shared folder. Without a single place to capture and track that work, things quietly fall through the cracks until a client chases. A client service desk fixes this by turning every request into a tracked piece of work with an owner, a status and a due date.

This guide walks through how to stand one up in your practice, and which decisions actually make it stick.

Why a service desk beats an inbox

A shared inbox feels like a service desk, but it behaves nothing like one. Emails get marked as read and forgotten. There is no clear owner, no priority, and no way to see how much work is in flight. Two people reply to the same client, or nobody does. When a partner asks what is outstanding for a client, the honest answer is a scroll through someone's mailbox.

A service desk replaces that guesswork with structure. Every request becomes a work item on a board. Each item carries a status, an assignee, a priority and a client it belongs to. You can see the whole queue at a glance, sort by what is overdue, and know that nothing is sitting unattended. The shift from "who has this email?" to "this job is in progress, assigned to Sam, due Friday" is the whole point.

Step one: design your boards

A board is the workspace where related requests live. The first real decision is how to divide work into boards, and the most common mistake is creating too many. Start with how your practice actually operates rather than your org chart.

For most firms, a small set of boards works well:

Client requests for the general flow of ad-hoc questions, document chasing and one-off jobs.
Compliance work for recurring obligations such as BAS, IAS and income tax returns, where due dates drive everything.
Onboarding for new clients moving through engagement, AML/KYC and setup.

You can always split a board later once you can see real volume. Starting lean means the team adopts the desk instead of getting lost in it. In Finye you can view any board as a kanban for a visual sense of flow, or as a list when you want to sort and filter a long queue.

Step two: define statuses that mean something

Statuses are the columns on your board, and they describe where a piece of work sits in its life. The trap here is copying a generic to-do, doing, done set that tells you nothing useful. Good statuses reflect the real stages a request passes through and, crucially, who the ball is with.

A practical set for an accounting practice might be:

New for requests that have landed but nobody has triaged yet.
In progress for work actively being done.
Waiting on client for anything blocked pending information, a signature or a payment.
In review for work that needs a second set of eyes before it goes out.
Done for completed and closed.

That waiting on client status earns its place. A huge share of accounting work stalls because the client has not sent something back, and without a dedicated status those jobs hide inside "in progress" and look like your team's problem when they are not. Pulling them into their own column shows you exactly what to chase, and protects your numbers when you review productivity.

Step three: get requests into the desk automatically

A service desk only works if requests actually land in it. The fastest way to kill adoption is to ask staff to manually copy emails into the system. Instead, route the work in for them.

Finye turns inbound client emails into work items through email-to-ticket, so a message to your support address becomes a tracked item on the right board without anyone retyping it. Your client portal does the same from the other direction: clients raise requests, upload documents and approve work, and each action flows straight onto the desk. For incoming requests, AI triage can suggest a priority, an assignee and a category, so a fresh item arrives already partly sorted rather than as a blank line waiting for someone to make sense of it.

Step four: set the rules that make it stick

Tools do not create discipline; agreements do. Before you switch on, settle a few working rules with the team so the desk stays trustworthy.

One front door. Decide that the desk is where work lives, and that nothing of substance happens purely over email or in someone's head. If it is not on the board, it does not exist.
Every item has an owner. Unassigned work is nobody's work. Triage should leave each item with a named assignee.
Statuses are kept honest. Moving an item to waiting on client the moment it stalls is what keeps the board an accurate picture rather than a wish list.
Use checklists and subtasks for multi-step jobs. A year-end file or an onboarding has many moving parts; breaking an item into subtasks stops the detail living only in one person's memory.

Once the desk reflects reality, the rest of the practice gets easier. Recurring compliance jobs can be templated so a quarterly BAS generates itself, time logged against work items feeds your WIP, and a partner can finally answer "what is outstanding for this client?" in seconds.

Start small and let it grow

You do not need a perfect configuration to begin. Stand up two or three boards, agree a handful of statuses, point your client email and portal at the desk, and commit to keeping it honest for a fortnight. The structure will tell you where to refine. What you will not do again is wonder whether a client request quietly slipped through.

If you are ready to turn scattered requests into tracked work, create your Finye workspace and build your first board, or see how it fits your team on the pricing page. You can also browse our guides for more on running a modern practice.