How to Train Your Staff on ServQueue (A 30-Minute Runbook for Business Owners)

You've done the hard part. You signed up, set the average service time, printed the QR code, and put it on the counter. ServQueue is ready to go.

Then your staff revert to the clipboard.

Not because they're difficult. Because nobody showed them the right way in the right order. They had a look at the dashboard, it felt unfamiliar, and they fell back on what they knew. It happens at almost every business in the first week — and it's entirely preventable with a single 30-minute training session run the right way.

This is that runbook.

Before you start: three things to have ready

Don't wing the setup. Have these in place before you call the team together:

1. The dashboard open on your till tablet or a shared device. Staff need to see it on the screen they'll actually use, not your phone.
2. The QR code visible at the counter. You're going to demo a customer joining live. It needs to be scannable.
3. Your own phone ready to play the customer. Scan the QR yourself during the session so staff see exactly what a customer experiences when they join.

If you have a second phone or can borrow one from a staff member, use it — watching a real join happen in real time lands better than any description.

The 30-minute session

Minutes 0–5: Show them what the customer sees first

Start here, not with the dashboard. Staff who understand the customer side use the operator side correctly. Staff who start with the dashboard often treat it like a spreadsheet — something to look at, not something to act on.

Scan the QR code with your phone. Let the page load. Walk them through what a customer sees:

• Their position in the queue
• Their estimated wait time
• The chat box where they can message you
• The notification they'll get when it's their turn

This takes three minutes. It answers the question every staff member has but won't ask out loud: "What is this actually for?"

Minutes 5–15: Walk through the dashboard live

Now open the dashboard and go through the four actions they'll use every single shift:

Call Next — tap this when you're ready for the next customer. ServQueue sends them an SMS and updates their screen. They walk in. That's the whole loop.

Mark Served — tap this when you're done with a customer. This is the one people forget. If they don't mark served, the queue count is wrong all day, wait estimates drift, and customers start arriving late because the app told them they had more time.

Skip — tap this if a customer doesn't show up when called. They go to the back of the queue. Use it freely — it's not punishing anyone, it just keeps the line moving.

Add manually — if someone walks in and doesn't scan (older customers, people in a rush), your staff can add them to the queue from the dashboard. Name optional. Takes five seconds.

Run through each one live. Have a staff member do it themselves on the tablet while you watch. Muscle memory beats explanation every time.

Minutes 15–20: Chat

The chat feature is where businesses get surprised — in a good way. Customers can message you from the queue page while they wait. Staff can reply from the dashboard.

Show them:

• Where incoming messages appear (the orange notification dot on the customer card)
• How to reply (tap the card, type, send)
• When to use it: answering a question ("can you do a full colour today?"), giving an update ("running about 10 minutes behind, sorry"), or telling someone they're nearly up

The rule to give your staff: if you'd normally walk out to the waiting area to tell a customer something, send it as a chat instead. That's it.

Minutes 20–25: SMS broadcast

This one is for unusual situations — not day-to-day use. If you're running 20 minutes behind because of a no-show, or you're closing early because the hot water went out, you can send a single SMS to every customer currently in the queue at once.

Show them where it is. Explain when to use it. Then give them the rule: broadcast is for situations that affect everyone in the queue at once. It's not for individual updates — use chat for that.

Most businesses use broadcast once or twice a week at most. Some never use it. But staff need to know it exists so they don't panic when something goes wrong.

Minutes 25–30: Edge cases

Cover the three situations that cause the most confusion on day one:

"A customer joined but I can't see them." Tell them to refresh the dashboard. It updates in real time but an occasional manual refresh clears any doubt.

"The queue is really backed up." Keep calling next at your normal pace. The wait time estimates update automatically as you move through the queue. Customers can see the live estimate — they're not waiting blind.

"What do we do at close?" Stop adding people to the queue about 15 minutes before close. Mark any remaining customers as served when you're done with them. The queue resets overnight — you don't need to manually clear it.

The two mistakes that happen most in week one

Calling customers by shouting instead of tapping Call Next. It feels faster in the moment. It isn't — it means the customer's app doesn't update, they don't get the SMS, and they think they're still waiting when their name has already been called. Every time staff skip Call Next, someone walks out confused.

Forgetting to mark served. This one compounds. By mid-afternoon the queue count is four people ahead of where it should be, wait estimates are 30 minutes off, and customers are arriving early because the app told them they'd be next 20 minutes ago. Drill mark served from day one.

Quick-reference sheet for the counter

Print this and stick it near the till for the first two weeks:

---

ServQueue — 5 actions, every shift

1. Customer arrives → they scan the QR and join themselves
2. You're ready → tap Call Next (they get an SMS automatically)
3. They don't show → tap Skip (they go to the back)
4. You're done → tap Mark Served (do this every time)
5. They didn't scan → tap Add Manually on the dashboard

Chat = message one customer | Broadcast = message everyone at once

---

Day two

Let your staff run the queue unsupervised for a full shift. Don't hover. At the end of the day, ask two questions: what felt awkward, and was there anything they weren't sure how to handle?

Almost every business finds the same answer: the first day felt unfamiliar, the second day felt fine. The unfamiliarity is the training gap closing — not a sign that something is wrong with the system.

By day three, most teams stop thinking about it. The queue just runs.