Operations

Let Guests Join the Queue First. Alerts Can Wait.

Jomqueue Team September 21, 2026 8 min read
Back to all posts
A guest is at the door with friends, hungry, ready. They will happily scan a QR. They may not want to set up a chat just to get a number. Let them join first. Alerts can wait — the queue should not.

A number should be easy to get

The job of join is simple: record who is next. Anything extra — a new app, a new chat, a long form — adds friction at the one moment people are already deciding whether to stay. The friendliest queues treat the ticket as the first win.
Alerts are wonderful. They are also optional. Guests who skip them are still in line. That is fairness, and it is good operations. A Saturday rush should feel like a scan and a smile, not a setup wizard.
Think of it like a queue number at a busy stall. You take the number first. You figure out how you want to be called after you already have it.

In line the moment they join

With Jomqueue, a public join puts the guest on the live list straight away. Staff can see them. The floor can plan. Nobody sits in a hidden "please connect first" state just to appear on the board.
Two friends can join together. One later connects Telegram. The other just watches the status page. Both keep the same fair place. That is the whole point of a digital queue: the ticket is the ticket.
After they are in, they can connect Telegram if they want updates there. On Android and desktop they can also enable browser alerts. Both are extras on top of a ticket they already hold. Read more about that guest-first wait in Queue Is Not the Product. Time Is.

Situation: join now, alerts when you are ready

Scan. You are in the queue. Later, if you like, tap Connect Telegram or turn on browser notifications. iPhone guests skip the browser-push prompt — Telegram stays optional. The ticket does not depend on either step.

Optional Telegram, optional browser alerts

Telegram is a great add-on for people who already live there. Browser alerts are handy on Android and desktop. Neither should block the join. Guests who only want the status page can refresh it. Guests who want a ping can add one. Same queue. Same energy at the door.
iPhone in the browser is a little different: there is no browser-push prompt, and that is fine. Telegram can still be connected if they want it. Native app guests get the app experience. The important part is the same everywhere — they already joined.
That is how you keep a busy Saturday moving without turning join into homework. See features and the Malaysian classic Berapa Lagik? for why a number they can check beats a question they have to shout.

Staff still see them. Calling still works.

Optional alerts are for the guest. Visibility is for the team. Once they join, they are on the operator list. When you call them, the floor still runs. If they later connect Telegram, catch-up can help. If they never do, they still had a fair place in line.
Join first. Notify when they opt in. Keep the welcome bright — and keep the queue honest.

Key takeaways

  • The ticket comes first. Alerts are optional extras.
  • Guests are live on the staff list as soon as they join.
  • Telegram and browser alerts can be added after — iPhone skips browser push.
  • See it in a demo

Ready to Transform Your Queue Management?

Join hundreds of Malaysian businesses using Jomqueue to improve customer experience.
Get Started Free