The question that went missing
Tuesday morning, mid-cycle. A client emails one of your payrollers directly: "Quick one, should Mrs Patel's maternity pay have started this period or next?"
Your payroller is halfway through a weekly run with a lunchtime BACS deadline. She reads the email, makes a mental note, and gets back to the run. By Thursday the question has slipped beneath forty newer emails. The client, hearing nothing, rings the office. The person who answers has never heard of Mrs Patel. The original email is in a colleague's personal inbox, invisible to everyone else.
Nothing about this story involves a bad payroller. Every part of it involves a bad system. The inbox did exactly what inboxes do.
Why the inbox fails as a payroll helpdesk
Email is where client questions naturally arrive, which is precisely why it feels harmless. But measured as a helpdesk, it fails on every count that matters to a small bureau.
No ownership
An email sits with whoever received it. If they are processing, on leave, or simply busy, the question waits. Nobody else knows it exists, so nobody else can pick it up.
No status
An inbox cannot tell you whether a question has been answered, is being worked on, or has been forgotten. The only way to find out is to ask, which in a small team means interrupting the very people trying to hit cut-offs.
No history
When a client disputes what they were told about a pay rate in March, the answer is buried across three people's inboxes and a deleted folder. There is no audit trail, and in payroll, the absence of an audit trail is a risk, not an inconvenience.
No visibility of the workload
Here is the one small bureaus feel most. Answering queries is real work. It consumes hours every week. But because it happens invisibly inside inboxes, it never appears in any view of team workload. You staff for the payroll runs you can see and absorb the query load you cannot.
The same question, through a query hub
Now replay Tuesday morning with a payroll helpdesk in place.
The client raises the maternity pay question through their portal. It is logged the moment it arrives, visible to the whole team, not trapped in one inbox. Your payroller finishes her BACS deadline first, because the question is safely held with a status, not relying on her memory. A colleague with capacity picks it up, checks the client's record in the contact directory, and answers it that afternoon. The client sees the response in the same place they asked, with a full record of who said what and when.
No chasing phone call. No archaeology through inboxes. And at the end of the month, you can see exactly how many queries the team handled, from which clients, about what.
Queries are workload. Make them count.
That last point deserves its own moment. When queries are logged rather than scattered, they become measurable. You discover that one client raises more questions than your next ten combined. You see that query volume doubles in the week after payslips land. You learn what your team's real capacity looks like, not just their processing capacity.
For a bureau of eight or twelve people, that knowledge changes decisions. It shapes pricing conversations, staffing plans, and which clients need a gentle process reset. None of it is available while the questions live in an inbox.
Clients ask questions because they trust you with something that matters. A structured query hub makes sure that trust is never let down by a busy Tuesday.
See how other bureaus handle client queries at https://www.changepen.co.uk/customers
