Hospital OPD queues

A queue management system for hospital OPD wings — not a HIS replacement

A 200-bed hospital's OPD block runs eight specialties out of one lobby, and by 9:30 every counter has a line that isn't moving because nobody outside the building can see it. A queue management system for hospital OPD wings has to solve a harder problem than a single-doctor clinic: which specialty, which counter, which floor — before a single token gets issued. TOKENN handles that routing entirely on WhatsApp, without touching your hospital information system.

Why a single-doctor OPD tool breaks in a hospital

A solo GP's queue tool only has to answer one question: what number are you. A hospital OPD block has to answer three — which department, which counter, and which floor — before it can even issue a number. General medicine, orthopedics, gynecology and pediatrics often share one entrance and one crowd of confused patients on their first visit. A token system built for a single doctor simply has nowhere to put that routing decision.

The result, in most hospitals still running paper tokens, is a general enquiry counter that becomes a second bottleneck — patients queue once to find out where to queue again.

What TOKENN actually manages in a hospital OPD block

Department-wise queues with independent token series, WhatsApp-based booking and routing, live wait estimates per department, and waiting-area displays for each floor or counter. That's the full scope, and it's deliberately narrow: TOKENN is the outpatient queue and patient-communication layer, not a hospital information system.

Routing patients to the right department on WhatsApp

A patient messages the hospital's WhatsApp number and, when it isn't obvious, the AI asks one short clarifying question — "Which department would you like — General Medicine, Orthopedics or Gynecology?" — before issuing a token into that department's own queue. Patients who already know where they're headed skip the question entirely by scanning that department's own QR code posted at its counter, and go straight into the right line.

Referrals between departments, mid-visit

A general medicine consult that ends in "go get an ECG and come back" is routine in a hospital OPD and routinely breaks paper-token systems, which force the patient to pull a fresh number. TOKENN parks the original token in an awaiting-return lane instead — the same mechanism clinics use for lab-report loops — so the patient rejoins on the same token once the referred department is done, with no second queue and no lost place in line.

Multiple entry points, one connected queue

Larger hospitals often run more than one registration counter — a main lobby desk plus a satellite counter near a busy department, sometimes on a different floor entirely. Every counter feeds the same live queue data, so a token issued at the satellite desk shows up correctly on the main lobby's display and vice versa. Reception at any counter sees every department's queue, not just the one physically in front of them.

Display boards across a hospital OPD floor

Each department or floor gets its own display — any TV or tablet already in the building — showing that department's now-serving token and announcing it out loud. In a hospital lobby, ambient noise and larger crowds make the audio call genuinely useful, not just a nice-to-have: patients waiting three rows back can still hear their number without straining to read a screen.

What TOKENN deliberately does not do

It does not manage IPD admissions, bed allocation, discharge summaries, billing, insurance claims or EMR records, and it does not integrate with your existing HIS — by design, not by limitation. Hospitals evaluating queue software are often mid-way through, or wary of, a much larger HIS procurement; TOKENN sits entirely outside that decision. It runs on its own, alongside whatever hospital information system you have or plan to get, and never touches patient medical records.

Rolling out across an OPD block without an IT project

Hospital software procurement is normally a months-long cycle — vendor integration, IT sign-off, staff training across shifts. TOKENN skips all of it because there's nothing to integrate: each department is configured independently in minutes, using the WhatsApp Business number the hospital may already have. A pilot department can go live in an afternoon; the rest follow once reception sees it working.

Pricing for a multi-department hospital OPD

Pro plan covers up to 500 tokens/day and 15,000 WhatsApp messages/month per clinic account, with unlimited staff and departments configured independently — most eight-to-ten-department OPD blocks fit comfortably inside one Pro account. Hospitals with genuinely high footfall (1,000+ OPD visits/day) or multiple physical buildings should talk to us directly; we scale message and token limits per-department rather than charging a flat hospital-wide premium.

What changes for hospital reception and floor staff

Before: a general enquiry counter fielding "which counter for cardiology" a hundred times a morning, plus department counters each running their own paper system with no visibility into each other. After: every counter sees every department's queue on one dashboard, walk-ins get routed and ticketed in two taps, and the enquiry counter's workload drops to the genuinely unusual cases — a patient with no clear department, a language the AI flags as unclear, a same-day emergency walk-in.

Daily analytics across every department

Hospital OPD administrators get a consolidated view — total patients seen, no-show rate and average wait across the whole block — plus a per-department breakdown that individual clinics never had reason to build. Over a few weeks this surfaces which departments are genuinely overloaded versus which just feel busy, turning a staffing decision that used to run on complaints and guesswork into something the dashboard can actually answer.

Nursing homes and mid-size hospitals without a full HIS

Not every hospital searching for a queue management system already runs a hospital information system — plenty of nursing homes and 30-60 bed private hospitals in India still run OPD registration on a paper register or a basic billing tool, with no plans to buy an enterprise HIS soon. For these, TOKENN isn't a layer alongside a bigger system — it can be the entire OPD queue solution, department-wise, without waiting for a future HIS purchase to justify starting.

Why hospital OPD blocks resist the kiosk-and-ticket approach

The kiosk-and-printed-ticket model common in government and larger private hospitals solves the "what number am I" question but does nothing for "when should I actually walk into the building." Patients still arrive early and crowd the lobby around the kiosk itself, defeating the point of a numbered queue. A queue system that reaches patients on WhatsApp before they leave home is the only version that actually thins a hospital lobby rather than just organizing the crowd already inside it.

Frequently asked questions

Does TOKENN replace our HIS or hospital management software?

No. TOKENN manages the outpatient queue and WhatsApp booking only — it doesn't touch admissions, billing, bed management or medical records, and needs no integration with your HIS.

Can it handle IPD or admissions?

No — TOKENN is OPD-only, by design. If you need IPD or ward management, that stays with your HIS; TOKENN runs alongside it purely for the outpatient queue.

How many departments can it handle?

As many as your hospital runs. Each department gets its own token series, hours and QR, configured independently in minutes.

Can patients be routed to the right department automatically?

Yes — the AI asks a short clarifying question if it isn't obvious, or the patient scans that department's own QR to book directly into it.

What happens when one department refers a patient to another mid-visit?

The original token is parked in an awaiting-return lane; the patient rejoins the same token once the referred department is done — no second queue.

Do we need separate hardware for every floor or department?

No — any existing TV or tablet becomes that department's display, showing its own now-serving token and calling it out loud.

Can more than one registration counter feed the same queue?

Yes — every counter sees and issues into every department's live queue, whether it's the main lobby desk or a satellite counter on another floor.

Is patient data safe?

TOKENN only ever holds token, queue and WhatsApp contact data — never medical records. Encrypted at rest (AES-256), hosted in India, daily backups.