Give each provider the same fictional room, the same service request and the same outage scenario. Ask them to show the guest screen and the staff screen. Capture the result during the call, while the hotel team can see what actually happened.
On this page
Prepare the test property
Choose a typical room and two roles, such as a receptionist and a duty manager. Set opening hours and a fallback contact. Pick one ordinary request and one that belongs to a different department. Give every vendor the same setup in advance.
Invite the person who will own the work after purchase. When they hear “supported,” ask them to open the view and complete the action on a phone or staff account.
Ask for four live actions
- Open the guest link on a phone and locate a service without a presenter pointing to it.
- Send a request, assign it to the correct department and show how the guest can tell it has been picked up.
- Hand the request to a second shift and show what the next team can see.
- Change a service’s availability and check the guest page. Ask which role can make that change.
Score only what you saw
Record each item as shown, partly shown or awaiting confirmation. Write the exact condition for approval beside any partial result. For integrations and commercial terms, request written confirmation for your property setup and subscription.
Keep a separate list of essential tests. A vendor that leaves an essential failure unresolved still has an open item, even if several other tasks went smoothly.
Start the call with the same property brief
Send each vendor one page with the size of the trial, service hours, two staff roles and the systems you already use. Tell them which tests you need to see from your own handset. Let them use a training account. The brief is particularly important if the property has a restaurant whose desk closes earlier than reception, or staff who cover more than one building. A demonstration set in a full-service city hotel can hide the work that lands with one person overnight.
Ask the vendor to mark work that needs configuration before it appears in a trial. For example, a button can exist in the vendor’s account while your own team would need to build the service menu and decide which role receives the requests. Put the configuration and who will own it on the scorecard. That keeps the next call from starting with an empty question about implementation.
Test how a request is corrected
Send a request for a spare blanket. Have the first receptionist send it to housekeeping, then say that housekeeping has gone home. Ask the vendor to route it to the duty person and show the guest view again. Look for the old assignment being clearly replaced, with a record someone else can find on the next shift. Make sure two departments do not end up delivering the same blanket.
Repeat with a guest who asks to cancel after staff have accepted. Ask the presenter to show what is visible on the desk, on the staff phone and to the guest, in that order. A screenshot of a success screen answers very little about who can undo an action. Write down which roles are allowed to change it and whether changing the request automatically sends a message.
| Task | Observed | Follow-up |
|---|---|---|
| Guest opens service link | Breakfast and room service found | Repeat on a guest phone with its language changed |
| Desk hands off a request | Duty queue shows it, with the earlier note | Confirm who can assign outside their department |
| Desk cancels after acceptance | Staff can cancel in the dashboard | Show what the guest sees after cancellation |
| Service closes early | Hours changed in the demo | Repeat with a guest already on the open menu |
Ask for evidence on a second device
Put a receptionist on the staff view and a colleague on the guest phone. Turn off the presenter’s screen sharing long enough for both people to complete the ordinary task. A good service menu will still make sense from the hallway or a room with poor Wi-Fi. Time how long it takes to find the fallback number or address on the printed card. Keep that separate from the time to open the app.
Try a booking that was changed after the original link was sent. Ask what the guest sees if the room changes, the stay ends or a new guest gets the room. Only test systems and records you are authorised to use. If that scenario depends on an integration, request a walkthrough with an equivalent test environment and mark the item open until you see it.
Get the rollout effort into the same comparison
Ask who writes the room information, checks the menu language, prints the cards and trains the night shift after signing. Include the recurring work when hours change and when someone joins or leaves. Ask about an export of the information the hotel enters, who receives support calls outside desk hours and how a property can return to its existing process during a pilot.
Separate optional convenience from a condition you cannot operate without. A prettier home screen can matter after the team has confirmed how to receive, acknowledge and reassign requests. Review the shortlisted vendors with the shift lead who would own the change. Hand them the evidence rows and let them pick the unresolved tests to repeat.
Use the result three days later
Send the vendor the remaining questions with a concrete answer for each. “Show a duty receptionist receiving the request after the housekeeping account leaves the shift” is easier to check than “confirm routing.” Give each item a person on your side and a date to close it. When the vendor replies in writing, retain the response beside the test that prompted it.
If the demo goes well, use the same tasks in a small pilot, on the actual devices and at the time the desk will run them. Start with guest access and one service request. The scorecard becomes a useful training handout when the hotel can read a row and reproduce the result without the vendor present.
Source Guestivo walkthrough booking


