All articles

Operations

How to Transfer a Queue Ticket Between Services

A transfer keeps the Ticket number and moves the visitor to another Service, at the back of that line. It is a different action from Return to queue and from handing them to another Counter.

· Esperaly Editorial · 10 min read

Transfer a queue ticket between Services when the visitor joined the wrong line, or when the next step of the visit is a different desk. The Ticket number stays. The Counter that had them lets go. They go back to waiting, at the back of the Service you named, behind the people already standing in that line.

That is a floor action, not a design question. When to split queue Services decides whether “questions” and “filings” should be separate lines in the first place. Calling the next Ticket is the ordinary loop once someone is in the right line. Transfer is the move you make after the Ticket already exists and the Service on it is wrong, or finished.

Esperaly keeps the same three words. A visitor joins a Service, holds a Ticket, and staff work that Ticket at a Counter. Transfer changes the Service on that Ticket. It does not mint a second number, book a time, or write a chart.

When the transfer is the right move

Use it in two situations. Both are common on a walk-in desk, and both get messy when staff invent a side list instead.

  • They joined the wrong Service. The poster offered “Questions” and “Permits.” They tapped Questions because it was first. The work is a permit. Move the Ticket. Do not cancel it and ask them to scan again unless they want a new number.
  • The visit has a second step that is a different Service. Triage heard the question. The actual filing happens on another Service, with its own waiting order. A permit desk that splits application types is the pattern in permit and licensing queues. Transfer is how the first Counter hands the same Ticket across, instead of a sticky note on the second window.

Say the reason out loud before you move them. “This is a permit, so I’m putting A14 on the Permits line. Your number stays A14. You will wait behind whoever is already there.” People accept a new wait when the number they are holding still means something. They do not accept a whispered rewrite of the list.

Leave the Ticket where it is when the Service is already right and they only need a moment. Stepping away to find a form is a pause, not a new line. Sending them to a different Service to “help them along” puts them behind a room of people who have been waiting for that other job.

What changes on the Ticket, and what stays

From the Counter you are managing, open the Ticket, choose More, then Another service, and pick the destination. Four things follow from that action.

  1. The number stays. A14 is still A14 on the phone, on the wall, and in the activity. You are not issuing a replacement.
  2. The Ticket goes back to waiting. It is no longer called or being served at the Counter that moved it. That Counter is clear to call someone else.
  3. They join the back of the destination Service. The place in line is the time of the transfer. People already waiting on that Service stay ahead. An empty destination line means they are next, which the phone shows as zero people ahead, until a Counter calls them.
  4. The activity records the move. Open the Ticket’s activity and you should see a line such as “Transferred to Permits,” using the Service name you picked. That is the record when someone later asks who moved them.

The phone page follows the Ticket while they keep it open. The Service name changes. The people-ahead count and the estimated wait, if you leave the estimate on, are for the new Service. The “Joined” time on that page is still when they first took the Ticket, not the minute you transferred them. Tell them that, or they will argue with a timestamp that is doing a different job. How that page behaves is covered in phone queue tickets without SMS. Nothing is texted. If the tab is closed, the wall is the backup.

A display follows the Service it is scoped to. After the transfer, the Ticket is waiting on the new Service, so a board for that Service can show it. A board limited to the old Service should stop treating the number as called at the old Counter. If the room cannot see the new line, fix the board’s Service list before you blame the visitor for missing the call. The setup for that screen is in queue display board software.

Three moves that look alike from the chair

All three live in the same menu. The visitor hears a different promise from each one. Train one sentence per action, then rehearse it.

  • Transfer to another Service. The Service name changes. The Ticket waits at the back of the new line. Activity says “Transferred to” that Service. Use this for a wrong join or a real second step.
  • Return to queue. The Service stays the same. The Ticket goes to the front of that line, and the activity says “Returned to the front of the queue.” Use this when you called them, they were genuinely a few steps away, and your published recall rule says they keep their place. It is a strong action. Using it to apologise for a slow Counter lets one Ticket pass everyone who waited fairly. Missed calls and abandonment sit in reducing walk-in queue no-shows, which is the policy for people who do not come back. Return to queue is not that policy.
  • Move to another Counter. The Service stays the same. You are handing the Ticket to a different window. If they were still waiting, that Counter calls them. If they were already called, the call moves with them. Use this when the right Service is already on the Ticket and the wrong thing is which window is free. Several windows on one Service are the multi-counter setup.

