Operations
Return a Queue Ticket to the Front of the Line
Return to queue sends a called Ticket back to waiting at the front of the same Service. The number stays. The next Call next takes them ahead of people who have been waiting.
· Esperaly Editorial · 10 min read
Return a queue ticket to the front when you already called the visitor, they were only a few steps away, and the rule you posted says they keep the next place. The Ticket number stays. The Service stays. The Counter lets go of them. They go back to waiting, ahead of everyone still waiting, and the next Call next that can serve that Service takes them.
That is a floor action with a sharp edge. Transferring a Ticket between Services keeps the number and puts them at the back of a different line. Reducing walk-in no-shows is the policy for people who leave. Calling the next Ticket is the ordinary loop. Return to queue is the button you press when the Service was already right and the promise is the front of that same line.
Esperaly keeps the same three words. A visitor joins a Service, holds a Ticket, and staff work that Ticket at a Counter. Return to queue does not mint a second number, book a time, or write a chart.
When the front of the line is the right promise
Use it only when you can say the reason out loud and the people still waiting would accept it. Three situations cover almost every honest use.
- You called them a moment too soon. The number is on the board, they are in the restroom or the car park or still reading the poster, and your recall window is still open. Putting them at the front means the next call is the same number, not a stranger who happened to be standing closer to the desk.
- You marked them missed, and they came back inside the window you posted. Missed means they are out of the waiting line. Call next moves on to whoever is still waiting. Return to queue, from the missed row, is how you bring that number back to the front without issuing a new one.
- The Counter was not actually free. You called, then realised the window still had a form to finish or the right person was not at the desk. Send the Ticket back to the front and clear the Counter, instead of asking the visitor to pretend the call did not happen.
What changes on the Ticket, and what stays
From the Counter, open the Ticket, choose More, then Return to queue. On a missed Ticket the same words are the main button on that row. The location’s ticket list has the action too. Four things follow.
- The number stays. A14 is still A14 on the phone, on the wall, and in the activity. You are not issuing a replacement.
- The Service stays. Return does not rename the line. If the work belongs on a different Service, this is the wrong button.
- They go back to waiting, and the Counter lets go. The window that was holding the Ticket is clear to call. The Ticket is no longer the one that window is serving.
- The activity records the promise. Open the Ticket’s activity and you should see “Returned to the front of the queue.” Read that line before you defend the decision. If you cannot say it to the room, you wanted a different action.
The phone page follows the Ticket while they keep it open. The Service name does not change. The “Joined” time is still when they first took the Ticket, not the minute you returned them. The people-ahead count drops to zero, unless a later return on that Service is already ahead of them, and the default waiting label is “You’re next.” A short estimate can still sit beside that zero when a Counter is busy with someone else. Zero people ahead means they are first in this Service’s waiting order. It does not mean a free window is standing idle. How that page behaves, including the fact that nothing is texted, is in phone queue tickets without SMS. Alerts on the phone are off unless that visitor turned them on for this Ticket. A closed tab gets no chime and no text.
The wall stops showing the number as now serving, because they are waiting again. Do not then point at the waiting strip and promise it matches the next call. That strip is ordered by the latest status change, so a Ticket you just returned can sit at the end of the visible waiting list, or on a later page of it, even though Call next will take them first. The phone’s people-ahead count is the place in line. The board’s job after a return is to stop claiming they are at the Counter. The setup for that screen is in queue display board software.
Who Call next takes after you press it
Call next on a Counter that can serve their Service takes the returned Ticket before anyone who is only waiting. That includes people waiting on a different Service, when this Counter is assigned to those Services too. A Counter that cannot serve their Service never sees them. The phone only counts the same Service, so it can read zero people ahead on Permits while that Counter also has a Questions line. For that window, the returned Permits Ticket is ahead of Questions. A Counter limited to Permits does not change the Questions order. If that jump would be unfair, narrow the Counter’s Service list, or transfer them to the back of the other Service instead. Splitting the work is covered in when to split queue Services. Several windows on one Service are the multi-counter setup.
Two returns do not share the front. The later Return to queue is the next Call next. The earlier one waits behind that later return, and both still wait ahead of people who simply joined. Pressing it twice to “be fair” to two latecomers puts the second one in front of the first. If you cannot explain that order, do not stack the button.
Return only releases the Ticket you applied it to. Using it on a Ticket another window is serving takes that visit off their Counter. Do that when that window asked you to, not because the row was easy to reach.
What to say, and what to stop doing beside the line
Write a script short enough to use while someone is standing there.
- Name the number and the Service, which is not changing.
- Say you are putting them at the front, and that the number stays.
- Say that people still waiting on this Service will be behind them. If this Counter also calls another Service, say that too, in plain words: the next call at this window will be their number.
- Point at the phone page, not at the waiting strip on the board. If the page is closed, they will not get a text when you press the button, and they will not see the count change until they open it.
Then stop the side systems this button is meant to replace:
- A paper “they were next” note at the window. The next Call next already has that job. A second list is how two people get told they are first.
- A new Ticket “so the board looks right.” A second live number for one person is how the room loses trust. Cancel only if they ask to leave, or if you are voiding the first Ticket on purpose.
- A note in a chart or a booking calendar as the way back. The way back is the Ticket. The queue does not become the record, and it does not become the appointment book.
When it is the wrong button
- The Service is wrong, or the next step is a different desk. Transfer them. They keep the number and wait at the back of the destination Service, behind people already there. Return to queue would leave them on the wrong line and put them at the front of it.
- They came back after the recall window you posted. Do not jump the people who stayed. The script in staff training is the right one: rejoin for a new Ticket so the new number waits at the back. Return to queue is the opposite of that rejoin. One recall inside the window can be this button. A second chance after they left is a new join. Post that where people take a Ticket, so staff are not inventing it mid-argument.
- You want another window to take them while they stay called. Putting them back in the waiting line is not a handoff. The three moves that look alike from the chair — transfer, return to the front, and handing the Ticket to another Counter — are separated in the transfer article. This button always means waiting, at the front.
- You are apologising for a slow Counter, or a friend asked to skip. Return to queue lets one Ticket pass everyone who waited fairly, including on other Services this Counter calls. That is a strong action. It is not a courtesy button. The same pressure shows up as a side clipboard. The answer is still the posted order.
- They are already waiting and were never called. The ticket list will still offer Return to queue. Using it on that row jumps someone who has not missed a call. That is a side list with a cleaner name. Leave waiting Tickets in the order they joined unless you are undoing a call you just made.
Missed means staff called the Ticket and nobody was served. If you return them and then complete the visit, they were served, and the activity still shows the return. Do not treat the button as a way to hide a call you do not want to explain. The weekly missed count is defined in queue management KPIs for a walk-in desk.
Practice it once before a real morning
Ten minutes with two test Tickets teaches the menu better than a paragraph in the handbook. Do it on the Counter staff will actually manage.
- Join the same Service twice from two phones, a minute apart. Call the later number.
- More, then Return to queue. The activity should say “Returned to the front of the queue.” That Counter should be clear. The phone should show zero people ahead and the same number, with the original Joined time. The earlier Ticket is still waiting.
- Call next. You should get the returned number, not the one that has been waiting longer. If you get the earlier number, stop and read the activity before you train anyone.
- If this Counter also serves a second Service, join that Service from a third phone before you return anyone. After the return, Call next should still take the returned Ticket, ahead of the other Service. If that surprise is unacceptable, narrow the Counter’s Service list before you open the doors.
- Return a second called Ticket and Call next again. The later return comes first. The earlier return waits behind it. If you would not say that sentence to both people, you wanted one of them to rejoin at the back.
A planning pass for a busy hour still belongs in the wait-time estimator before you open, not as a promise made with the menu open.
Front of the same line, or leave the button alone
Return a queue ticket to the front when the Service was already right and your posted recall rule says they keep the next place. Keep the number. Clear the Counter. Tell them they are ahead of the people still waiting, and point at the phone page. Use transfer when the Service is wrong. Use a new Ticket when they came back after the window. Do not stack two returns and call it fair.
The rest of the desk — join, call-next, displays, and the Ticket actions — is on features. 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.