SWIQ is a booking and queue-management tool built for Indian and US service businesses, and how the SWIQ live token queue works in one sentence: customers join a numbered queue remotely or at the door, see their live position on their phone, and get told when to walk in. It is the bank-token idea, digitised so the queue can be watched from anywhere - home, the car, the chai stall. Nothing about the service gets faster; what disappears is the crowding, the repeated 'how much longer' questions, and customers who leave because they cannot tell where they stood.
Key takeaways
- The loop: a customer scans a QR or opens a link, takes a token, watches their live position, and arrives when called.
- The business side sees one screen: the number being served, who is waiting, and how long waits actually run.
- Turn updates by WhatsApp or SMS let customers wait elsewhere, which shrinks the lobby without shrinking business.
- SWIQ also handles bookings and reminders, so appointment customers and walk-ins share one honest sequence.
The 30-second version of live tokens
Every customer who wants service joins one numbered sequence, whether they are standing at the door or sitting at home. The system issues the next number, shows everyone the same live state - 'now serving B-07, about 20 minutes of waiting' - and messages the customer when their turn approaches. The business runs the counter from one screen; the customer carries the queue in a pocket. Both sides see the same order, which is also what makes it feel fair: the sequence cannot be quietly broken the way a paper pile or a shouted list can. For the wider mechanics this pattern comes from, see how live token systems reduce waiting confusion.
The sequence also handles exceptions cleanly: an emergency can be called forward without rewriting the list, because the order is visible to everyone at once. Staff who used to hold the queue in their head get that time back, which in a two-person shop is the difference between a calm hour and a chaotic one. Customers who leave and come back keep their place, since the number travels with them rather than with a chair in the room. Nothing in the flow requires anyone to install anything, which is why it works for the customer who visits once a year.
The flow, step by step
- The business sets up a queue - a service, hours, and the counter that serves it. A QR code and a shareable link are generated.
- The customer joins - by scanning the QR at the door or opening the link, and submitting a short form (name, phone, service).
- A token is issued - the next number in sequence, confirmed on screen and by WhatsApp or SMS.
- The position stays live - the customer sees their place and the number being served, on their phone and on the business's screen.
- The turn update fires - when the customer is close, they get a message, so they can walk in instead of waiting in the room.
- The wait is recorded - issue time and service time are stamped, giving the business its real wait numbers afterwards.
Each step is reversible: a customer who cannot scan can be issued a token at the desk, and the sequence stays intact. The link works in any phone browser, so a shared WhatsApp message is enough to join without a QR in sight. Setup for a single service takes minutes, which is why most businesses start with their busiest offering and add the rest later.
One caveat before you start: live tokens do not fix a schedule booked with unrealistic durations, so honest slot lengths come before the queue publishes them.
What the business sees
One screen at the counter, backed by the numbers that matter afterwards:
- Now serving: the token on screen, so nobody has to ask.
- Waiting list: who is next, in strict order.
- Estimated wait: derived from the last ten customers' actual times, not a guess.
- Weekly stats: average wait, worst hour, tokens issued vs served, walkaways.
Bookings and walk-ins live in the same sequence, so a late appointment and a walk-in interleave predictably instead of arguing. Reminders for booked customers ride the same system, which is what keeps the day from sliding later and later.
One screen means one source of truth: nobody has to ask the colleague at the far end who is next. Because the wait is recorded automatically, an argument about how long someone waited becomes a question with an answer instead of a memory contest. The weekly view also shows when to open a second counter, because the worst hour tells you where staff rather than software are the constraint.
One honest boundary for owners: the dashboard is not a substitute for the hospital portals covered in our Rajasthan guides, where iHMS, ORS and ABHA flows run on the hospitals' own schedules.
What the customer sees
Three things, in order of how much they matter. First, position: 'you are A-14, four ahead.' Second, an estimate they can plan a chai run around. Third, the message that says it is time. That is the entire experience - no app install, no account, no queue diplomacy at the door. Customers who can see the queue stop asking staff about the queue, which is the interruption saving that makes the whole system worth it for a two-person shop. The psychology behind why an honest moving estimate feels shorter than a vague static one is covered in the psychology of waiting.
A position that moves is what makes waiting bearable, because uncertainty is heavier than the wait itself. Customers who can step away come back without losing their place, which shrinks the lobby without shrinking the business. For someone accompanying a patient, a parent or a child, that freedom is often the entire value of the token.
What live tokens are not - honestly
Some honest boundaries. Live tokens do not make a service faster; they remove the confusion and crowding around it. They are not a hospital-grade system by default - the token flows described in our Rajasthan guides (SMS Jaipur, AIIMS Jodhpur, MG Hospital Jodhpur) run on government portals and ABHA, and SWIQ is not affiliated with or endorsed by any hospital, lab or salon. Directory listings on SWIQ are listings, not endorsements. And SWIQ itself is simply the tool in this article: a live token queue, an online booking page, and reminders a small business runs from a phone. Processes and features change, so check the current product and any business listing on the day you rely on them.
Frequently asked questions
Do customers need an app to use SWIQ live tokens?
No. Customers join by scanning a QR code or opening a link in their phone browser, and receive their token and turn update by WhatsApp or SMS. Nothing to install is a deliberate design choice, because walk-in customers will not install anything.
How does the business know when to call a customer?
The counter screen shows the current number and the waiting list; staff serve in order and mark each token served. The turn update to the next few customers fires automatically as the queue advances.
Can SWIQ handle appointments and walk-ins together?
Yes - booked customers and walk-in tokens share one sequence, so they interleave predictably instead of competing. Reminders for booked customers go out on the same system.
What happens if a customer does not show up?
The token is marked as a walkaway in the system, which makes it countable rather than invisible. Walkaway counts are one of the four numbers that tell a business whether its waits are actually shrinking.
Does SWIQ work outside Rajasthan?
SWIQ is built for service businesses in India and the USA. The Rajasthan examples on this blog illustrate the pattern with real local institutions; the product itself runs anywhere a business has a phone and a counter.
See SWIQ in action
SWIQ live tokens, bookings and reminders run from the phone you already own - launch the SWIQ web app and set up your first queue in minutes.
Launch the SWIQ web app