One stage of a multi-step queue. For each party the step records when they entered it, when they were called at it, when they left it and who worked it. A party visits each step at most once. Retired steps are archived, so past history still reads.
One stage of a multi-step queue. For each party the step records when they entered it, when they were called at it, when they left it and who worked it. A party visits each step at most once. Retired steps are archived, so past history still reads.
See also: Multi-step queue, Queue entry, Wait time
Continue exploring our knowledge base
An ordered list of queue entries for one service a business offers: parties join it, wait their turn and are called in order. A queue belongs to one business and can be tied to one location. Customer-facing copy calls a queue a waitlist or a line; specs say queue, because in the platform's ontology 'line' names a line of business.
A queue entry's number in its queue, where 1 is next. Position moves up on its own as entries ahead are seated or removed, and the party sees it on their tracking link.
The estimated minutes until a queue entry is called, worked out from the entries ahead of it and the business's recent time per party. It is an estimate that is refreshed as the queue moves, and both the party and the staff see it.
The number of people a queue entry or a reservation is for. It is captured when the party joins or books, and staff use it to match the party to a table or resource and to estimate the wait.
A party's private live page, sent by text or email or shown right after joining, where they follow their own queue entry: position, estimated wait and messages from the business, without asking staff.