Take bookings on your own page instead of a marketplace that charges per cover. The system refuses to double-book a table, walk-ins and bookings sit on one board, and the guest gets a WhatsApp confirmation.
The bookings board and the guest booking page, as they ship.
Most restaurants here run bookings in a notebook, a WhatsApp thread, or a marketplace that takes a fee for a guest who was already coming. All three fail the same way on a busy Thursday.
Two people take a booking for the same table an hour apart and nobody knows until both parties are standing at the door. Walk-ins live somewhere else entirely, and no-shows are never recorded, so you cannot tell whether you have a problem.
The system checks the table against everything else booked in that window and refuses the clash rather than recording it. Walk-ins join the same board as bookings, and every no-show is a status you can count later.
You still keep a book. It just will not let you write the same table down twice.
One status per booking, with the transitions guarded so it cannot go somewhere that makes no sense.
On your own booking page: a date, a party size and a half-hour slot. Past slots disappear on their own, so nobody books 7pm at 7.30.
Name, phone, an occasion and a seating preference — the things that let you put an anniversary somewhere better than the door.
Before the booking is written, the system looks at everything else on that table in that window. A clash is refused, not recorded.
A WhatsApp confirmation when a phone number is on file and your WhatsApp number is connected — so the guest has it in the thread they actually read.
Bookings and walk-ins in one list. Confirm a pending one, move it to seated when they arrive, complete it when the table turns.
A walk-in is a pending booking. It sits on the waitlist view until a table frees, then it is confirmed and seated like any other.
Mark it and it counts. A cancelled or no-show booking can be reopened later, and the table check runs again in case the slot was taken meanwhile.
From the link they were sent, confirmed against their phone number. A cancelled booking frees the table without anyone answering a call.
Bookings default to 90 minutes; set a different duration per booking when a party needs longer.
Grouped by the failure each one prevents.
Bookings that arrive without a commission attached.
The check that a notebook cannot do.
The two things a host is juggling, in one place.
Confirmations that arrive where people read.
Where reservations meet the floor.
Everything else is convenience. Two parties at one table at eight o’clock is the thing that costs you a regular.
Creating a booking looks at every other booking on that table whose window overlaps. If one does, the booking is refused with the clash named — it is never stored and found later.
Changing the time, the table or the duration re-runs the same check. A booking pushed half an hour later cannot quietly collide with the one after it.
A cancelled or no-show booking can be reopened, but the slot may have gone in the meantime. Reopening runs the check again rather than assuming the table is still free.
Cancelled and no-show bookings are excluded from the check, so the slot is genuinely available to the next guest the moment it is marked.
Reservations is useful alone. It gets better attached, because the guest who booked is the same record that orders, pays and comes back.
Bookings are assigned to the same tables the POS seats and the QR cards are printed for — one set of tables, not a parallel list.
A drag-and-drop canvas with zones for indoor, terrace and majlis, so a seating preference means something concrete.
The seated table is the table the till opens a check on. The booking and the bill are the same evening, not two records.
The phone number on the booking resolves the guest profile, so an anniversary two years running is something you can see.
A guest who books directly and eats regularly is exactly who a loyalty tier is for.
A rating request after the meal, closing the loop on the booking that started it.
Products are switched on individually — see the full catalogue and prices on the products page.
The clash check is universal. What else you get out of it is not.
Built around how people here actually make a booking.
A confirmation in the thread the guest already uses, rather than an email they will not open. It goes out when a phone number is on file and your WhatsApp Business number is connected.
The public booking page runs in English and Arabic with proper right-to-left layout, so a guest books in the language they think in.
Seating preference is captured on the booking, and with Floor Plan those zones exist on a canvas rather than only in a host’s head.
Duration is per booking, not a fixed turn time. An iftar table that sits for three hours is booked as three hours, and the overlap check works from that.
Two ways to get it: add it to the plan you already pay for, or move to the plan that bundles it. Either way there is no fee per booking or per cover.
Start with a Tahlib plan, then add the products you need — or move to a plan that already includes them.
Yes. You get a public booking page under your own restaurant link, which you can put on your site, your Instagram bio or a QR card. Bookings taken there cost you nothing per cover.
That is the main thing it does. Before a booking is written, the system checks every other booking on that table whose time window overlaps, and refuses the clash rather than recording it. The same check runs again if you move or lengthen a booking, or reopen a cancelled one.
Ninety minutes by default, and you can set a different duration per booking. That matters for long sittings — an iftar table or a shisha booking is booked for the time it will actually take, and the overlap check works from that number.
Yes, over WhatsApp, when a phone number is on file. It needs your WhatsApp Business number connected to send — until then the booking is still recorded and your team is notified in-app, but the guest is not messaged.
Yes. They cancel from their own booking link, confirmed against the phone number on the booking. The table is released immediately, so the slot is genuinely free for the next guest.
A walk-in is a pending booking, so it sits on the same board as everything else. The waitlist view shows every pending party in one list; when a table frees you confirm it and seat it exactly like a booking.
No. The waitlist is a queue you work, not an estimator — it does not calculate or display a wait time. If quoted waits are important to you, that is worth saying before you commit.
Yes. No-show is a real status rather than a deleted row, so you can see how often it happens and to whom. A no-show can be reopened later if the guest turns up after all, and the table check runs again.
Yes — the guest-facing booking page runs in English and Arabic with right-to-left layout. The staff-side bookings dashboard is currently English only; that translation is a known gap we are closing.
Yes. Bookings are assigned to your real tables — the same ones the till seats and the QR cards are printed for. With the Floor Plan product those tables sit on a canvas with zones for indoor, terrace and majlis.
Two ways. Add it to the paid plan you are already on, at its own monthly price per branch, with a 14-day free trial. Or move to the plan that bundles it. Either way there is no fee per booking or per cover — the pricing section above shows both routes.
Put a booking page on your own link, work walk-ins and reservations from one board, and stop finding out about a clash when both parties arrive.
No card to start · nothing to install · cancel whenever