Open the menu from a test room just before the kitchen closes. If you send an order now, who sees it? Run the four cases below on an early and a late shift using the devices and staff who normally take orders.
On this page
Set up one room, one dish and one person on each side
Give the guest role to someone who has never used the staff screen. Put them in a room with an ordinary phone, the printed code and whatever instructions a guest would find there. The person at the kitchen station should hear the normal noise of a shift. A manager watching both screens in the office tends to fill in gaps that a guest, cook or receptionist cannot see.
Pick one uncomplicated dish and one with a modifier the kitchen has to notice. Agree what makes a test unmistakable at the point of preparation. If payment or posting is in scope, use an approved test route or training account. Plan who will close test tickets and verify they are out of the live queue before releasing the room.
Write down your acknowledgement target before you take the first order. Decide which staff message counts. A green check on a guest’s phone can mean the system stored the request. The kitchen still has to accept it or someone has to tell the guest it will be delayed.
Follow one order from start to finish
Open the QR link on a phone in the room. Send a clearly marked test order and note the time on the guest’s screen. Ask the kitchen to acknowledge it from its usual station. Verify that the room, item and any notes match. Ask reception where it can check the status if the guest calls.
Write down the maximum acknowledgement time the team will commit to for this shift. Use the same target in the retest. Log the time the kitchen acknowledged the order, the first message the guest saw and the person who owned the next step.
Know which screen proves each step
Follow the same test order through three places. The phone tells you what the guest was promised. The kitchen view tells you how the order arrived and what happened to it. The desk view tells you whether anyone can answer a call without walking to the kitchen. Keep the ticket number beside the times so that someone reviewing the log can tie all three together.
Pay attention to the modifier, the room reference and the delivery note. A perfectly timed alert is little help if the order gets attached to the wrong room or if “leave at door” only appears on an admin view. Read back exactly what the cook saw and ask them to describe the next action before you explain the expected answer.
| View | What to save |
|---|---|
| Guest phone | Submitted time, total shown and the first status after sending |
| Kitchen station | Ticket time, room and items, modifier, who acknowledged it |
| Reception | Where the desk can find the ticket and the current message for the guest |
| Payment or posting, if used | Method, test amount and the matching reference |
Test where the handoff can break
- Kitchen closed. Send a test just after the cutoff. Check that the menu sets the right expectation and that the guest has a clear next step.
- Sold-out dish. Mark an item unavailable while a test guest has it open. Check what their phone shows and who can offer a replacement.
- Repeated tap. Try submitting the same test order twice, then check the kitchen queue. The shift lead should be able to identify and resolve a duplicate before it is prepared.
- Missed alert. Silence the test device and send an order. Check which person or backup station notices it and how reception gets an answer.
Watch what the guest does after a repeated tap
Start with a slow connection on the test phone or briefly disconnect it after submitting. Give the tester no instructions beyond ordering the dish. They might reopen the page, use the back button or press send again. Check which ticket the phone shows after it reconnects and which orders appeared in the kitchen. A second row in the queue needs a visible way for staff to tell whether it is a second request or a duplicate.
Also try the opposite mistake. Order the same item twice on purpose, separated by a short interval. Two legitimate orders can look identical by room and price. The right check is the order reference and the history the shift can see. Train the shift to ask before cancelling an ambiguous ticket, especially when preparation has already started.
Retest the missed alert with the staff you actually have
Run the missed-alert case during the period when the kitchen is most stretched. Put the test order in while the operator is away from the station. Who sees it if the sound is off and the screen is out of view? Follow the backup through one full handoff. If the desk calls the kitchen, ask which number works, who has the handset and what the guest hears while waiting.
Here is an illustrative run with a two-minute target. An 18:00 ticket is acknowledged at 18:01:12 and the correct room and modifier reach the station. At 20:45 a quiet alert is missed. The backup opens the queue at 20:49:10. Four minutes and ten seconds misses the target even if the food eventually arrives. Change one thing, such as assigning reception to check outstanding tickets during close, then run that same case again.
If you can only run one extra scenario, change the staffing, not the dish. Test it when the person who set the system up has gone home. Leave the booking and the everyday support instructions as they would otherwise be.
Keep payment and kitchen acceptance in separate columns
If your setup lets guests pay by card, test what appears after a payment fails or is abandoned. A kitchen ticket should make clear whether staff can start preparation, whether another check is needed or whether the order was cancelled. For a room charge, have the authorised staff member match the test ticket to its posting. Keep that check in a separate column from kitchen acknowledgement.
Oracle documents room-folio charging as a separate transaction flow in its Simphony and OPERA example. Use the setup your property actually has and ask your provider to show the equivalent flow. Where staff post manually, include the person and time in the log. That is the way to find a dish the kitchen delivered even though the room charge never appeared.
Source Oracle Hospitality on charging menu items to a room folio
Give the pilot a clear way back
Leave the usual ordering option available during the pilot and make it obvious on the room card. Write down who can pause mobile orders while the kitchen works through a backlog, how the guest will see that service is paused and what happens to orders already submitted. At shift change, tell reception whether the menu is open, paused or back to normal.
At the end of the pilot, review failures by consequence. A confusing status message needs a rewrite. A ticket that reached the wrong room, an order accepted after the kitchen shut or an unaccounted payment needs the shift lead to see a clean rerun before expanding. Give each open case to the department that can actually change it.
Decide whether the next shift can repeat it
Use the CSV log for both shifts. Assign a person and a retest date to any case that missed your target. Keep the existing ordering channel available until the team can demonstrate a recovery path on the shifts that will take live orders.
The public Guestivo demo can show the guest-facing part. Use a staff walkthrough for kitchen notifications, routing and escalation.


