Restaurant booking systems

What the assistant does today

It answers, asks, and puts the booking in your dashboard as an appointment. That holds:

• the guest’s name and phone number;
• the day and the time, as an appointment on a slot;
• anything else that was said — the number of people, an allergy, a high chair, a birthday — in the call summary. Party size is not a separate field you can filter on.

Be aware of this: the assistant tells the guest the booking is made. It does not ask them to wait for a confirmation, and it does not look at your floor plan — it does not know whether you are full or whether the table fits. So the booking is a time slot, not a table.

You then put the booking into your own system yourself, and call the guest if it turns out not to work.

Zenchef and Guestplan

There is no button in your dashboard that switches these on. We set them up by hand, per account.

Email info@voicehelden.com with which system you use and which restaurant it is for. We will look at what is possible and what it costs — and say so when it is not.

Connecting it yourself with a webhook

If you run your own system, or want the booking request in your CRM, use the webhook: it sends the summary to a URL of yours after every call, from where Zapier, Make or n8n can pass it on. How to set it up is on Connecting your CRM with a webhook. A direct link with Zenchef or Guestplan stays on request.

Appointments on a time slot do work

If you work with time slots rather than tables — a tasting, a private dinner, a room viewing — the assistant can book that itself, in your Google Calendar. It checks whether you are free and puts the appointment in. See Connecting your Google Calendar.

What it does not do

• No table plan, no occupancy, no waiting list.
• No confirmation by text or email to the guest. You send that.
• No cancellations or changes written back into your booking system. The assistant does note them, so you see them.
• No no-show tracking and no deposits.