What your customers see

The status page

Once somebody has joined, the status page is their copy of the ticket. It is the page that lets them leave your shop and go and do something else — which is the thing customers actually want from a waitlist.

What it shows

  • Their position in line, updating live as people ahead of them are served.
  • An estimated wait — the same figure your team sees, so nobody gets two different answers.
  • Which branch and queue they are in, and what they asked for.
  • Whatever actions you have allowed them.

It updates by itself. Somebody watching the page sees their position count down without refreshing, which is worth more than it sounds — it is the difference between trusting the wait and standing in the shop to check.

What the customer can do

Which of these appear is up to you, under waitlist rules:

  • Leave the line — cancels their visit. Worth allowing: somebody who has changed their mind and cannot tell you just becomes a no-show and a wasted call.
  • I'm here — tells you they have arrived, without replacing their place in line.
  • I'm running late — flags a delay on your list so you can call somebody else first.
  • Still coming — confirms they have not wandered off, which is what you want after a long wait.
  • Correct their details — a mistyped mobile number is fixable by the one person who knows the right one.

Finding it again

Customers close tabs. The link is included in the messages you send them, so the confirmation message is worth having switched on for exactly this reason — it is how somebody gets back to their place after their phone locked. Where a message can point somewhere, you choose whether it goes to the status page, the booking details or the branch home page.

When it is their turn

Calling somebody changes the page and sends the message. This is the moment the whole product exists for, so it is worth being deliberate about which channels you use and what the wording says — see channels and fallback.