All articles

Guides

Phone Queue Tickets Without SMS

A phone queue ticket is a live browser page: your number, people ahead, and the Counter that called you. No app install, no text pack, and the page has to stay open.

· Esperaly Editorial · 9 min read

A phone queue ticket is the visitor’s live Ticket in the mobile browser: their number, how many people are ahead, and the Counter that calls them. They already unlocked the phone to scan a QR. The same page is the ticket. There is no app to install and no SMS pack to buy.

This is a different job from virtual queue vs walk-in ticket queue. That guide compares two ways of waiting: stay in the room, or leave and come back. This one is about the object in the hand. It is also different from paper ticket vs QR, which is about how someone joins, and from queue display board software, which is the screen on the wall. The phone page, the wall, and the Counter should all show the same call.

Esperaly’s model stays Ticket, Counter, and Service. A visitor joins a named Service, gets a Ticket, and staff call the next Ticket at a Counter. The phone is a window onto that loop. It is not a second waitlist, a texting product, or a clinical record.

What the waiting page actually shows

After someone joins, the Ticket page opens on their phone. While they are waiting it leads with their number, then the facts that stop them walking back to the desk to ask “am I next?”

  • The Ticket number, large enough to read at arm’s length. That number is what the Counter calls and what a wall display should repeat.
  • People ahead. The count is on the page the whole time they are waiting. Zero people ahead is labelled as next, before a Counter has called them.
  • Service and join time. “Permits · Joined 10:14” tells a household with two Tickets which page belongs to which errand.
  • An estimated wait, when the desk leaves it on. The figure comes from how many people are ahead and how fast that Service has actually been moving, across the Counters staffed for it. A very short estimate shows as “Soon.” A long one caps at 60+ minutes rather than pretending to know the exact hour. The desk can hide the estimate. Position stays.
  • A short picture of the line, when the desk leaves it on. Now serving, a few numbers immediately ahead, their own number, and how many people are behind them. The desk can hide this strip. The people-ahead count stays.

Treat the estimate as a pace reading, not a promise you print on the door. If you need to decide whether the lobby can absorb a busy hour, use the wait-time estimator before you open, and check queue management KPIs after the week is over. The phone page is for the person in line. It is not your staffing model.

They can leave the queue from the page. That cancels the Ticket. It does not quietly hold a place for later. Say that out loud at the desk once, so “I still have the page open from this morning” is not a dispute.

Alerts work only while that page stays open

The alert channel is named for what it is: this browser. The visitor turns alerts on from the Ticket page. Esperaly can then chime, vibrate, and—if the phone allows site notifications—raise a system alert at two moments: when they become next, and when a Counter calls their number. The called alert names the Counter when the desk shows Counter names.

The page says the limit in plain language: alerts only work while this page stays open on the phone. Closing the tab ends the channel. A backgrounded tab can still raise a system notification when the browser has permission. Sound and vibration are for the open page. If the browser blocks notifications, the backup is sound and vibration while the page is in front of them, and the visitor has to allow notifications in the browser if they want an alert with the tab behind another app.

Phones also refuse sound until the person has tapped the page. That is a browser rule, not a queue setting. The button on the Ticket is there so the first tap both grants the alert and unlocks the chime. Opening an already-called Ticket does not buzz them again just because they refreshed.

None of that is an SMS. A text can arrive after the browser is gone, and some desks want that. It is a different product, usually priced per message or in a credit pack, and it fails when the number is wrong or the person is roaming. A phone queue ticket spends nothing per wait. The cost of that choice is operational: someone has to keep the page open, or look at a display, or both.

What the phone shows when a Counter calls

Calling the next Ticket at the Counter is what updates the phone. Staff do not send a separate message. The waiting page becomes a called page: “Go to” plus that Counter’s name, or “It’s your turn” if the desk has hidden Counter names. Their number, the Service, the Counter, and the time they were called sit on the same screen.

Once service starts, the page moves to being served at that Counter. When the visit ends, it shows the Ticket as completed. If they miss the call, the page says they missed their turn and offers a way to rejoin when the desk still allows a new join. Rejoin is a new place in line, not a silent restore of the old one. Pair that with the recall rules in reducing walk-in queue no-shows so the phone and the staff script describe the same recovery.

Order has to match the call. If staff shout a name the board did not call, the phone and the room disagree and the page stops being trusted by lunchtime. The five daily actions in staff training for call-next are the habit that keeps the phone honest.

