WalletPlusThe Restaurant module · table booking
The ones who stay seated, too.
Takeaway is one half of it. If you have tables, the guest should be able to reserve one on the same site, in the same flow and with the same profile, instead of calling during a busy Friday service and hoping somebody picks up. Table booking is part of the Restaurant module.
The figures come from the reservations that have actually come in through the system. The largest table booking so far was for nine people.
The guest's side
Four fields, and the table is requested.
01
They tap “Book a table”
The button sits on your front page and on the contact page. You decide whether it goes in both places or just one.
02
Date, time and number of people
Plus name and phone. The notes field is optional. That is where the high chair and the allergy get written.
03
They are told it is a request
Not a confirmation. That is a deliberate difference: you need a chance to say no to a table for nine at 7 pm on a Friday.
04
The confirmation comes once you say yes
By SMS or email. You choose which. If you say no, they are told that too, so nobody turns up at the door for nothing.
Your side
It lands in the same place as the orders.
The reservation comes into backoffice beside the takeaway orders. Two buttons: accept or decline. There is no third screen to keep an eye on.
Accept or decline with one tap
The decision can only be made once. If two people in the kitchen tap at the same time, the guest still gets only one message.
You choose the channel
SMS has a per-message price and is read straight away. Email is included in the price. Most choose SMS for table bookings.
The guest is the same as online
If they book a table and order takeaway the week after, it is one profile in the loyalty club, not two.
Switch it on and off
If you close the kitchen to parties in December, you switch the button off without touching the rest of the site.
The note comes along
High chair, wheelchair, allergy, birthday. It is on the reservation when you open it.
Payment per booking
Only for the reservations that actually come in. The SMS confirmation has its own per-message price; if you choose email, it is included in the price. Contact us for a price.
What we are building now
From requests to real table management.
Requests and approvals are running today. What is missing is everything that makes it a booking system rather than a form, and that is what we are working on right now.
Tables and capacity
How many tables you have and how many can sit at each, so the system says no by itself when you are full.
Available times instead of a blank field
The guest chooses between the times there is actually room for, and you are spared having to decline.
Calendar overview
The evening as a list: who is coming when, how many they are, and what the note says.
Automatic approval
Fewer than four people on a Tuesday does not need a human. More than that does.
A reminder the day before
An SMS with the option to cancel. Empty tables cost more than a message.
Sittings and last table
Two hours per table, last reservation an hour and a half before closing. You set the limits, not us.
We are building it together with the restaurants that have tables. If you want a say in how table management should work, tell us. It is easier to shape now than afterwards.
Why it hangs together
The same guest, whether they collect or sit down.
In most places it is the same people. They collect on Friday and book a table for their mother's birthday the month after. If those two things sit in separate systems, neither knows it is the same person, and then you can neither say thank you nor write to them.
Next step
If you have tables, say the word.
We switch table booking on for your site while we are on the phone, and you pay nothing until a reservation actually comes in. And if you want to help shape table management, we would gladly take your kitchen's advice.
Or call: 61 10 00 83 · sales on weekdays 10–16