Skip to content
Q·Flow

Every customer knows their turn, on their own phone.

Scan a QR code, take a number and follow the queue in the browser. No app, no account.

Your ticketYou're in the queue3 people ahead
Preview with demo data

A working product, not a concept.

Real captures of the system running locally with demo data. Staff screens are in Arabic.

Capture of the branch board showing tickets in several states with a call button on each
Branch operations board
Capture of branch reports showing ticket totals, average wait and status breakdown
Branch performance
Capture of the display screen with the current number large and the ready numbers beside it
Waiting room display

Six steps for the customer, one button for staff.

The customer

  1. Scans the QR code

    With the phone camera. The branch page opens in the browser.

  2. Requests a turn

    One tap, with no account or phone number.

  3. Gets a ticket

    A large, clear number that stays available at its link.

  4. Follows the wait

    Sees how many people are ahead and the current status.

  5. Keeps the page open

    The status updates live. Alerts are optional.

  6. Is called

    Sees the call and taps “I'm coming”.

The team

  • New ticket

    Automatic numbering, or the cashier's number with a QR per order.

  • Send the call

    One tap updates the status and tells the customer.

  • Recall and calling out loud

    If sending fails, the board says so and asks you to call the customer yourself or recall.

  • Confirm and complete

    Staff confirm arrival, so the records stay accurate.

What works in Q-Flow today

Digital tickets, no install

Runs in the browser in Arabic and English, and recovers from its link.

A queue board for staff

Clear statuses, search, and calling from one place.

Live updates with recovery

WebSocket with reconnection, and periodic checks if it drops.

Waiting room display

A number readable from afar, with optional chime and voice.

Reports per branch

Wait, response and status breakdown, for up to 92 days.

Branches and team roles

Each company is isolated. Each employee has their branches and permissions.

Optional

Browser alerts

Web Push where the device supports it. iPhone requires adding the page to the Home Screen.

In development

Live Activities on iPhone

An optional iOS layer still being verified on devices. Not available to customers yet.

We don't say “delivered” without proof.

The board shows the furthest state we can prove for each call. If it fails, it asks staff to call the customer themselves, so nobody loses their turn.

  1. Send requested
  2. Accepted by push service
  3. Receipt from device
  4. Notification opened
  5. Tapped “I'm coming”

For anywhere people wait

Statuses are general, and wording adapts to the business type. No sector integrations are available yet.

  • Restaurants and cafes
  • Clinics
  • Hospitals
  • Service centers
  • Salons
  • Retail
  • Banks and customer service

Frequently asked questions

Does the customer need an app?

No. The whole journey runs in the browser after scanning, with no install, account or phone number.

Do alerts arrive when the phone is locked?

We don't guarantee that in a browser. Web Push is optional and depends on the device. Returning to the link restores the status from the server.

Can someone take more than one ticket?

Tabs of one browser normally share a ticket, but two devices can't be linked, because customers give no identity.

What if a customer can't be alerted?

The staff board shows the actual send result, asks staff to call out loud, and offers Recall with the number on the display.

Is it ready for every device?

Automated tests pass, but testing on real phones is still under way. We don't claim a device until it's proven.

Try Q-Flow at your branch.

Create the account, print the QR code and start your first queue.

Create your account