Stop running client work from your inbox
Email is a queue only one person can see. What inbox-run client work really costs an agency, and a migration path where clients keep emailing.
· 4 min read · Agency operations
It is 4:52pm on a Friday when the WhatsApp arrives. A client wants a change to the pricing page before their board meeting. The account manager reads it on the train, mentally files it under Monday, and by Monday the message is forty scrolls up in a thread that has since moved on to a discussion about a photoshoot. Nobody decided to drop the request. It simply had nowhere to land.
That is the whole problem in one paragraph. Not laziness, not carelessness. Requests arriving in places that were never built to hold them.
Your inbox is a queue nobody can see
An inbox is a queue with exactly one viewer. When client work runs through it, the state of the agency lives in one person's mailbox: what has been asked for, what has been promised, what is blocked, what was quietly agreed in a reply at 10pm. The rest of the team can see none of it.
This has a strange consequence. The busiest person in the agency becomes the least visible. From the outside, everything looks calm, because the chaos is private. Work is being triaged in one head, prioritised by scroll position, and progressed in whatever order the replies happen to surface. When someone asks what is on for the week, the honest answer is stored in a mailbox, and mailboxes do not answer questions.
Email is a superb transport and a terrible database. It moves messages beautifully. It holds work terribly.
Requests arrive from everywhere, and none of it is on the record
The inbox is only the largest of the leaks. Real client requests arrive by email, yes, but also by WhatsApp, by phone, and in the last two minutes of a call when someone says, while I have got you, could we also. Each channel feels legitimate to the client, and each one produces the same result: a request that exists only in the memory of whoever happened to receive it.
The "while I have got you" request is the most dangerous of the lot, because it is agreed verbally, never written anywhere, and remembered differently by both sides. There is a longer look at that particular species in the "can you just" request. The short version: an unrecorded request is a dispute on a delay timer.
What it actually costs
Three costs, and they compound.
Dropped requests. Some percentage of what arrives simply vanishes. The client notices before you do, because the client is waiting and you are not. Every dropped request converts a routine piece of work into an apology, and clients keep a private ledger of apologies.
No record of what was agreed. When the client says they asked for three concepts and you remember two, there is no neutral place to look. The agreement lives in a call, or a deleted voice note, or an email only one side can find. You will usually absorb the difference, because arguing costs more than doing the work, and absorbing scope quietly is how retainers stop being profitable.
One mailbox as the company's memory. If the account manager is on holiday, the state of three clients is on holiday too. If she resigns, the agency loses not just a person but a filing system. No handover document survives contact with six months of threads.
None of this shows up as a line item. It shows up as Friday evenings spent reconstructing what was promised, and as clients who chase because chasing is the only visibility they have.
A migration where email still works
The reason agencies stay in the inbox is not that they love it. It is that every alternative seems to require retraining clients, and clients will not be retrained. Any migration that begins "our clients will now log a ticket" is a migration that ends with your clients emailing you anyway, plus a tool subscription.
So do not ask clients to change on day one. Pick a system where email is a front door: mail sent to a workspace address becomes a ticket automatically, with the thread attached. The client keeps emailing exactly as before. What changes is where the message lands, which is a queue the whole team can see, rather than a mailbox only one person can. Then the move is unremarkable:
- Pick one client. Not your biggest, not your most nervous. A steady retainer with a reasonable contact.
- Route their requests into the workspace. Email arrives as before and becomes a ticket; anything that comes in by phone or WhatsApp gets logged by whoever took it, in under a minute. Some tools will even draft the ticket from a pasted email, which removes the last excuse.
- Work from the queue, not the mailbox. A filterable list, a board, and a view of what is due replaces scroll position as the prioritisation method.
- Put a visible landing date on every request, so the client can see when their work will arrive without asking. This, more than anything, is what stops the chasing, because status updates stop being a manual chore.
- After a month, move the next client. By the third, the mailbox is just a mailbox again.
The client experience on day one is unchanged. The agency experience is transformed, because for the first time the queue is a shared object rather than a private burden.
Where HoopoeHQ comes in
HoopoeHQ works exactly this way: email a workspace address and it becomes a ticket, every request carries a landing date the client can see, and your team works from one calm queue instead of five mailboxes. It was built inside a working agency that had exactly the Friday-at-4:52 problem described above. If that sounds familiar, start a 14-day trial with one steady client and see whether the chasing stops.