Field notes on AI-era growth, deliverability, voice, and messaging for developers and teams building on Orbit by Devotel.
When a proactive surface is missing, AI agents only ever react. This post shows the ambient-outreach model on Devotel Orbit — CDP-segment triggers routed through the AI-agent runtime with the full per-event decision trail auditable, plus the tenant-owned consent and quiet-hours controls that govern every send.
DNI swaps the phone number a site visitor sees so an inbound call can be attributed back to the campaign that drove it. This explainer fixes the terminology (DNI vs DNC vs DNO vs TRACED), walks how Devotel Orbit's tracking pools bind a number to a visitor session, shows where attribution lands, and covers the consent, quiet-hours, and IVR/AI-agent routing questions buyers ask before they ship one.
The Eleventh Circuit vacated the FCC's one-to-one consent rule in January 2025 — but seven state mini-TCPA overlays and the federal 8-to-9 recipient-local window never depended on it. This explainer bridges the vacatur news to the controls a Devotel Orbit tenant actually configures: state-calling-window intersections, refuse-by-default marketing posture, audit-logged opt-in receipts, and known-litigator scrub.
SMS marketing runs on a different rulebook than transactional SMS — promotional consent classes, quiet hours, 10DLC campaign registration, opt-out SLA, and a metrics surface that tells delivered from clicked. This playbook defines the marketing-as-program discipline, works through the marketing vs transactional class boundary, and maps every control to the tenant-owned surface in Devotel Orbit that enforces it.
Delivery updates fail at the fallback layer, not the channel layer. This explainer covers the logistics notification problem on Devotel Orbit end to end. It walks which channels carry the shipment message, the tenant-owned quiet-hours and consent controls, pay-by-link for duties and surcharges, Verify for sign-up, and wallet passes for the boarding pass your customer keeps.
The cross-channel quiet-hours policy — recipient-local send windows that gate outbound sends — is now readable and writable through the workspace settings API. Two endpoints expose the policy document and the effective window per channel, so an organization that manages compliance configuration in code no longer clicks through the dashboard to review or change its send windows.
The federal TCPA window (8 AM–9 PM recipient-local) is the floor, seven US states run stricter overlays, and the result depends on how they intersect. This guide walks through the difference, per-state deferral examples, and how to read the state-calling-windows reference page so an Orbit tenant can schedule compliantly without guessing.
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.