NomoQ Book a demo

Queue management for clinics and restaurants

No more waiting.

Customers scan a QR, join from their phone, and walk away. The screen calls them when it is their turn.

Book a demo See how it works
Riverside Family Clinic OPEN10:42
Now serving 014 4 waiting, 13 served today

Scan to join the queue

Or ask at the counter.

0Installs requiredCustomers use their own browser
1 dayTicket stays on the phoneReopen the page and it is still there
24/7Boards run unattendedNo one has to walk over to them
90Days kept, then purgedTicket records and message logs

Four moves, and nobody stands in line.

The whole loop runs on the phone the customer already has, the board on the wall, and one console at the front desk.

1

Scan the counter QR

That code on the wall is the only way in. It is renewed every time the queue opens, so a code from an earlier session is refused.

2

Wait wherever you like

A live ticket page tracks their place in the queue. No countdown, no guesswork, and no need to keep an eye on the counter.

3

Get called

The board and the phone call them at the same moment, and a reminder goes out first so they have time to come back.

4

Seated or served

One tap clears the ticket. Every board moves up at once, so nobody has to ask what is next.

Three surfaces, one queue.

Every screen reads from the same live state, and every screen shows position rather than prediction. Call someone from the desk and the board, the ticket and the console all move in the same second. Between calls, each board runs your poster, video and promo text slots.

Riverside Family Clinic10:42 Now serving 014 Please proceed to the front desk OPEN 4 waiting

Display board

Riverside Family Clinic10:42

Now serving 014. 4 waiting, 13 served today.

Call next Recall a party

Being called

014Marisol DomingoServeNo show

Waiting

015Ramon Aquino
016Grace Villanueva
017Noel Marquez
018Ana Reyes

Staff console

Riverside Family Clinic

016
Waiting
1 ahead of youNow serving #014
We will call your number on the board.

Customer ticket

Alon Bistro OPEN 7:18 PM
Now serving 032 Party of four, come to the host stand

Scan to join the queue

Tonight

Chargrilled catch of the day, finished with calamansi butter.

Previously called
031Cruz, 2 030Lim, 6 029Reyes, 4 028Santos, 2

Table for two

  • 033Dizon2 pax
  • 034Garcia2 pax

Table for six

  • 035Bautista6 pax

Wall display, restaurant layout. Waiting positions are grouped by table bracket.

Set up for the way your room runs

A clinic queue and a restaurant queue are not the same problem, so no location gets a generic setup. We configure each one for its own room before the doors open.

Clinics

One patient at a time

Every patient holds a single ticket. Staff work the queue in order, and the console keeps a few people called ahead so the front desk never stalls.

Two patients waiting to be seen in a clinic waiting area, with the receptionist at the counter

At a clinic location

Customer unit
One patient
Party size
Not collected
Calling order
In order, one at a time
Called ahead
Three kept ready
Head-back nudge
Two places ahead
Board layout
Broadcast, with ad space

Now serving

014Marisol DomingoCalled

Waiting

015Ramon Aquino
016Grace Villanueva
017Noel Marquez
018Ana Reyes

Just served

013Corazon IlaganServed
012Danilo PerezServed

The console, set up for a clinic location

Restaurants

Parties, seated by table size

Guests join as a party and say how many are coming. When a table frees up, the console offers the tables that fit, best match first, so nobody does the arithmetic at the door.

Two guests waiting to be seated beside the host stand, with diners at tables behind them

At a restaurant location

Customer unit
Party of guests
Party size
Collected, mapped to table brackets
Seating
Best fit, as tables free up
Calling
Follows the tables
Head-back nudge
One place ahead
Board layout
Classic, with a recently-called strip

A table just freed up

Seat a table for 2 Seat a table for 4
Table for 6 Table for 8+

Waiting by bracket

033DizonBracket 2
034GarciaBracket 2
035BautistaBracket 6
036LimBracket 4

Previously called

031Cruz, party of 2Seated
030Reyes, party of 4Seated

The console, set up for a restaurant location

Several themes for every screen

Your queue shows up on more than one screen: the TV or tablet at the counter, the phone in a customer's hand, and the computer your staff use at the desk. Pick a theme made for clinics, one for restaurants, or one for any other business. Or set your own colours and add your logo and name.

