How did we test WaiterPilot's ordering, and how can you repeat it?
On 15 October 2026 we placed real orders at one table of Broadnet Cafe, BroadNet.AI's own demo restaurant, in the live product. The guest side ran in a phone-sized browser window and the staff board in a second window. We timed four confirmed orders from the guest's Confirm to the ticket appearing on the staff board: 0.81, 2.74, 1.49 and 1.28 seconds. Four samples is a small test; this page gives the method so you can repeat it on your own menu.
Updated
What was the test setup?
One restaurant, one table, two browser windows, the live product, one afternoon.
| Item | What we used |
|---|---|
| Date | 15 October 2026 |
| Product | WaiterPilot, the live product as restaurants use it (not a mock-up or a simulation) |
| Restaurant | Broadnet Cafe, BroadNet.AI's own demo restaurant. Real menu of 147 dishes in 19 sections, prices in Jordanian dinars (JOD), Arabic set to Jordanian, bill charges Service 5% and Tax 7.5% |
| Table | One table, "Table Demo 1"; the restaurant's other demo tables were open but had no orders |
| Guest device | A browser window sized like a phone, 390 × 844 pixels |
| Staff device | The staff board (All staff view) in a desktop browser window, 1280 × 900 pixels |
| Staff alerts | Phone alerts were blocked in the staff browser, so they were not part of the test |
| What we ordered | Single drinks from the Fresh Juices section: orange, strawberry, banana with milk, lemon with mint, mango |
What did we do, step by step?
We went through a whole visit as a guest and as staff, and took a screenshot at each step.
Open the table
Open the table's link, as a QR scan would, and check the chat greets the guest with Chat, Menu and Bill tabs.
Ask a menu question
"Hi! What fresh juices do you have?" Check that the answer lists only dishes on the menu.
Order in plain words
"One orange juice please, the regular one, no smoothie." Check the cart holds exactly that.
Confirm and time it
Tap Confirm in the cart and time how long the ticket takes to appear on the staff board.
Awaiting staffWork the ticket
On the staff board, tap Confirm, check the ticket moves to In kitchen and the guest's screen follows, then tap Served.
ServedCall and check
Ask the chat to call the waiter and check the call reaches the Floor service screen; ask for the check and note the cash-or-card question; open the Bill tab.
Change language
Ask the same juice question in Spanish and in Gulf Arabic, and record the language and dialect of each reply.
How long did confirmed orders take to reach the staff board?
Between 0.81 and 2.74 seconds, over four orders. The average was 1.58 seconds and the median 1.39 seconds.
| Sample | Guest Confirm to ticket on the staff board |
|---|---|
| 1 | 0.81 s |
| 2 | 2.74 s |
| 3 | 1.49 s |
| 4 | 1.28 s |
| Average (4 samples) | 1.58 s |
| Median (4 samples) | 1.39 s |
This measures when the ticket appears for staff. It does not measure chat reply time, how fast staff confirm, or kitchen time.
What else did we observe?
Each step behaved as described on our product pages. Screenshots are on the pages linked here.
| Check | What happened | Screenshots |
|---|---|---|
| Menu question in English | Answered from the menu, with Arabic dish names alongside and one add-on suggestion (smoothie for 0.35 JOD) | How it works |
| Order states | Awaiting staff, then In kitchen after staff Confirm, then Served; the guest's screen followed each change | How it works |
| Waiter call | Appeared on the Floor service screen and in the main board's Requests panel with Ack | Waiter call and bill |
| Check request | The chat asked "Will you be paying with cash or card?"; we stopped there | Waiter call and bill |
| Live bill | Subtotal 19.00 JOD, Service 5% 0.95, Tax 7.5% 1.43, total 21.38 JOD, with Split the bill | Waiter call and bill |
| Spanish question | Answered in Spanish; dish names stayed in English as on the menu | Multilingual ordering |
| Gulf Arabic question | Answered in Jordanian Arabic, the restaurant's chosen dialect, with Arabic buttons | Multilingual ordering |
How can you repeat it in your restaurant?
During a demo or your 30 free days, with two devices and a stopwatch or a screen recording.
- Use your real menu and tables. Pick a table at the far end of the room, where the signal is weakest.
- Use the devices you'll really use. A guest's phone on your guest Wi-Fi or mobile data, and the tablet or phone your team will keep at the pass.
- Record both screens. A screen recording of each device, or a video of both side by side, lets you read the time from Confirm to ticket afterwards.
- Take at least ten samples. Spread them over a quiet hour and a busy one. Write down the smallest, the median and the largest.
- Time the people too. How long until someone taps Confirm, how long until Served, how long until Ack on a waiter call. The owner page shows these averages once you're live.
- Test the hard cases. A note, an allergy question, a dish you've marked sold out, a guest cancelling, and two or three guest languages. Our order exception guide lists what to expect.
- Write it down with the date. Device, network, table, what you ordered and every time. Repeat after you change your menu or set-up.
Questions about this test
Why only four samples?
This was the first timed run, done while capturing the screenshots. We publish it with its size so nobody reads more into it. We will add samples in later runs.
Was this a real restaurant?
It was Broadnet Cafe, BroadNet.AI's own demo restaurant, running on the live product with a real 147-dish menu. No real guests' orders were involved.
Does "within seconds" include staff confirming?
No. The times are until the ticket appears on the staff board. The first order at a table then waits for a person to tap Confirm.
Can I see the test myself?
Yes. Book a demo and we can run the same steps with you, on your own phone, or try the sample order first.