Virtual Queues for Australian Community Pharmacies: Scripts, Vaccinations, and the 4 PM Rush

Community pharmacy in Australia has quietly turned into a multi-service business. A typical suburban chemist now runs script dispensing, vaccinations (flu, COVID, shingles, travel), MedsChecks, sleep apnoea trials, vitamin advice, baby formula sales, photo printing, and the 4 PM after-school chaos of working parents picking up scripts before dinner.

The dispensing system handles the medication side. It does not handle the people standing at the counter. That is what a virtual queue is for — and in a pharmacy, the gap between "script is ready" and "customer has been served" is where margin and goodwill leak.

This is for pharmacy owners, pharmacists-in-charge, and retail managers running independent and banner pharmacies (Chemist Warehouse, Priceline, TerryWhite, Amcal, Guardian, Discount Drug Stores) across Australia.

The actual problem on a Tuesday at 4:15 PM

A normal weekday afternoon at a suburban pharmacy:

• A parent walks in for a daughter's antibiotic.
• The flu vaccination room has one patient in it and two waiting.
• A regular elderly customer is at the counter with a Webster pack question that will take six minutes.
• Two people are at the photo kiosk, one is at the front register buying sunscreen, and one is in the vitamin aisle making eye contact with the pharmacist for advice.
• The dispensing queue on the screen says 9.

The pharmacist is the constraint. Every interrupt costs three to four seconds of dispensing accuracy attention, and a busy pharmacy cannot afford to spend that on "is my script ready yet?" — the answer to which is always we'll let you know.

A virtual queue gives customers a way to know. It gives the pharmacy a way to call them back without yelling a surname across the shop floor.

What the setup looks like

Most pharmacies deploy this shape:

1. QR code at the script drop-off counter. Customer hands in their scripts (or sends them through the eRx token), scans the QR, enters name, mobile, and what they're waiting for.
2. Optional kiosk for older customers. A small tablet at reception height so an 82-year-old does not have to use their own phone.
3. Dispensing software stays the system of record. FRED, LOTS, Minfos, or Z Dispense continues to handle the script. The queue is the customer-side layer only.
4. SMS when ready. "Your scripts are ready at TerryWhite Glenfield — see you at the counter."
5. Separate lanes for vaccinations and consults. Different intake reason, different dashboard, different staff member.

The pharmacist on dispensing does not touch the queue. The retail team and the dispensing technician do — the same people who already manage handovers.

Lanes that matter in a community pharmacy

Pharmacies are unusual because they run several queues at once. A virtual queue lets you make them visible:

• Script wait — the long one. Customers can leave the shop and come back, which is the entire point. SMS arrives, they return.
• Vaccination — short, room-bound. Walk-in flu shots, COVID boosters, travel vaccines. Owners want this as bookable as possible, but the walk-in lane still matters in winter.
• Pharmacist consult / MedsCheck / HMR follow-up — needs the pharmacist's attention for ten to fifteen minutes. Visible in the queue with a tag so it can be scheduled around dispensing peaks.
• NDSS, sleep apnoea, dose admin aid pickups — quick handoffs. Often blocked by the script queue today. A separate fast lane fixes that.

The single biggest operational win we see is splitting the script-pickup lane from the consult lane. They are different services with different durations, and merging them is what creates the afternoon pile-up.

Compliance and the Pharmacy Board

A virtual queue is a customer-flow tool. It is not a clinical record and not a dispensing record. That is the right side of the line for Pharmacy Board of Australia obligations and the PSA Professional Practice Standards — your dispensing software remains the record of truth for the script, the counsel, and the supply.

Specifically the queue does not, and should not:

• Store clinical information.
• Hold a copy of the script.
• Record counselling content.
• Touch Schedule 8 or Schedule 4 records.

What it stores is operational: name, mobile, arrival time, reason tag, SMS log. Same posture as the appointment book on the counter, in a digital form.

The 4 PM rush — what changes

Most pharmacies have a clear afternoon peak between 3:30 PM and 6:00 PM as workers and parents pick up scripts. The before-and-after on this peak is the easiest place to show the value:

• Before. Customer drops script, asks "how long", is told "fifteen minutes", waits twelve, asks again at minute ten, leaves at minute eighteen frustrated, returns the next day. Two interrupts to the dispensing bench.
• After. Customer drops script, scans QR, gets a wait estimate on their phone, walks to Coles, gets SMS at minute fourteen, collects at minute sixteen. Zero interrupts.

Multiply that by sixty customers on a Tuesday afternoon and the pharmacist gets thirty to forty minutes of uninterrupted dispensing back. That is a real safety margin, not just a service one.

SMS done in a way the Pharmacy Guild would not roll its eyes at

Three rules we follow, and you should:

• Transactional only. "Your script is ready." Not "your script is ready and have you considered our vitamin range." The Spam Act 2003 has a transactional exemption — use it carefully, do not push it into marketing.
• Clear sender ID. Customers should know which pharmacy is texting them. The brand name in the sender field, not a random shortcode.
• One opt-out path. STOP works on Australian SMS by convention. ServQueue handles it automatically.

If you want to send marketing later, do it through a separate consent flow, not through the queue. Keeping these clean is what protects the sender reputation that makes the transactional messages arrive.

Workflows the queue handles well

• Script wait with leave-and-return. The core use case.
• Vaccination room flow. Tag, room ready, SMS in.
• Pharmacist consult queue. Separate from scripts, so it doesn't compete for attention.
• Late or running-behind broadcasts. "Vaccinations running 20 minutes behind, we'll text you when the room is ready" — sent to the next three customers in that lane only.

Workflows it does not handle

• Script management. Dispensing software.
• Stock and ordering. Dispensing or POS.
• Loyalty / rewards. Banner group's loyalty stack.
• Pricing or PBS claiming. Dispensing software only.

The queue is a thin layer that sits on top. It does not try to be a pharmacy operating system.

What changes in the first 30 days

• Week 1. Staff are sceptical, customers are confused for two days. By day four, the front-desk dispensary tech has stopped shouting surnames across the shop and is visibly happier.
• Week 2. Pharmacist notices fewer interrupts. Dispensing errors caught at final check drop measurably for some clinics — this is anecdotal but consistent.
• Week 3. First clean walkaway data — customers who joined the queue and left without collecting. Often this exposes a Saturday-morning understaffing problem nobody had numbers on.
• Week 4. A conversation about adding the vaccination lane, which is where the second wave of value comes from.

Cost vs. an hour of casual time

ServQueue is A$49/month single store, A$129/month for multi-store. That is roughly one hour of casual retail time per month at award rates. The framing for the owner is the same one we use everywhere: give it 30 days, see whether it pays for itself in reduced interrupts, and walk away if it does not.

Free 7-day trial, no card. The ServQueue for pharmacies page has the pharmacy-specific feature overview and AUD pricing. If you want to talk through a specific pharmacy setup before signing up — particularly multi-store and shared SMS sender ID — contact us. Otherwise the onboarding flow takes about ten minutes.

Related reading: the medical clinics guide covers a similar walk-in plus appointment mix, and the SMS provider guide explains why we route Australian SMS the way we do.