Queue Join

What your customers see

What your customers see

Half the product is a set of pages you will rarely look at, because they are for your customers rather than your team. It is worth knowing what each one does — most support questions are about something on one of them.

They look like you, not like us

Every public page carries your business name and your branding — colours, fonts and background are set under custom design. The wording is yours too: the terms customers see for a visit, a booking or a queue can all be renamed, which matters when your industry calls them something else.

Two things on them are Queue Join’s rather than yours. The join form, the booking form, the status page and the booking confirmation link to Queue Join’s terms, privacy policy and SMS policy, because we are the ones sending the texts. And a visitor may see a small banner asking whether they accept Google Analytics cookies. It never appears on the waiting-room display, which runs with nobody there to answer it, or on the kiosk, which is one tablet shared by everyone who comes in.

Customers never sign up

There is no account for a customer to create and no password for them to forget. Their place in line is held by an unguessable link, which arrives in the message you send them and works from any device until the visit is over.

Test the whole thing on a real phone

Before you put a code on the door, scan it on a phone that is not signed in to anything, on mobile data rather than shop wi-fi, and go all the way through joining and being called. Ten minutes here saves a bad first day. Add that phone under Location settingsTest numbers first, or joining over and over from one number soon looks like misuse and gets turned away — see testing with your own phone.