A restaurant's messaging problem is unusual: a table at 7pm on Saturday is worth a great deal at 5pm and nothing at 8pm. That makes speed the whole value, and it makes most scheduled messaging beside the point.
What the systems know
- Reservation platforms know the booking, the party size and the no-show history. That last one is more useful than people realise.
- Toast and Square know the check — what was ordered and what was spent — plus loyalty membership where you run one.
- Online ordering knows the order status, which is the one genuinely expected notification in this whole category.
The messages worth sending
| Message | Verdict | Why |
|---|---|---|
| Order ready for collection | Send it | Expected, useful, reduces counter crowding |
| Reservation confirmation | Send it | Standard, and reduces no-shows |
| Same-day cancellation fill | The best play here | Perishable inventory, conversational channel |
| Reservation reminder | Only if the platform is not already sending one | Two reminders is worse than one |
| Weekly specials blast | Do not | This is what email and social are for |
| Birthday offer | Sparingly, if it is genuinely good | Otherwise it reads as a database, not a welcome |
The cancellation fill is the one to build. A 7pm four-cover cancels at 4pm; a short message to a waitlist, first reply wins, and the table is sold. That is real money and it needs a conversational channel to work. The Saturday rush mechanics.
Restaurants are the easiest business to over-message
Your customers eat out often and hear from a lot of restaurants. The frequency ceiling is lower here than almost anywhere: a promotional message more than about once a month reads as noise, and the opt-out rate will tell you so. Spend the channel on logistics and the cancellation fill, not on specials.
Integration reality
Toast has a partner API programme; reservation platforms vary considerably in what they expose. As with salon software, confirm what your actual plan includes before designing around it — and note that a waitlist fill can be run from a simple list without any integration at all. The play matters more than the plumbing.
Build order
- Order-ready notification, if you do takeaway. Most expected, least risky.
- Cancellation fill from a waitlist. Highest revenue impact.
- Reservation confirmation, only if the platform is not already sending one.
- Nothing promotional until the above are working and measured.
- A frequency cap of roughly one non-transactional message a month.