From paper and WhatsApp books to confirmed tables.
If your reservations live in a notebook, a WhatsApp thread and the host's memory, start with the browser demo. See a booking checked and saved, then review how your venue could use one shared record.
Where a manual book lets you down.
Nobody here is careless. The book is just in three places, and the person keeping it is also seating guests.
Two books, two answers
A guest moves Saturday from four people to six on WhatsApp. The notebook still says four. Whoever takes the next call answers from whichever one they checked.
The phone rings mid-service
The host is seating a table when the phone goes. The guest who wanted 8pm hangs up and books somewhere else.
Yes, from memory
Someone confirms table seven for eight o'clock without looking. Two parties arrive for one table.
Event enquiries go quiet
A party of fourteen asks about the private room. The message sits in one person's phone until the date has passed.
Try one shared booking record.
The demo saves bookings against its configured floor. Your venue's existing bookings, staff workflow and external channels need setup and testing before guest use.
Checked against your tables
In the demo, Amira checks the configured table capacities, dining time and booking start times. If the requested time is full, she can offer available alternatives. How the check works.
Saved, then confirmed
The booking goes into the book first. Amira says it is confirmed only once it is saved, and reads back the date, time, party size and name.
Changes on the same call
A guest who calls to move a booking or add two people can do it on the call. If the new time is full, the original booking stays.
Your team can always step in
Hosts can move a booking, change the party size or switch the table in the host workspace. Each change is kept in the booking's history, with who made it.
What moving over looks like.
You don't need a new booking habit before you start. Setup begins from how your venue takes bookings today.
- 1WalkthroughShow us how bookings work today: the notebook, the WhatsApp threads and who answers the phone.
- 2Your floorTables and their sizes, how long a table is held, the times you seat, and when a party becomes a private event.
- 3Every booking in one placeWe plan how WhatsApp and walk-in bookings would reach the same record. Any booking absent from that record cannot be included in Amira's availability check.
- 4Test, then go liveKeeping your number is the planned path. Carrier routing, the connection, staff fallback and a complete booking need testing before guest calls can be enabled.
What works now and what needs setup.
Browser demo and phone setup
The browser call demo is available now. Your restaurant's phone connection, booking information and conversation requirements need setup and testing before guest use.
Planned, not live. Onla doesn't read your WhatsApp threads yet.
Before you move your book.
Will Onla read our WhatsApp messages?
No. The current browser demo does not read your restaurant's WhatsApp threads. During setup we plan how those bookings would reach the same record. WhatsApp account activation and telephone connections need separate qualification.
Do we have to stop using the notebook?
Keep it while you set up if it helps. But one book has to be the one everyone trusts. When two books run side by side, someone ends up reconciling them by hand, and that's where double bookings come from.
What happens to the bookings already in our notebook?
They have to be in Onla's book before Amira takes calls, or she can't see those tables as taken. We plan how they get there during setup.
Can my team change a booking Amira made?
Yes. Staff can move, resize or cancel any Onla booking in the host workspace. If a change clashes with another booking, the free times are shown first, and saving anyway is recorded in the booking's history.
What does it cost?
One monthly plan per venue, with no setup fee, and you can cancel any month. The price is agreed on the walkthrough call.