Automotive messaging on Orbit
Recall notices, service reminders, and dealership follow-ups arrive with different legal weight and urgency — and the OEM needs proof a safety-class recall notice reached every owner. Splitting recall lanes, service reminders, and sales follow-ups across vendors makes opt-out propagation and per-notice delivery proof impossible to defend.
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 notice class — Safety recall notices, service reminders, and marketing follow-ups each assert a consent basis your dealership program labels; enforcement is the platform's send gate.
- Quiet hours for courtesy lanes — Service reminders and sales follow-ups respect your recipient local-time rest windows; safety recall notices bypass by policy.
- Owner opt-out — STOP on a service-reminder blast propagates through the shared suppression list so the marketing sequences stop too.
- Brand registrations — The dealership program owns the sender identity — per-brand 10DLC campaigns and WhatsApp templates held by the workspace.
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 — Recall and service reminders — the reliable floor for owner reach.
- WhatsApp — Dealer-service coordination: appointment confirmations, parts-arrival threads, and photo intake.
- RCS — Rich recall/book-a-service cards with SMS fallback.
- Voice — Dealership callbacks, IVR recall status checks, escalations.
- Email — Long-form recall documentation and warranty-service correspondence.
The buyer-explainer for Automotive
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: Automotive messaging, the buyer's explainer.
Evaluating Orbit for automotive?
If your procurement review needs a security questionnaire response, volume pricing, or an enterprise terms discussion for automotive traffic, talk to us.