Field notes on AI-era growth, deliverability, voice, and messaging for developers and teams building on Orbit by Devotel.
A2P messaging week in brief by Devotel Orbit: the OTT twist loop reshaping SMS-only programs, the WhatsApp quality-rating wave one month in, carrier interconnect and metering shifts since Q3, what Orbit shipped in September, and a QA checklist to close the week.
Orbit vs Karix: India A2P/DLT routing, honest parity, and where an India-first incumbent beats a global single-wallet platform (and where Orbit wins).
The US runs long-code A2P on TCR-registered 10DLC with per-carrier approval tracking; Canada runs it on short codes, long codes, and registered alphanumeric sender IDs under carrier self-regulation. A sender-id regime that works in one country silently misconfigures in the other, so cross-border programs need a per-country registration map. This playbook covers the carrier-by-carrier split, registration windows, sender-id posture, and opt-out handling for both.
The H2 2026 carrier-fee wave on application-to-person SMS — per-message surcharges and per-message-versus-per-conversation billing moves across Twilio, Vonage, and Infobip — and the four-step repricing pass every sender should run against a published per-destination rate card.
The EU's Unfair Commercial Practices Directive (UCPD) backs regulators' coordinated dark-pattern sweeps on checkout and messaging flows. What it means for A2P senders, mapped to the tenant-owned controls Devotel Orbit actually ships.
India's DPDP Phase II deadline lands 13 November 2026, bringing the Consent-Manager model into enforcement for consent-based A2P SMS into India. What signed consent receipts are in business terms, who must act, and the verification surface Devotel Orbit ships.
Interconnect fees on A2P SMS in plain terms — the three components of a per-message price, which inter-operator fee layers a bare "carrier surcharge" line can hide, and how to reprice your messaging from a transparent rate card instead of an invoice surprise.
Quiet hours and send-time optimization are evaluated on recipient-local time, not UTC. When a waiting message pins the send window to UTC, daylight saving shifts move its Local delivery hour and it lands inside the owner's blocked window. This post defines quiet hours and STO, works through the DST failure mode with a concrete example, and shows how to configure recipient-local send windows that survive clock shifts as tenant-side controls.
Start free and ship your first voice, messaging, or email flow today, or talk to our team about your rollout. No annual contract, one pay-as-you-go bill across every channel.