Where the Hub fits beside your POS and reservation book

Your POS and your reservation system keep the covers and the table. The Hub adds the channel to the guests who chose to hear from you.

What this helps you do

Your point-of-sale keeps the checks, your reservation platform keeps the bookings and the table plan, and your loyalty or gift-card system keeps the balances. The Hub holds only the guests who connected, the audiences they picked, and what you sent them. It does not know tonight's covers, so a standby seat or an hours change is something a person sends the moment the floor knows. Whatever the system, the doors are the same four: a CSV export you upload on Connections, the inbound webhook that invites one person at a time, signed outbound events that tell your systems who connected or replied, and the Zapier app when both ends are apps rather than code.

When to use it

Use CSV when the opted-in part of your loyalty or mailing list is what you already have. Use the inbound webhook when a booking confirmation or a signup form should invite a guest the same evening. Use outbound events when your own list should learn who connected. Most restaurants start with the table tent and the receipt alone.

How to do it

  • Export the opted-in guests from your loyalty or mailing list and upload the CSV on Connections.
  • Point the confirmation step of your booking or signup form at the inbound webhook on Integrations.
  • Add your HTTPS endpoint under events out if a spreadsheet or CRM should hear about new connections and replies.
  • Ask for the Zapier app to connect the two ends without code.
  • Send the closure, the hours change or the standby seat from Send as soon as the floor knows. Nothing watches your book for you.

Example

A restaurant uploads its opted-in loyalty list and puts the code on the table tent. A pipe bursts at four; the manager sends one Blast to All Guests about tonight's closure and answers the replies in Conversations. The reservation book never moved, and no integration was involved.

Good to know

  • There is no POS, reservation or delivery-platform connector. A booking stays in the system that took it.
  • The Hub takes no payments, holds no card and cannot confirm or cancel a reservation on a guest's behalf.
  • A YES or NO reply to a standby offer is the guest's own action, which the Hub counts. It is not a booking.

Do it in your Hub

Inside your Hub, Help shows this same article next to the screen it describes. Sign in at restaurantblasts.com or right here.