A pharmacist is halfway through checking a prescription when the telephone rings. It is somebody asking whether their prescription is ready.
While she answers, two people join the queue at the counter. One wants to know when the pharmacy closes on Saturday. The other is collecting for a relative and wants to know whether they are allowed to.
She resumes the check. This happens between forty and sixty times a day, and not one of those three questions needed a pharmacist.
The first failure: the cost is measured in minutes
A thirty second question that interrupts a clinical check is not a thirty second cost. Restarting a precision task carries a risk that no time calculation captures.
The second failure: status enquiries dominate everything
Is it ready, has it arrived, did the surgery send it. The single largest category of contact and the one requiring the least expertise.
The third failure: nobody is notified when something is ready
Which generates the status enquiries in the first place. A message when a prescription is ready removes most of the traffic at the source.
The fourth failure: the telephone has priority over the person present
A ringing telephone interrupts both the dispensing and the customer at the counter, and the person physically waiting is served worse than the person who rang.
The fifth failure: the routine questions have no other home
Opening hours, collection rules, service availability and delivery arrangements exist nowhere findable, so the counter is the only route.
The sixth failure: the clinical and the administrative arrive together
A question needing a pharmacist and a question needing a status lookup enter through the same door at the same priority.
The seventh failure: the queue discourages the useful conversation
Somebody who needs advice will not raise it in front of a queue, so the questions that genuinely need a pharmacist are the ones that do not get asked.
The eighth failure: the delivery and collection rules generate avoidable trips
People arrive to ask something they could have been told, which is the ground in prescription collection questions pharmacies answer all day.
The ninth failure: the peak is predictable and unstaffed
Volume clusters around opening, lunchtime and the hour before closing, and rotas frequently do not reflect it.
The tenth failure: the same question recurs from the same people
Monthly, because the process was never explained once properly, which is the pattern described in call volume from routine questions that never change.
The eleventh failure: the boundary is not drawn
Anything answered automatically must stop cleanly at clinical territory, which is the discipline set out in what a pharmacy website must never advise.
The twelfth failure: the counter and the telephone are staffed by the same person
One person cannot serve a queue and answer a telephone, so whichever is in front of them wins and the other waits. In a small pharmacy this is the structural constraint behind almost every complaint about service.
The thirteenth failure: nobody measures the interruptions
Pharmacies that count them for a single day are usually shocked, and that number is what justifies doing anything about it.
The fix: take the status traffic off the counter entirely
An assistant that answers status enquiries, notifies people when a prescription is ready, explains collection rules and opening hours and hands anything clinical straight to the pharmacist protects the check that was interrupted sixty times today. The same principle as stop answering the same email twice automate it. Start at try, see features, and the sector view sits under pharmacies.