Use Case
Reservation reminders while the table can still be filled
Confirm tomorrow’s bookings today, turn a no-show into a cancellation you can still sell, and see the whole run priced before it leaves.
- Party size and sitting written into the message
- Scheduled at booking, sent the day before
- The whole service priced before approval
Scheduled send
Day before, 11:00
Hi Ana, your table for 4 at [YOUR RESTAURANT] is held for tomorrow at 20:30. If plans changed, call [YOUR NUMBER].
One night of covers, confirmed
Bring the book across
Guest, phone, date, sitting and party size, as the floor already records them.Tomorrow’s covers become an audience
Built from the booking date, and split by the size of the party.The confirmation goes the day before
Early enough that a table given back is a table you can sell again.Read the report
Every number accounted for before the doors open.
A booking is confirmed away from the table
The guest who reserved last week is out of the house, mid afternoon, holding a phone with nothing of yours installed on it.
It reaches a guest who is out
The confirmation arrives wherever the day has taken them, among the messages from the people they are bringing with them. And if the answer is no, the number to call is in the same line.
There is nothing to install first
No app, no account, no password to recover on the way to somewhere else. The phone that took the booking is already the phone that confirms it.
It goes at the hour the house picks
Schedule a send from 30 minutes to 365 days ahead, so tomorrow’s bookings are confirmed late morning, with a service still left to resell the table in, rather than whenever someone remembers between two covers.
Set it up once, then run it every service
The first night takes an afternoon. After that only the date changes.
Import the reservation book
Bring guests in with the booking date, the sitting, the party size and whatever the floor notes beside them. Each one becomes an attribute you can write with.
Pick tomorrow’s covers
Build a reusable audience on the booking date. Audiences read the rule again each time you use them, so a table released this morning is not messaged tonight.
Write the confirmation, and the one for the big table
Personalize with the guest name, the time and the party size. The preview counts the length and the price as you type, so a longer line for a party of ten is a decision rather than a surprise.
Schedule it, then read the report
Pick the hour, review the guests and the total, and approve. Each confirmation is then tracked to delivery in reporting, so you know which ones arrived while there was still time to sell the table again.
The booking already knows what to say
Tomorrow’s covers are an audience, not a list somebody retypes between services. The booking date the house already keeps is the rule, and the audience reads it on the day it sends.
Party size, sitting and table note come across as attributes, so the message can use them. A two-top gets the time and where to park; a party of ten gets the set menu and the hour the kitchen needs a final number by. One run, one audience, different words. More on the trade in restaurants and hospitality.
