
On this page
- The problem in one scene
- The flow, step by step
- 1. Booking by department, then doctor
- 2. Token issued by SMS or WhatsApp
- 3. Arrival check-in from the patient’s phone
- 4. The desk calls the next token
- 5. Waiting patients can see their place
- Where queues break
- What the front desk actually needs on screen
- Set-up checklist
- For clinics already running tokens
The queue outside a clinic is not a staffing problem. It is an information problem. Nobody knows how many people are ahead of them, so everybody stands at the counter to find out.
An OPD token system fixes that with one number per patient. Here is what the flow looks like end to end.
The problem in one scene
It is 10am. Forty people are in the waiting area. The desk is answering questions that are not medical:
- “Meri baari kab aayegi?” (When is my turn?)
- “Doctor aa gaye hain?” (Has the doctor arrived?)
- “Main abhi aaya hoon, token milega?” (I just arrived, can I get a token?)
Every answer takes two minutes and stops the queue. Meanwhile the phone rings with a patient who wants to know whether it is worth coming now.
The flow, step by step
1. Booking by department, then doctor
The patient messages the clinic number. The system asks for the department first, then the doctor, then a time that doctor actually has free.
Department first matters. A patient who wants “a heart doctor” does not know the consultant’s name, but they know what is wrong.
2. Token issued by SMS or WhatsApp
The confirmation carries three things: the token number, the approximate time, and the doctor’s name.
The number is what people hold on to. It replaces the question “where am I in the line?” with a glance at the phone.
3. Arrival check-in from the patient’s phone
On the day, the message has an “I’ve arrived” button. Tapping it checks the patient in and issues today’s token — without joining the counter queue to announce that they exist.
This is the single biggest time-saver at the desk.
4. The desk calls the next token
The front desk sees a queue, not a crowd: who has arrived, who has not, whose turn is next. When the doctor is ready, the next token is called.
5. Waiting patients can see their place
The patient can check how many are ahead. When it drops to two, they can leave the tea stall and come back.
Where queues break
Walk-ins with no token. Someone arrives without booking and expects to be seen. Decide the rule in advance — a separate walk-in slot, or the next available token — and write it where the desk can see it.
Doctors running late. Every token downstream shifts. If the system does not update times, patients arrive at the old time and blame the desk.
No-shows with early tokens. Two empty slots at 11am waste a whole hour. A quick “running late?” message at 30 minutes before the slot usually recovers half of them.
The patient who will not use a phone. Some will always want to speak to a person. Keep the phone line open for them. A token system should remove work, not refuse patients.
What the front desk actually needs on screen
Four things, nothing more:
- Today’s queue in order
- Who has arrived and who has not
- Which doctor each patient is waiting for
- A way to add a walk-in in ten seconds
Anything else is noise when there are forty people in the room.
Set-up checklist
- Departments and doctors listed, each doctor mapped to a department
- Slot length realistic — not every consultation is five minutes
- Emergency rule written and tested (emergencies never get a token)
- Walk-in rule written down
- Message templates in the language patients actually use
For clinics already running tokens
BittaFlow runs the whole flow: booking by department and doctor, OPD tokens over WhatsApp and SMS, an “I’ve arrived” check-in from the patient’s phone, and an AI receptionist that knows your doctors, so an after-hours call still ends in a booking. Pricing is per clinic, not per doctor or per booking.
The queue is still a queue. It just stops being a crowd at the counter.