Use the phone and the wall for different failures

A phone queue ticket helps the person who can step away: the pharmacy customer who walks an aisle, the parent who takes a child outside, the resident who sits in the car while a permit is prepared. The page follows them. A wall cannot.

The wall still earns its place. People lock phones. Batteries die. Some visitors never wanted a page. A waiting-room display on a television you already own shows the called Ticket to the room. Mount it where the waiting people can see it, and show the same Ticket characters the phone shows. A nickname on the wall and a number on the phone is how arguments start.

Show the Ticket number, not a full name. The privacy basics in QR Ticket privacy apply here too: the phone already belongs to the visitor, and the shared display is readable by everyone in the lobby. Collect less at join. The page does not need a date of birth to say how many people are ahead.

Healthcare, retail, and civic desks use the same pair of surfaces. The Service names change. The phone page stays a Ticket: it does not become a chart, a prescription, or a case file. See healthcare, retail, and government.

When a text pack is the wrong bill

SMS looks simple until the invoice arrives. A busy desk can send several messages per visit: joined, you are next, you are called, you missed us. At a few cents each, a morning of walk-ins is a line item. Failed delivery still costs staff time, because the person walks up and says the text never came.

A browser Ticket skips that meter. The visitor is already on the page they opened to join, and status updates are the same live queue the Counter is calling. You pay for the location, not for each wait. Current location pricing is on pricing.

Use SMS when people cannot keep a page open and you hold a reliable mobile number for each of them. Use the phone queue ticket when they joined on their own phone and can leave that tab alive. Many small desks do the second and keep a display for everyone else. If you are still comparing products that lead with message credits, read the small-business buyer guide and what to ignore when buying queue software. Message volume is a cost question. It is not proof that the line is fair.

Staff habits that keep the page trusted

The software can show the right number and still lose the room if the desk improvises. Four habits matter more than a new setting.

  1. Call from the Counter, in order, for that Service. The phone updates because the Counter called. A side conversation that serves someone out of order makes every open page look wrong.
  2. Name Services the way visitors choose them. “Pickup” and “New application” are choices. “General” is how two different jobs share one estimate and one people-ahead count. Split when the jobs differ, using when to split queue Services.
  3. Say what “next” means. Zero people ahead means they are next, not that a Counter is free this second. The call is a second moment. Tell staff that, or they will apologise for a page that was telling the truth.
  4. One recovery for a missed call. The page offers rejoin when a new Ticket is allowed. Staff should use that, not a handwritten exception list that the phone cannot see.

If the estimate is often wildly off, fix the line before you hide the number. A Service with no staffed Counter has nothing honest to estimate. A Service that mixes a two-minute question with a long interview will show a wait nobody recognises.

Set it up on a desk you already have

Print the Service QR and put it where people actually stop. They scan, pick the Service, and land on the Ticket page. That join path is QR join. The page they keep is phone tickets. A shared tablet is optional for people without a phone; it uses the same join, which is the trade-off in QR join vs a tablet kiosk. The first hour of setup is the same checklist as setting up a digital queue in under an hour.

Before the first real morning, walk one Ticket yourself:

  1. Scan the QR on the phone you will ask visitors to use.
  2. Confirm the number, the people-ahead count, and the Service name on the waiting page.
  3. Turn alerts on. Lock the phone with the page still open, then call the Ticket from the Counter. You should get the call alert, and the opened page should name the Counter.
  4. Close the tab and call a second test Ticket. Confirm that nothing arrives. That is the limit you will explain at the desk.
  5. Call the same number on the waiting-room display and check the characters match.

Add the display and a second Counter only after that loop is boring. Multi-window desks are covered on multi-counter. The phone does not change because you opened another window. It follows whichever Counter called the Ticket.

A phone queue ticket is a page you can point at

Give the visitor a number, a people-ahead count, and a call that names the Counter. Tell them to keep the page open. Put the same number on the wall for everyone who will not. Train the Counter to call in order. Skip the SMS pack unless you have measured that people leave and cannot keep a browser tab.

The product surface is phone tickets, next to features if you are still checking the rest of the desk. New workspaces are paused. Register your interest and we will email you when signup opens. Existing accounts can still sign in. The price, when signup is open, is a 14-day trial that requires a card, then $19 per location per month. Counters, staff, kiosks, and displays at that location are included. Cancel before the trial ends and you pay nothing. Details are on pricing.