Patients book their turn on WhatsApp, watch the queue move from home, and walk in minutes before they're called. Your receptionist stops answering “how long more, sir?” and starts running the day from one screen.
Works on the phone every patient already has. No app to install — theirs or yours.
Already using LiveQueue? Log in to your clinic ›
An hour on a plastic chair with no idea how much longer. Some walk out and don't come back — and you never find out why.
A paper register, a marker board, and a phone that rings all morning. One person holds the whole day's order in their head.
No-shows leave a chamber empty at 11. A rush leaves it three deep at 12. Nobody has the numbers to fix either.
LiveQueue sits between the phone in your patient's pocket and the screen at your front desk. Everything else stays exactly as it is.
To your clinic's WhatsApp number. No app, no signup, no form. The bot answers with today's doctors and sessions, and they reply with a number.
They get their number, who's being seen right now, an estimated time in both “about 25 minutes” and “around 11:40”, and a link that tracks the queue live. Walk-ins get the same thing, issued at the desk in two taps.
The tracker updates itself as the queue moves. When their turn is close, LiveQueue messages them to start heading over — timed against how fast this doctor is actually moving today, not a fixed guess.
The board in the waiting area flips, the doctor's screen updates, and that patient's phone chimes and buzzes. Someone who hasn't shown up is held, not lost — and the queue keeps moving instead of stalling on them.
Tomorrow's sessions are created overnight from your weekly rota. Each morning's sessions open at their own advertised start time. You get consultation times, wait times, no-show rates and volumes per doctor — measured, not estimated.
Nothing about your consultation changes. Everything around it does.
Every screen updates the instant anything changes — no refresh button, anywhere.
Call next, pause for a break, add a walk-in, check someone in, open and close the session. The whole day from one screen — and it visibly disables itself if the connection drops, so it never lies to you.
Who's in front of you, who's next, how many are left. Nothing else. The doctor never has to ask the front desk anything.
A big “now serving” number and who's up next, on any screen with a browser. Point an old smart TV or a spare tablet at a URL and you're done.
Their number, the current number, and a live estimate — open on their phone at home. When they're called it chimes and buzzes, even from a pocket.
Doctors, staff logins and roles, the weekly rota, the booking window, and analytics on volumes, waits and consultation times — averaged from what actually happened, never rolled up from other averages.
Takes bookings, confirms them, sends the “start heading over” nudge, announces delays, and tells someone their turn has come — on the one app every patient already opens twenty times a day.
Open a window of 0 to 30 days when you're ready. The same per-session cap applies, so a future day can't be oversold.
An advance token checks in at reception. Until then it's passed over rather than blocking the room.
A patient who calls instead of texting gets booked from the desk into any date in your window — the same token, the same confirmation.
Every booking on a day with its status and remaining slots. Cancel one, fix a name, or move someone to another session.
The rota creates tomorrow overnight; each session opens at its advertised start time. Closing stays a deliberate, confirmed act.
Confirmation, one heads-up when their turn slips, the call itself. Never a message for every small change.
Receptionist, doctor, clinic administrator, owner. A clinic can never be left without an administrator, and nobody can lock themselves out.
The wait quoted is built from this doctor's recent consultation times today — not a number somebody typed in once.
Multi-clinic from the ground up, with each clinic's data strictly its own and its own timezone, hours and booking window.
No. Booking happens in WhatsApp, and the live tracker is a link that opens in their browser. There is nothing for a patient to install, register for, or remember a password to.
They're handled exactly as before, only faster — the receptionist issues a token in two taps and it joins the same queue as the WhatsApp bookings, in the right order. A phone number is optional for a walk-in.
They're held rather than dropped. The queue moves on to the next patient and the one who missed their call is re-seated just behind, keeping their place relative to everyone else. After a few passes the token is released, and they're told.
The console tells you plainly that it's disconnected and disables the actions it can no longer trust, rather than quietly showing you a stale queue. It reconnects and catches up on its own. Nothing is lost.
A working session on the first day: add your doctors, their weekly hours, and your WhatsApp number, and the queue can run that afternoon. Advance booking and reports are switches you turn on when you want them.
Yes — separation is enforced in the database itself, not by a check somewhere in the code that could be forgotten. A request that reaches for another clinic's data doesn't get a refusal; it gets nothing at all.
We'll set up a session with your doctors' names and hours and hand you a phone. Book a token, watch the board, call the next patient. Then decide.
Currently onboarding a small number of clinics. You'll speak to the people who built it.