Travel & hospitality messaging on Orbit
Booking confirmations, itinerary changes, and guest-communications work across SMS, WhatsApp, and voice — but the guest opted out on the SMS 18 months ago when they texted STOP for the wrong vendor's blast, and the front-desk team cannot see the unified timeline across the check-in, concierge, and late-checkout flows.
The tenant-owned compliance posture
Compliance posture on Orbit is tenant-owned: your workspace attests the consent basis per flow, sets the quiet hours, keeps the shared suppression list, and holds the sender registrations. The platform enforces those settings at send time — the controls below are decisions your team owns, not platform mandates switched on for every tenant.
- Consent by guest-touch — Booking confirmations (transactional) and marketing outreach (promotional) declare distinct consent bases per flow; enforcement is your platform's gate.
- Quiet hours for marketing — Promotional and post-stay outreach respect recipient local-time windows; urgent flight-change or safety alerts bypass by policy.
- Guest opt-out — A STOP on the activity-recommendation blast propagates through one suppression list — full-stack suppression per guest.
- Sender registrations — Per-property or per-brand registrations hold the sender identity for SMS and WhatsApp templates, all tenant-owned.
These controls are tenant-owned: your workspace decides the consent basis, the hours, and the list hygiene; the platform enforces your settings at send time.
The channel matrix
Every flow above runs on the same account across the five channels — the fallback chain is a setting you configure once, not a per-channel vendor contract.
- SMS — Booking confirmations, check-in nudges, and flight-change alerts — the floor for on-the-go reach.
- WhatsApp — Two-way concierge chats, activity-booking intake threads, and multilingual guest care.
- RCS — Rich itinerary cards (check-in action, share-the-stay buttons) on supported handsets with SMS fallback.
- Voice — Pre-arrival confirmations, premium concierge callbacks, and IVR self-serve itinerary lookups.
- Email — Long-form itineraries, hotel welcome packets, and post-stay surveys.
The buyer-explainer for Travel & hospitality
The full narrative — what you are actually buying, in what order to evaluate it, and how the channel fallback chain degrades — is the paired buyer-explainer post: Travel & hospitality messaging, the buyer's explainer.
Evaluating Orbit for travel & hospitality?
If your procurement review needs a security questionnaire response, volume pricing, or an enterprise terms discussion for travel & hospitality traffic, talk to us.