Logistics messaging on Orbit
Delivery notifications, dispatch changes, and driver's last-reply handling fail when each is a different vendor. The most expensive status exception is the one a customer never heard about — but the second-most expensive is a dispatch change that landed in the wrong inbox because delivery alerts, driver replies, and WISMO (where-is-my-order) tickets run on three platforms.
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.
- Transactional vs promotional split — Delivery updates and pickup-window alerts classify as transactional in your workspace; the promotional membership or upsell sends on consent classes your team labels per flow.
- Quiet hours for reminder tiers — Out-of-route notifications arrive at 07:00–22:00 rest windows you set per region, while failed-delivery urgent exceptions bypass the window when your policy marks them urgent.
- Opt-out across channels — Unsubscribe from SMS notifications propagates to email and WhatsApp tracking links the moment your suppression workflow fires.
- Sender registrations per region — Per-region brand and campaign registrations (US 10DLC, EU sender IDs) remain tenant-owned — no shared-destination shortcuts.
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 — Delivery ETA and exception alerts — the reliable floor for time-critical updates.
- WhatsApp — Two-way driver/customer coordination and photo-proof-of-delivery threads.
- RCS — Rich tracking cards (out-for-delivery, signature options) with SMS fallback.
- Voice — Dispatch escalation and rescheduled-delivery conversations; IVR self-serve for tracking lookups.
- Email — Shipment confirmations, customs documents, and long-form manifests.
The buyer-explainer for Logistics
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: Logistics messaging, the buyer's explainer.
Evaluating Orbit for logistics?
If your procurement review needs a security questionnaire response, volume pricing, or an enterprise terms discussion for logistics traffic, talk to us.