When Every Question Is Urgent: Designing a Request Queue That Protects Focus
Photo: virtual assistant managing shared inbox on laptop with small UK team in office, via images.stockcake.com
Every small firm has a version of the same scene. A colleague appears at the desk, asks a quick question, receives an answer and leaves. The exchange lasts two minutes. The cost is not two minutes. It is the fifteen or twenty minutes of concentration that never returns.
The 'quick question' habit is not a character flaw. It is usually a sign that the business has no reliable route for requests. When there is no shared queue, the nearest knowledgeable person becomes the queue. In a UK small business, that person is often the owner or a senior manager who is already carrying sales, finance and operations.
The Real Cost of a Quick Question
Interruptions are expensive because they fragment attention. A question about a supplier invoice pulls the owner out of a pricing proposal. A request to confirm a delivery slot interrupts a credit-control call. Individually, these moments feel manageable. Across a week, they create a pattern of shallow work, late decisions and unfinished projects.
Consider a team of six where the owner receives ten requests a day, each taking four minutes to answer and ten minutes to recover from. That is over two hours a day before the actual work begins. The arithmetic is uncomfortable, but it explains why so many capable owners finish the week exhausted without being able to point to a single substantial achievement.
Before: The Open-Door Week
On Monday, the owner plans to finish a tender response by Thursday. By 10:15, three people have asked about invoices, a client wants a call moved, and a supplier needs a purchase order number. Each request is reasonable. None is routed. By Friday, the tender is still open and the owner is answering messages at 7pm.
The problem is not that the team is lazy or disorganised. The problem is that urgency has no definition. Everything arrives through the same channel and is treated as equally time-sensitive. The person with the most context becomes the human switchboard.
The Fix: One Front Door, Three Queues
A virtual assistant can run a simple request system that gives the team a single front door and gives the owner protected time. The mechanism is a shared inbox, such as [email protected], with three folders: Today, This Week and Reference.
Today is for requests that genuinely block a customer, a statutory deadline or a same-day operational task. This Week is for routine requests that need an answer within two working days. Reference is for information that needs to be filed, not answered.
The team sends every request to the shared inbox rather than to individual mobiles. The virtual assistant triages at set times, tags each request, checks that it contains the necessary information and either answers from an approved template, routes it to the right person or escalates it. The owner reviews a short digest rather than a live stream.
Batching Makes Answers Better
Batching is not about making people wait for the sake of it. It is about answering related questions together, with full context. A VA can group invoice queries, scheduling changes and document requests into separate blocks. Templates handle repeatable replies. A decision log records what was agreed, which reduces the same question returning next week.
In the before example, the owner answered questions in the gaps between work. In the after example, the owner answers the Today queue at 11:30 and 4:00, and the This Week queue once a day. The tender is finished on Wednesday. The team still gets answers; they simply get better answers, delivered in a predictable rhythm.
The VA's Role
The virtual assistant is not a gatekeeper who decides what matters. The assistant is a router and a preparer. The owner sets the rules: what counts as urgent, who can approve what, which templates are approved and when escalation is required. The VA keeps the inbox clean, chases missing details and maintains the FAQ that stops repeat questions.
Data protection matters. Use a shared mailbox with named users, role-based permissions and a clear retention policy. Do not forward sensitive documents to personal accounts. For finance requests, keep approvals with the authorised person and log the decision.
Making It Stick
Name the queue, publish the response times and review the system weekly for the first month. If a request is urgent every day, the process is not working; the cause may be a training gap, a supplier issue or an unrealistic deadline. Fix the cause rather than reopening the owner's door.
The most common objection is that a shared inbox will feel impersonal. In practice, teams adapt quickly when they can see that requests are acknowledged and answered. The owner gains focus. The team gains certainty. The business gains a record of what was asked and what was decided.
A Practical Start
Pilot the system for two weeks with one team and one shared inbox. Track the number of interruptions, the average response time and the owner's protected hours. At Fylde VA, we would rather set up a modest system that people use than a complex one that becomes another task. The quick question is not going away. The open door does not have to be the only way in.
