An AI host built around your covers.
Try the journey from a browser conversation to a saved demo booking, then review the setup your restaurant needs.
One evening on the phone, start to finish.
A guest calls and a chat books a table while the call is on; the owner's week; a regular changes her booking in Arabic; and the special requests the team prepares.
One booking, start to finish.
See these five steps in the browser demo. Real venue channels and booking rules are qualified before guest use.
- 1StartsTry a browser call or chat in the Marsala demo. Connecting a restaurant's phone line is a separate setup step.
- 2AnswersOnla greets the guest and asks how it can help.
- 3ChecksIt checks covers by table and dining time against your floor rules.
- 4BooksIt saves the reservation in its booking book, then confirms it to the guest.
- 5Hands overYour team sees the booking. Anything unusual is recorded as a request with conversation context.
What Onla handles for you.
Browser call and chat demo
Try a two-way browser call or chat with Amira here. A connection to your restaurant's phone line or a chat widget on your own website needs separate setup and qualification.
Browser demo · livePhone line · setup requiredWhatsApp · activation pendingCovers, not abstract slots
Onla checks table capacity, dining time and configured booking start times. If a time is full, it can offer an available alternative. Section preferences and kitchen-close rules need separate review during setup.
Table capacityDining timeBooking start timesBooked end to end
Onla checks availability and saves the reservation before it confirms. How this fits your existing booking system is agreed during setup.
Checked before confirmingSaved booking recordPrivate events on the spot
A birthday or a corporate dinner: Onla checks the room and saves the private-room booking, then records a menu and deposit follow-up for your team.
Room availabilityMenu and deposit follow-upYour restaurant's knowledge
The demo answers from its configured restaurant information. During setup, we review your menu, parking, opening hours and house policies, and test the answers before guest use.
MenuParkingOpening hoursHouse policiesBookings and follow-ups
Your team can review saved bookings, guest requests and follow-up status in the host workspace. Saved guest-call recordings and a staff recording viewer are not currently included.
Saved bookingsGuest requestsFollow-up statusWhat your team sees.
A host workspace for the requests that need a person. Claim one under your own name, set when you will follow up, and close it with a note.
Unowned and overdue requests are flagged first.
Search the next seven days of Onla reservations by guest, date or reference.
Reopen a request with a reason if something changes.
Host workspace
Requests
- Guest asks for the managerWaiting 34 min · no ownerOverdue
- Birthday cake for SaturdayClaimed by Layla · follow up by 19:30Claimed
- Allergy question on the tasting menuResolved · note: chef confirmed by phoneResolved
Every claim, note and reopen is kept in the request's history.
What Onla leaves to your team.
Knowing where the AI stops is part of trusting it.
Menu and deposit details
Recorded as a follow-up for your team. They are not sent to the guest automatically.
Complaints and unusual requests
Recorded for your team with conversation context. Your team owns the follow-up; a saved request does not prove the guest has been contacted.
Activation is pending approved account setup, templates and delivery tests.
Your booking system
How Onla works alongside it is agreed during setup, before any real call.