Messages missed during service
19:00–22:00 is both the busiest hour on the floor and the busiest on WhatsApp. Messages get read after service, and that is usually too late.
The 2am booking shouldn't wait until morning.
In restaurants and cafés a serious share of reservation requests land after service closes. By the time anyone reads them, the guest has found somewhere else. Bekir is on the line at that hour.
The room is full and the phone is ringing.
Lost reservations usually aren't about having no table — they're about nobody being able to answer. During the evening rush you cannot watch the floor and the phone at once.
Night and closed-day traffic
Weekend plans are made at night. If you're closed Monday, Saturday's request waits until Monday — the guest doesn't.
The same three questions
Is there parking, is the garden open, is there a children's menu. Bekir closes these itself and leaves the team the real work.
The booking that never finishes
"I'll check and come back" doesn't close. Bekir takes the party size, time and preference in the same conversation and finishes it.
What it actually closes.
In a restaurant Bekir doesn't just answer questions; it effectively keeps the reservation book.
01 Takes reservations
Collects date, time, party size and garden/indoor preference by talking; checks availability and holds the table.
02 Handles changes and cancellations
Time shifts, party-size updates and cancellations come through the same chat and the book is updated.
03 Answers menu and price questions
Average per head, kitchen hours, vegetarian and children's options — answered from what you provided.
04 Collects special requests
Birthday cake, table decoration, a quiet corner — noted and passed to the team.
05 Escalates group bookings
Requests above the party size you set aren't closed on its own; they're summarised and handed to a manager.
06 Remembers the guest
Knows the table a returning guest prefers and what they didn't like. They don't have to explain themselves again.
You draw the line: what Bekir may decide and where it brings you in is defined together at setup. Need something built for your own process?
Restaurant questions
Does it connect to our reservation system?
We handle whether it needs to connect to your reservation or POS system in the setup call. When connected, Bekir reads table status from the source; when not, it works from the capacity rules you give it.
Could it double-book a table?
No. It works from your capacity rules and existing reservations, and where it can't be certain it asks for confirmation and hands over to you.
Can we keep our current restaurant number?
Yes. Bekir takes over the WhatsApp line your guests already message; the number on your sign doesn't change.
How many conversations can it run at peak?
It doesn't queue, and in practice concurrency isn't the constraint. We size the plan on the call by looking at your actual message traffic.
Will guests know it's an AI?
How it introduces itself is configurable — we decide it together based on your sector's rules and your preference.
Let Bekir take this Saturday's bookings.
Let's look at a week of your WhatsApp traffic and count how many reservations went unanswered.