Not a clinic or a restaurant?

The queue works for more than one kind of place. How many people can join at once, how far ahead we call, whether staff can add someone at the desk, and whether names show on the board are all settings. Describe how your room runs, and we will set it up that way.

Tell us about your room
NomoQMessenger
Ticket 018 is confirmed. Three parties ahead of you.10:12 AM
You are two ahead. Start heading back.10:31 AM
Ticket 018, it is your turn. Please proceed to the front desk.10:38 AMView my ticket

Messenger thread, recreated from the product

Reaching people after they walk away

The ticket page is the baseline channel and it works for everyone. Two more sit on top of it, and one of them is already built.

Live status page

Every ticket has its own link that updates itself in real time, with polling and a tab-focus resync as fallbacks.

Always on

Facebook Messenger

Customers opt in from the ticket page. Confirmation, head-back and called notices each carry a button back to the ticket.

Built, awaiting Meta credentials

SMS

The dispatch router and the message log already handle this channel. Adding a provider later is additive, not a rebuild.

Provider slot ready

Built for front-desk trust

A queue holds names and phone numbers. NomoQ treats that as clinical data, because for most of our locations it is.

Accounts and tenancy

  • Isolated by location. Every record is scoped to one location, and every staff route checks ownership.
  • Two roles. Admins reach settings and staff management. Operators get the console only, including open and close.
  • Sign-ins are locked down. Staff passwords are never stored in readable form, and repeated failed attempts get slowed down.

Check-in integrity

  • The QR is renewed every time the queue opens. A link from an earlier session stops working, so nobody joins from across town.
  • Ticket links cannot be guessed. A link carries a long random code, not a running number.
  • Check-ins and messages are verified. One connection cannot flood the queue, and Messenger messages are confirmed as genuinely ours.

Operations and data

  • 90-day retention purge removes queue records and message logs on a daily job.
  • Nightly backups with a documented restore, plus health and readiness endpoints.
  • Only safe file types are accepted. Uploads are limited to ordinary images and video, and the site cannot be embedded inside another page.

Common questions

Still deciding? A short call is usually faster than a spec sheet.

Book a demo

Or email hello@nomo-q.com.

Do customers have to install an app?
No. Check-in and the ticket page both run in the phone browser. There is nothing to download, and no account to create.
What happens if someone scans an old code?
The link is refused and they are shown a short message asking them to scan the code currently at the counter. That is what stops remote check-ins and repeat joins.
Why is there no wait time on the ticket?
Because a wrong estimate makes people angrier than an honest position. Customers see how many are ahead and what number is being served. That is always accurate.
Can you set up a clinic and a restaurant differently?
Yes. A clinic location and a restaurant location queue in different ways, so each one is set up for its own room: the check-in form, the calling rules and the board. You also pick how the screens look, from ready-made themes or your own colours, and the number, the status and the QR code follow. We do that setup with you before the location goes live.
We are not a clinic or a restaurant. Can we still use it?
Often yes. The queue is built from settings rather than hard-coded for one industry, so how many people join at once, how far ahead we call, desk check-in and whether names show on the board are all switches. Tell us how your room runs and we will say plainly whether the current version fits. We would rather turn down a poor fit than sell you something you will grow out of.
What if the display loses power or the network drops?
Boards are built to run unattended. They re-fetch when the connection returns, poll every ten seconds as a safety net, and recover from an API restart without anyone walking over to them.
Where does our queue data live?
Your queue lives on the same system that serves your location, kept separate from every other business on it. We never mix one location's data with another. Queue records and message logs are deleted automatically after 90 days.

Put your queue in their pocket.

We set up each location for you. Your staff learn one screen, and the queue starts running the same day.

  • Provision a location with an admin account, closed by default.
  • Configure your name, fonts, palette, logo and group sizes.
  • Train the front desk on open, close, call and seat.
  • Go live with the QR on the counter and the screen on the wall.
Please enter your name.
Please add your organisation.
Not a clinic or a restaurant? Choose Something else and describe it below. Please pick a location type.
Helps us match timezone and support hours.
Optional. We will confirm a time when we reply.
We only use this to reply about your demo. That address looks incomplete. Check for the @ and the domain.
How many queues, how busy, anything unusual.