Restaurants and hospitality

The Friday-night table request no longer waits until Monday

Between 5 and 8pm twenty messages arrive at once: a table for 6, a party that wants to push it back an hour, someone asking whether you can do gluten-free. Those messages land on one number, and nobody types the confirmation or the reminder by hand anymore.

30 days free, no credit card required

Prefer a hand getting started? We'll get you started

No setup fees
No commitment
09:41
BL
Bij Loes
online
Today
Hi, any room for 6 on Friday around 7:30?
17:42
Automated
Passing your request on: Friday, 6 people, 7:30pm. Our host will get back to you tonight.
17:42
Great. Two of us eat gluten-free, is that possible?
17:44
No problem, the kitchen always has a gluten-free dish. Your table for 6 is booked for Friday at 7:30.
18:55
How it works today

Where it breaks during service

  • The phone rings in the middle of service, while everyone is on the floor or at the pass.
  • Bookings come in through the website form, Instagram, and the host's personal number.
  • A party cancels in the morning and the table stays empty, because nobody calls the waiting list.
  • Guests who ate with you yesterday never get asked to leave a review.
The guest journey

From request to the day after

Request

A guest sends the date, the time and the number of people. The flow puts those details next to the conversation, so whoever is on shift only has to say yes or no.

Confirmation

Once the booking is fixed, the confirmation goes into the chat with the time, party size and address.

Day before

A reminder the day before the visit, asking the guest to let you know if the party gets smaller or larger.

Special requests

Allergies, a high chair or a cake with dessert sit in the same conversation, so the kitchen can look them up.

Afterwards

A day later the review request goes out, only to the guests who actually came and ate.

How restaurants use it

A typical week

A table opens up

When a party cancels, 1 message goes to the guests you had to turn away earlier.

Questions about the menu

Opening hours, the terrace and gluten-free options get answered from the information you've added.

Groups and catering

A request for 20 arrives with the date, headcount and occasion already filled in.

A review after the visit

The review request goes out on the day the visit is still fresh in the guest's memory.

Terrace opening or Christmas menu

One message to your regulars, sent at the moment you choose.

Floor, kitchen and office

Everyone works in the same inbox, so a guest never gets two different answers.

That's how other restaurants use it. Have a different idea for your guests? We'll build it.

In practice

A hospitality business in its own words

In hospitality, reviews matter. With Tobachat they come in without you having to ask. Smart system, easy to use.

Integrations

What your booking system passes on

We don't integrate directly with reservation systems. When yours sends a new booking or a cancellation to Zapier or a webhook, the flow picks it up and sends the matching message. You can only message a guest first once they've given permission. If your reservation system or point of sale can't do this, tell us and we'll build the connection to the system you already use.

Price

What it costs

Automations come with every plan, integrations start at Growth. Meta charges separately for each message you send, with no markup from us.

Frequently asked questions

About WhatsApp in hospitality

The request arrives as a message and the flow asks for the date, the time and the party size. Those details sit next to the conversation, so whoever is on shift can say yes or no at a glance.

We don't reserve the table ourselves: we have no floor plan, so nothing is booked automatically. Someone on your team confirms, and that message goes back into the chat.

Launch your first restaurant flow.

30 days free, no credit card required.

Prefer a hand getting started? We'll get you started

30 days free, no credit card required No setup fees No commitment