Floor rules to set before an AI host takes bookings.

Six decisions to bring to the walkthrough

We compare these with the way you take bookings today, then test the setup that results.

1. Tables and their sizes

   List each bookable table and its capacity, and Onla checks for a free table that fits. Review any table combinations you allow during setup. Never assume every pair can be joined.

2. Dining time

   Decide how long a booking holds a table. Review the venue default, the configured table durations and the private-room duration before you test back-to-back bookings.

3. Service and seating times

   Set your weekly services, last seating, booking interval and special closed days. Test the exact date and time, especially for a service that runs past midnight.

4. Private dining and large parties

   Review the room's capacity and which party sizes can book it directly. Add your set menus and deposit rule as well, and Amira books the room, the menu and each guest's choice in one call and tells the guest the deposit. The private-dining guide covers the details.

5. Notice and booking horizon

   Set how much notice you need and how far ahead guests can book. Onla checks these limits against your venue's local date. The default horizon is 180 days.

6. Complaints, allergies and extras

   Today Amira records complaints, allergy safety questions, special requests and callers who ask for a manager for your team, without promising a callback. Agree who reads them, and publish the house policies you want her to quote. See what Amira handles end to end.

Terraces, sections and preferences need their own review

Bring your section, terrace, kitchen-close and seating-preference rules to the walkthrough too. Don't assume the availability check enforces them. We review your bookable inventory and those restrictions with you during setup. A saved preference does not guarantee your team can fulfil it.

Keep one book, and let staff make exceptions

Bookings kept in a notebook, a WhatsApp thread or another system have to reach the agreed booking record. Amira can't treat a table as occupied from information that is missing. See moving from paper and WhatsApp.

Your team can still make exceptions. In the host workspace, staff can move a booking or deliberately override an availability clash. The clash is shown first, and the decision is recorded in the booking history.

Test the rules before guest calls

Once the rules are set, try them the way guests will: an available table, a full time, a party that is too large, a booking change and a request for a person. Check the saved record after each attempt.

Test English and Arabic names, numbers and times with your team, since real-call qualification is still in progress. The availability guide explains the check-and-save step. Your phone connection needs its own checks before go-live.