VOCA answers from your hotel’s information, in Arabic or English. When something needs doing, it becomes a tracked task for the right team.
Kitchen
Housekeeping
Front desk
Stay is current No stay Request routed to a team
A scripted illustration of one hotel. Room numbers, times and the reference are samples. Step through the interactive demo →
How it works
Five steps, the same every time. Each one shows what the guest sees and what your team sees.
Step 1 of 5
The guest scans the hotel’s QR code, picks English or Arabic and gives their room number. Or they scan the room’s own code and enter the stay code from check-in.
Guest · first screenPhone
Room
205
Continue
Team · front deskWorkspace
Step 2 of 5
They ask in their own words, by voice or by typing. VOCA answers from the information your hotel approved, and says so when it does not know.
Guest · voice or typedPhone
Could we have two extra towels?
Listening
Team · front deskWorkspace
Nothing to do yet
Step 3 of 5
Orders, bookings and anything with a price are shown to the guest first. Nothing is sent until they say yes.
Guest · reviewPhone
Room service
2 × Club sandwich
Totalshown here
Team · kitchenWorkspace
Nothing sent yet
Step 4 of 5
When it exists as a record, with a reference, the room and an owner, VOCA tells the guest it was sent. Not before.
Guest · replyPhone
I’ve asked housekeeping to bring up two extra towels.
DEMO-1042 · Received
Team · housekeepingWorkspace
Two bath towels
Step 5 of 5
The team accepts and updates the status. If nobody accepts in time it is flagged for escalation. The guest sees every status and can rate a finished request.
Guest · your requestsPhone
Two bath towels
Rate when completed
Team · housekeepingWorkspace
Two bath towels
Not accepted in time → escalated
01 / What guests can ask
Information is answered directly. Anything that needs doing becomes a request.
Breakfast hours and place, facilities, offers and policies — from facts your hotel approves. If VOCA doesn’t know, it says so and offers your team.
AvailableThe network and password appear on the guest’s own screen, with a QR code to join. The password is never spoken aloud and is shown only to a verified stay.
AvailableTowels, cleaning, a broken light or air conditioning. Each request gets a reference, the room, an owner and a time to accept.
AvailableGuests ask for dishes in their own words and see your menu with prices. VOCA shows the total for the guest to confirm, then the order goes to your kitchen with any allergy noted. Sold-out dishes drop off, and your team posts the charge to the room. VOCA never calls a dish safe beyond what your menu records.
AvailableThese are requests for your team, not confirmed bookings. VOCA shows the guest a review before sending and says staff confirm price and availability.
Request onlyNot connected by default. Connections are assessed and scoped around the systems you use.
Integrations →What it looks like
Micrographs of the real screens. Content is sample content.
Welcome. How can I help?
The first screen asks for a room and a language, and the greeting follows.
2 × Club sandwich
2Totalshown here
3Orders and bookings show the guest the details or the total first.
NetworkHotel-Guest
2Password••••••••
The password goes to a verified stay and is never spoken aloud.
SarahI’ll take it from here.
Staff reply by name, and VOCA stops answering while they help.
Not possible · reason shown
Received, accepted, in progress, completed — or not possible, with the reason.
Checkout ends access at once, and the next guest sees none of it.
02 / Ownership
Your team sees what was asked, where, and by when. Anyone can take over a conversation; VOCA stops answering while a person is helping.
Recorded with a reference. The guest is told it was sent.
A team member takes it within the time you set.
Or Not possible / Cancelled, shown honestly.
03 / Room and stay context
Access is tied to a current stay. It ends at checkout, and the next guest sees none of it.
01
Staff create the stay and give the guest a one-time stay code.
02
The guest scans the room QR code and enters the stay code, or opens the hotel’s entry page, picks a language and gives their room number.
03
Requests are tagged with the room. A room change keeps the guest signed in.
04
Repeated wrong codes lock the stay for a short time.
05
Access ends at checkout. The next guest sees none of it.
For your guests
For your team
04 / Set up with you
Setup is forms and review, not prompt writing. Nothing goes live until you approve it, and staff can test a saved draft first; test orders are marked TEST.
See the deployment path →Hours, places, offers and policies you approve.
Which team receives each kind of request.
Arabic and English, and how VOCA greets guests.
How long a request may wait, and who is told next.
Dishes, prices, serving hours by section, and what is sold out today.
Rooms, stay codes, and who in your team can configure or approve.
05 / Hotel questions
They can ask. VOCA creates a request for your team and tells the guest that staff confirm price and availability. It is not a confirmed booking.
Yes, from your own menu. VOCA looks the dishes up, shows the total for the guest to confirm, and sends the order to your kitchen. Prices come from your menu, never from the agent’s memory, and your team gives any delivery time.
Not by default. Connections depend on your system and its interfaces, and are assessed and scoped in the pilot.
VOCA offers to connect them with your team, and your team can take over the conversation at any time.
The guest sees only their own stay. Your team sees requests in the workspace. Details are on the Security page.
Next step
Tell us about your property. We’ll prepare a focused demo.