Read the activity line aloud before you rely on the habit. “Transferred to Permits” is easy to defend. “Returned to the front of the queue” needs the recall rule you already posted. “Moved to” a Counter should name a window that was actually free.

The Counter has to be allowed to serve both Services

Transfer is refused when the Counter you are managing cannot see the destination. An open Counter, one assigned to every Service at the location, can move a Ticket to any of them. A Counter limited to a list can transfer only into a Service on that list, and only from a Service that is also on that list. A window that only handles Questions cannot send someone to Permits until Permits is on that Counter’s list, or until a Counter that covers both does the move.

You also have to be managing the Counter. Starting the session is part of the same habit as call-next. A Ticket menu opened from somewhere else is not a back door around that.

The Another service item appears when the location has a second Service to offer. One Service means there is nowhere to transfer to. If every visit is two jobs and you only named one Service, fix the names before you train the button. The checklist is in when to split queue Services. A council lobby and a clinic lobby use the same Ticket loop; government desks change the Service names, not the handoff.

Check the destination before you commit. If no Counter for that Service is staffed, the Ticket will wait with an honest people-ahead count and nowhere to be called. That is a staffing problem, which how many Counters you need is for. Transfer will not open a closed window.

What to say, and what to stop doing beside the line

Write a script short enough to use while someone is standing there. Something in this shape works:

  1. Name the number and the Service they are on now.
  2. Name the Service you are moving them to, and why.
  3. Say that the number stays, and that they wait behind people already on the new Service.
  4. Point at the phone page or the board they should watch next. If the page is closed, they will not get a chime about the move.

Then stop the side systems that transfer is meant to replace:

  • A second Ticket “so the other desk can see them.” Two live numbers for one person is how the room loses trust. Cancel only if they ask to leave, or if the first Ticket was a mistake you are voiding on purpose.
  • A paper list of names at the second window. The second Counter should call the transferred Ticket in the new Service’s order.
  • A promise that they “keep their place.” They keep the number. They do not keep a position ahead of people who joined the destination Service earlier. If you need them at the front of the same Service, that is Return to queue, and you should be ready to explain it.
  • A note in a clinical chart or a booking calendar as the handoff. The handoff is the Ticket. A clinic can still keep its own record elsewhere. The queue does not become that record, and it does not become the appointment book.

What a transfer will not fix

  • Unfair Service design. A two-minute question and a thirty-minute filing on one line stay unfair if you only move the occasional person. Split the Services, or staff the single line.
  • Skipping ahead. The destination place is the back of that line. The activity will still name the Service you chose.
  • A missed call on the right Service. Use the recall habit you already trained, or Return to queue when the posted rule keeps them at the front. Moving them onto a quieter Service to be kind takes that line from the people waiting there.
  • A closed destination. If nobody is managing a Counter for the new Service, the Ticket waits with a true people-ahead count and no one to call it.
  • A board the room cannot see. When the new Service is missing from the display and the phone page is closed, the call is hidden. Put the Service on a board, or name the screen they should watch.

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.

  1. Name two Services a visitor would recognise. Assign one Counter to both, and a second Counter to only the first Service.
  2. Join each Service from a phone. On the open Counter, move the first Ticket to the second Service. The number stays, that Counter is free, the activity says “Transferred to” the new Service, and the phone shows the new name with a people-ahead count for who was already waiting there. The “Joined” time stays the original one.
  3. From the Counter that only serves the first Service, try the same move. It should refuse. Widen that Counter’s Service list, or make the move from a Counter that covers both.
  4. Return one Ticket to the queue and read the activity aloud. It should say they went to the front. If that would cause a complaint, you wanted a transfer.
  5. Call the transferred Ticket from a Counter on the new Service and match the number on the display.

If the people-ahead count surprises you, look at who was already waiting on the destination. The count is that line. 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.

Move the Ticket, then say the new line out loud

Transfer when the Service on the Ticket is wrong or the next step is a different Service. Keep the number. Put them at the back of the new line. Tell them that, and point at the page or the board that will show the call. Use Return to queue only when you mean the front of the same line. Use another Counter when the Service was already right.

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.