Working documentation, in your vertical's terms
RestaurantBlasts documentation
The Hub is one platform. Its workflows and terminology adapt to the organization running it: on RestaurantBlasts, the audience that reaches everyone is called All Guests and the people you reach are guests. The pages below are the how, written in that vocabulary; the shared topics further down are identical for every vertical.
Deciding whether the Hub fits a restaurant? That case is made at restaurantblasts.com, not here.
RestaurantBlasts topics
01Turn guests into a direct audienceInvite guests at the reservation, the loyalty signup and the check, then reach them again.02Organize regulars, VIPs and event guestsSend the chef's table to your VIPs first and a closure to everyone with a table booked.03Give managers the right accessLet each manager reach their own guests while the owner keeps the All Guests sends and billing.04Send a closure, a change or tonight's newsGet an hours change, a sold-out notice or tonight's offer onto your guests' phones in minutes.05Take reservations and answer guests one to oneReplies to an offer land in one inbox, and the host stand or the events coordinator picks each one up.06Plan daily specials and weekly picks in advanceWrite a week of specials on Sunday and let each one go out at 11 a.m. on its day.07Welcome each new guest automaticallyGive every new guest the same first-week sequence, timed from the day they connect.08Run the countdown to a wine dinner or a holiday nightBuild the reservation call, the menu reveal, the doors-open note and the thank-you around one date, once.09Data in, data outCSV import, an inbound webhook, signed outbound events and a Zapier app. There is no POS or reservation connector.10Understand your creditsOne prepaid credit per guest, credits that never expire, and no per-message carrier bill.11Manage delivery problems and reconnectionSee why a notice did not reach a guest, and what, if anything, to do about it.12Set up RestaurantBlasts for your restaurantGet your restaurant profile, timezone, sending address and guest preferences page ready in a few minutes.
Shared Hub topics
These work the same way on RestaurantBlasts as on every other vertical, so they live once, in the platform documentation.
13What the Hub isOne engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.14Blasts and email, side by sidePeople who prefer email still hear everything, from your organization's own address.15Campaigns: three ways to send over timeContent Series on the calendar, Journeys relative to each person, Event Campaigns around one date.16Every way people can connectEnrollment code, QR code, printed kit, connect links, invitations, CSV, and a webhook.17Security, ownership, and leavingThe organization owns everything. Leaving takes one confirmation and emails a complete export.18External content and FlowAutomated producers file content through signed ingest; a human reviews it and explicitly publishes.
Ready to work in your Hub?
Sign in at restaurantblasts.com or right here. Inside your Hub, Help shows these same articles next to the screen each one describes.