Automatic restaurant reservation confirmation
Confirming a reservation shouldn't require a phone call. A simple, actionable message solves the same problem without taking up anyone's time.

Confirming reservations by phone, one by one, is a task that consumes real-time when the restaurant is already preparing for service. It is also a task that depends on the customer answering the call—and when they don't, the reservation stays in a sort of limbo, without clear confirmation.
This guide shows how to set up an automatic confirmation flow via WhatsApp in four steps, using the automation builder from WhatSMS.
Step 1 — Create the automatic confirmation flow
In the visual flow editor, drag a time-based trigger node (for example, a few hours before the reservation) followed by a message node with the confirmation template. As soon as a reservation is recorded—via WhatsApp or another channel connected to the calendar—the flow triggers automatically, without anyone on the team needing to type or call manually.
Step 2 — Define the message and expected responses
Edit the node text to ask for a clear confirmation—"confirm" or "cancel"—and associate a condition node with each possible response. An unusual request, such as a large group reservation that requires special table adjustments, can be routed to a human agent instead of following the rest of the automatic flow. For more critical dates—the eve of a holiday, a private event—the same flow can escalate to a phone call instead of ending just with the message confirmation.
Step 3 — Handle reservations that receive no response
If the customer does not respond within the defined deadline, the reservation is neither automatically cancelled nor confirmed—it remains visible as pending on the dashboard, and the team decides whether to send a second reminder or contact them directly, with the full history of the conversation already in view.
Step 4 — Adjust the lead time by service type
The time trigger is configurable per flow: a Friday night dinner might justify confirmation closer to the time than a Tuesday lunch. Adjust the lead time according to the no-show patterns observed for each type of service—on nights with higher demand, when the number of reservations to confirm is higher, this is precisely when the team has the least time available for calls and when this automation is most noticeable.
The impact on service
A team that no longer needs to make manual phone confirmations gains time to focus on the actual preparation for service—a resource that is scarcer than the time spent on repetitive calls. This predictability also benefits kitchen planning, which now has a more reliable estimate of the actual number of customers expected for each service.
You can create this confirmation flow for free and test it with your restaurant's real reservations before any commitment.
Frequently asked questions
Does the customer need to have the restaurant's number saved in their contacts?
No. The confirmation message arrives as a regular WhatsApp Business conversation; the customer replies directly there, without any prior configuration on their part.
What happens if the customer doesn't respond within the deadline?
The reservation is neither cancelled nor confirmed automatically—it remains visible as pending on the dashboard, and the team decides whether to send a second reminder or contact the customer directly.
Can I handle large group reservations differently?
Yes. The flow's condition node can route these cases to a human agent, or even escalate to a phone call on more critical dates, instead of following the standard automatic path.
How long before the reservation should I send the confirmation?
It is configurable in the flow trigger. A common starting point is a few hours before the reservation, adjustable according to the type of service and the restaurant's no-show patterns.
Does this completely replace phone confirmation?
In most cases, yes—but the flow can maintain the phone call as an alternative for specific situations, such as large group reservations or dates with a higher risk of no-shows.