Chat, take orders, and
notify guests on WhatsApp.

Yes. Outbound messaging starts with consent, not with a phone number. Opt-in can be captured at the points guests already reach you — during checkout or when they book a table — and the consent state is recorded against the guest profile and synced across every interaction, so your team can see whether someone has agreed before anything goes out. There is no facility for messaging people who have not opted in, and importing numbers from somewhere else does not create consent. What counts as valid consent, and what you tell guests at the moment you collect it, is set by your jurisdiction, by WhatsApp's own policies and by your privacy notice. Vertex records the consent you capture and honours it; it cannot judge whether you obtained it properly.

No, and the two are worth keeping firmly apart. A confirmation that an order is being prepared, a reminder an hour before a booking, or a delivery-tracking update is a transactional or utility message tied to something the guest asked you for. A promotion, an offer or a win-back message is marketing. Under WhatsApp's own messaging rules and under most privacy and e-marketing law these carry different requirements — marketing generally needs its own clearly worded opt-in, and a guest agreeing to receive order updates has not agreed to receive offers. Vertex records the consent you capture and sends the templates you configure; deciding which guests may receive marketing, and wording the opt-in so it genuinely covers marketing, is your call as the operator. Marketing templates also go through WhatsApp's review before they can be sent.

Any guest can stop at any time. One-Click Stop honours "Stop" keywords in line with WhatsApp's standards, and the opt-out is written back to the guest profile and synced across interactions so the same person is not quietly re-added by another part of the system. Treat an opt-out as covering marketing at minimum, and honour it promptly and in full. Guests will also ask to stop by other routes — in person, over the phone, by email, or in the middle of a thread without using the keyword — and those requests are exactly as valid; getting them onto the guest record is part of your process rather than something an automated keyword rule can do on your behalf.

No, and be wary of any vendor that says it does. What Vertex gives you is consent capture at checkout and booking, opt-out handling, a visible record of consent state on the guest profile, and guest data handling designed to support obligations under regimes such as GDPR and CCPA. Those are tools that help you capture and honour consent — they are not a certification, an audit or a legal opinion. Your lawful basis for processing guest data, your privacy notice, your retention decisions, how you answer access and deletion requests, and your standing under WhatsApp's own business messaging policy all remain yours as the operator. Read this page as a description of features, and treat your own counsel as the authority on whether your messaging programme is compliant.

Vertex detects delivery failures and can route the message over a fallback channel — SMS through Twilio, then email through SendGrid, in priority order — so a guest who is offline or unreachable on WhatsApp still has a path to the update. That is a fallback route, not a delivery promise: no platform can guarantee that a message is delivered, opened or read, and networks, handsets and WhatsApp itself sit outside anyone's control. Consent does not travel between channels either. A guest who agreed to WhatsApp updates has not thereby agreed to SMS or email, so fallback should only use channels that guest has separately agreed to, and any marketing send needs marketing consent on the specific channel it goes out on.