· 4 min · TextMeFlow Team

WhatsApp for Restaurants: Booking Confirmations and Pickup Alerts

A reservation that doesn't show up costs a restaurant a table that can no longer be sold. Confirming by phone costs staff time during the busiest hours. WhatsApp solves both: the message gets read (open rates around 95%, much higher than SMS or email) and the customer can reply with a single word without calling.

This article shows three concrete flows you can build with the TextMeFlow API: a booking confirmation, a reminder, and a pickup notification.

Why WhatsApp works better than phone or email for hospitality

A reservation system (or a simple form on your website) already collects a phone number. You don't need to ask for anything extra. You simply use a different channel to confirm. Advantages over the classic approach:

  • No phone queue during the lunch hour, when bookings and orders come in at the same time.
  • An automatic reminder on the day itself demonstrably reduces no-shows, without anyone making a call.
  • One word is enough to reply ("OK", "cancel"), which lowers the barrier for the customer.

For transactional messages such as a booking confirmation, you can usually rely on performance of the contract as the legal basis: the customer made a reservation, so they expect that confirmation. Do ask explicitly at booking whether WhatsApp is okay, and respect STOP requests. More on that in our article on GDPR and sending WhatsApp messages.

Disclaimer: this is general information, not legal advice for your specific situation.

Flow 1: Booking confirmation

As soon as a customer books (via your website, entered by staff over the phone, or through a reservation tool), you send a confirmation right away:

curl -X POST https://api.textmeflow.eu/v1/messages \
  -H "Authorization: Bearer $TMF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+32470123456",
    "type": "text",
    "text": "Confirmed: table for 4, Friday 8 pm at Bistro Centraal. Reply CANCEL if it no longer works for you."
  }'

The full endpoint specification (headers, response codes, error handling) is in the API documentation.

Flow 2: Reminder on the day itself

Schedule a reminder a few hours before the reservation using a cron job or your reservation system. This is the message that makes the biggest difference against no-shows, because it still gives the customer the chance to cancel in time instead of simply not turning up:

curl -X POST https://api.textmeflow.eu/v1/messages \
  -H "Authorization: Bearer $TMF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+32470123456",
    "type": "text",
    "text": "See you tonight at 8 pm at Bistro Centraal! If you cannot make it after all, reply CANCEL and we will release the table."
  }'

Keep in mind the quiet hours of the anti-spam pipeline: scheduled messages that fall outside the permitted hours are automatically deferred until the next permitted window. That way you never accidentally send a reminder at 6 am.

Flow 3: "Your pickup order is ready"

For pickup and takeaway the pattern is slightly different: the trigger isn't a time but a status change in the kitchen or your point-of-sale system. As soon as an order is set to "ready", your system fires a webhook or a direct API call to TextMeFlow:

curl -X POST https://api.textmeflow.eu/v1/messages \
  -H "Authorization: Bearer $TMF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+32470123456",
    "type": "text",
    "text": "Your order #482 is ready for pickup! We will keep it warm until 7:30 pm."
  }'

If you also want to attach a photo of the bill or the menu (for example for a group order), the API supports media up to 100 MB per message.

Processing replies

Customers who reply "CANCEL" need to be recognised and processed by your system, not read manually on a phone. You can do that with a webhook that sends incoming messages to your server as soon as they arrive. The webhook calls are HMAC-signed, so you can be sure the message really comes from TextMeFlow and hasn't been forged. The complete setup (payload format, signature verification, retries) is in the webhooks documentation.

One number, multiple staff members

Larger venues with separate kitchen and floor teams often want several people to be able to read along and reply from the same WhatsApp number. That's possible from the Business plan with multi-device support, so the head waiter and the manager have access at the same time without one phone becoming the bottleneck.

Getting started

A booking confirmation, a reminder and a pickup notification can be built with a few API calls on top of the reservation system or till you already have. No separate app for your customers, no installation: just WhatsApp, which they're already using.

Try TextMeFlow for free: 50 messages per month, forever, no credit card needed.

Want to send WhatsApp messages via API yourself?

Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.

Free forever