Customer input
Ask the queuer for an order number, name or reason for visit as they join, then act on it from the queue view.
Customer input lets you ask each queuer for one or two pieces of information when they join a queue: order number, name, reason for visit, anything you want. It shows up next to their queue number so staff can prepare ahead of time.
The classic use case: an online-pickup queue where queuers enter their order number when they join, and staff retrieve the order from the back room before the queuer reaches the counter. Much shorter perceived wait.
Setting up an input field
Section titled “Setting up an input field”-
In Flowby admin, open the queue you want to extend.
-
Click Edit.
-
Click Add to create a new customer input field.
-
Enter the text for each enabled language:
- Name: the label the queuer sees, e.g. “Order number” or “Your name”.
- Description: helper text below the label, e.g. “Find it in your order confirmation”.
- Example input: placeholder text inside the field, e.g. “123456”.
-
Tick Required if the field must be filled before the queuer can join the queue. Leave it un-ticked to make it optional.
-
Save.
To add a second field, repeat. Queuers will see them stacked in the order you add them.
Where the input shows up in admin
Section titled “Where the input shows up in admin”Two places:
- Queue view, when it’s the queuer’s turn: input appears alongside the call-to-action so the staff member at the counter sees it immediately.
- Queuers page (people icon next to the queue name): full list of everyone currently in the queue with their input. Useful for displaying on a back-of-house screen so the order team can pick orders in advance.
Common patterns
Section titled “Common patterns”- Order number: staff retrieve the order before the queuer reaches the counter, cutting service time noticeably.
- Queuer name: useful for queues that need to be called individually rather than served on a “next up” basis.
- Reason for visit: quick triage at a service desk so you can route to the right specialist.
- Keep prompts to two or three fields max. Each field is friction at join time; longer forms cause queuers to abandon the queue.
- Use Required sparingly. A required ID number keeps your data clean, but it also blocks queuers who can’t find theirs from joining at all.
- For multi-language stores, keep prompts as universal as possible. “Order number” travels well; longer instructions need careful translation.