One hub for Devotel Orbit product news: what shipped by month, what is generally available, and the announcements that matter — each resolved to the docs.
What shipped — by month
One rollup per month, resolved to the shipped capability and the docs page a buyer checks. GA means live on every workspace today; Preview means opt-in from the dashboard flag, named on the item.
PreviewQ1 2027 preview — the next quarter's operator agenda (Preview)
The quarter's preview post: the shipped record carried forward (WhatsApp Flows validation, the quiet-hours settings API, localized video waiting rooms, PII-vault batch grouping, multi-WABA deep links) and an explicitly Preview-only look at where each pillar heads next — no dates promised.
PreviewQ4 2026 preview — the forward look grounded in shipped releases (Preview)
The quarter's preview post: what shipped across August–October 2026 (WhatsApp Flows version pinning, the quiet-hours settings API, localized video waiting rooms, PII-vault batch grouping, multi-WABA deep links) and an explicitly Preview-only look at where each pillar heads next — no dates promised.
GAWhatsApp Flows validate cleanly on first upload (GA)
Every new flow — AI Generate, the visual editor, a template, or pasted JSON — now declares the schema version Meta accepts, pinned again at upload so a draft cannot reintroduce a stale one.
Rooms with a waiting room pick how new joiners queue at capacity, and the full lobby flow — lists, capacity labels, kick-ban — is localized end to end.
GAMulti-WABA deep links resolve the right account (GA)
Bookmarked or external links carrying a WABA id now scope the WhatsApp Messages page to that account instead of silently showing the workspace default.
When a carrier review comes back declined with a request for corrected documents, resubmitting now updates the same review instead of silently starting a new one.
Germany A2P SMS rules, decoded — UWG §7 consent and the Abmahnung economy, double opt-in as the provable standard, the sender-ID blocking reality, NIS2's 2026 tenant posture, WhatsApp opt-in evidence, and the DE send-gate row
A Germany-lane deep-dive for Devotel Orbit customers: UWG §7 consent and the Abmahnung enforcement economy, double opt-in as the provable standard, quiet-hours conventions, why dynamic alphanumeric sender IDs get filtered or replaced on German routes, long-number vs short-code economics, NIS2's 2026 message-security posture for enterprises, WhatsApp opt-in evidence under German consumer-protection precedent, and the DE send-gate row.
RCS Business Messaging in 2026 H2 — global agent coverage and rollout status, Google RBM verified-agent lifecycles, per-country pricing drift, carrier-side quality gates, and how RCS compares to the WhatsApp template-pricing shift
A consolidated industry-news explainer on RCS Business Messaging status in the second half of 2026 — where Apple's iOS RCS expansion landed, which carriers still lag, Google RBM verified-agent lifecycles, per-country pricing drift, carrier-side quality gates, and how RCS compares to WhatsApp's 2026 template-pricing shift.
Workforce management, end to end — the closed loop from forecast to schedule to real-time adherence, plus intraday reforecasting, open-shift/overtime/VTO markets, exception approvals, and payroll export across the built-in CCaaS surface
WFM on Devotel Orbit is the closed loop from forecast to schedule to real-time adherence, built into the contact center rather than licensed separately. A walkthrough of the full shipped WFM surface — intraday staffing, open-shift bidding, overtime and VTO offers, exceptions, timekeeping — with honest parity notes against standalone WFM specialists.
OpenAI's voice moves, decoded for the AI-voice lane — what the 2026 API changes touched, where a direct realtime pipeline still fits, and where production telephony (SIP, attestation, E911) picks up
What the 2026 OpenAI API changes actually shut down for buyers whose agent talks on the phone — what voice-as-product from a model vendor enabled and disabled, the honest case where a direct OpenAI realtime pipeline still fits, and where a production telephony layer (SIP termination, STIR/SHAKEN attestation, A2P routing, E911, published per-minute pricing) picks the work up.
The 2026 year in review and 2027 outlook — the year's twelve shipped changes consolidated from the quarterly reviews and monthly release notes, and the Q1 2027 agenda a buyer should carry into planning
The 2026 year in review and the 2027 outlook — how a shipping year moves from H2 2026 through Q4 2026 into the year-end window, the twelve changes that carried the year on the changelog, the Q1 2027 agenda a buyer should carry into planning, and where the cadence record lives.
In-app messaging operator guide — the owned, zero-carrier-cost feed your web and React Native SDKs render, the push/email/SMS decision matrix, authoring primitives, fallback wiring, and toggle-off governance
How Devotel Orbit's owned in-app channel works — the pull-based feed your web and React Native SDKs render, when in-app beats push, email, and SMS, the content-card and in-app-message authoring primitives under Messages → In-app, fallback-chain wiring, toggle-off semantics, and engagement measurement.
Brand registries and sender registration, decoded — brand-vetting re-vet cycles, the Apple Messages verified-thread lane beside SMS registration, and the tenant-owned read of your route-quality report
Brand-registry and sender-registration programs keep iterating on carrier schedules. This explainer reads the public developments shaping A2P sender identity this quarter, from brand-vetting score retrieval to new registry layers, and shows the tenant-owned controls for keeping sender state legible.
Per-carrier pricing for international messaging — MCCMNC route overrides priced per destination network, dashboard and API paths, and the invoice-verification loop
International SMS rates are not one number per country — they are one number per carrier. Devotel Orbit's MCCMNC override surface at /billing/mccmnc-overrides prices each destination carrier on its own card, so a negotiated route rate holds on the invoice lane it was negotiated for.
Apple Intelligence and Siri-enabled business calling, decoded — the verification workflow behind Siri-attributed calls, the iOS-side call-summary UX, and pass-through of Rich Call Data through the Verified-Caller surface
Apple's extended Apple Intelligence voice stack — a Siri-enabled business-communications layer with business-messaging hooks and a call-manager surface — is now documented for business calling. What Apple has published, what a business should prepare, and how the Orbit Verified-Caller surface passes the branding metadata through with no claim on Apple's backend.
The CPaaS ROI ledger — the vendor-consolidation business case, written as math: the five factors to price, the tenant-owned controls that run them, and where consolidation still fails
The orthodox math for consolidating per-channel and per-vendor communications bills onto one gateway — the hidden ledger lines a multi-vendor PaaS actually charges (integration capex, reconciliation, five-bill drift), the factors to price (cost-center attribution, anomaly detection, per-channel throughput, per-seat UCaaS/CCaaS alternatives), the tenant-owned controls Devotel Orbit ships to run the ledger, and the cases where consolidation still doesn't pay.
RCS per-message pricing, decoded — what the late-2025 verified-agent billing shift means for your per-message bill
Google Jibe and the GSMA-tier carriers activated per-message RCS billing on the verified-agent path in late 2025, making RCS cost like SMS premium on delivered traffic. This explainer covers what changed, what template mix does to the bill, and which tenant-owned controls decide what you actually pay.
Toll-free vs 10DLC vs short code — the US SMS number-type chooser: one decision table by volume, deliverability class, and vertical regulation, plus each type's verification flow
One decision table for the three US A2P SMS sender categories — toll-free (TFN) for one-to-many high-volume messaging, 10DLC for local two-way business traffic, and short code for burst and emergency throughput — with each type's verification flow, the tenant-owned controls in Devotel Orbit, and the migration path between types.
SMS OTP autofill on iOS and Android vs carrier possession — the verification chooser guide: what the autofill layer narrows, where it lands in the funnel, and when SNA eliminates the SMS
iOS one-time-code autofill and Android SMS Retriever vs carrier possession checks (SNA) — how the platform-side autofill layer works, where it sits in the verification funnel, and how to choose between SMS OTP autofill and SNA on the Devotel Orbit Verify API.
When your CPaaS vendor is acquired or EOL'd — the buyer contingency playbook: contractable runbook, month-over-month exit signals, the portability hedge checklist, and the tenant-owned controls that cut the blast radius
A buyer-ship contingency playbook for the moment a CPaaS or UCaaS vendor is acquired, merged, or sunset — what to demand from a vendor's runbook before the announcement, which vendor behaviours forecast the move (pricing uplifts, region sunsets), the hedge checklist that makes a port survivable (number portability, contact-profile export, an S3-delivered ledger, BYOC sip chassis, BYOK), and the tenant-owned controls Devotel Orbit ships today that cut the blast radius of a vendor exit.
iOS 26 call screening and Live Voicemail, decoded — device-side answer-intercept, the answer-rate correction, and branching on the ios_call_screening / ios_live_voicemail AMD verdicts
Apple's call-screening agent and on-device Live Voicemail move a growing share of outbound answers into a machine-handled lane before the phone rings. Here is what the two features do at the behavior layer, what they do to answer-rate metrics, and how the ios_call_screening / ios_live_voicemail AMD verdicts let you branch on them.
Best call-recording and voice-analytics platforms in 2026 — QM suites vs conversation-intelligence specialists vs programmable platforms, scored on capture point, custody, and export shape
Eight call-recording and voice-analytics vendors — NICE CXone, Genesys, Talkdesk, Twilio, Gong, CallRail, Observe.AI, and Orbit — evaluated on where the artifact is captured, whether QC is automatic, and whether the recordings resolve onto a customer profile with programmable reads.
Compliance health: read your 0–100 score before carriers throttle it — the four carrier-visible signals and the alert-cadence playbook
Your organization, every sending number, and every campaign gets a 0–100 score built from the four signals carriers act on — consent coverage, opt-out velocity, STOP-reply rate, and carrier rejections. The surface is read-only; the score tells you who is about to get throttled, and what to do with it stays your call.
When a regulator fine lands — the four-step tenant response playbook mapped to consent-proof, GDPR-evidence, opt-out-scope, and posture-review controls
FCC robocall actions, ICO PECR penalties, and EU regulator complaints all end at the same desk — the tenant's. This playbook walks the four steps a CPaaS tenant runs when a fine lands (complaint intake, evidence preservation, litigation hold, and post-fine posture update) and maps each step to the tenant-owned Devotel Orbit control that makes it survivable.
The compliance-bundles hub — HIPAA, fintech, e-commerce, and PCI quadrants sequenced: what each activation provisions, the walkthrough it deep-links, and the go-live checklist back to the docs
A buyer-side sequencing of Devotel Orbit's four vertical compliance bundles — healthcare HIPAA, fintech KYC, e-commerce, and PCI payments — naming what each activation provisions, the walkthrough it deep-links, the tenant-owned controls for that vertical, and the go-live checklist back to the docs pillar pages, so a compliance review runs start to finish from one page.
The tenant-owned alerting ladder — usage budgets, usage alert rules, the anomaly ledger, route quality, and KPI alerts composed into a three-tier operator guide
Compose Devotel Orbit's shipped alert surfaces — per-API-key budgets, usage alert rules, the anomaly ledger, route-quality thresholds, KPI alerts on CSAT/NPS/CES, and scheduled digests — into a three-tier alerting ladder (cost, volume, quality), with a runbook entry for what to do when a usage alert fires.
Silent Network Authentication, decoded — the GSMA Open Gateway / CAMARA possession proof vs SMS OTP vs passkeys, with the fail-closed degradation model
Silent Network Authentication (SNA) explained for verification buyers — the GSMA Open Gateway / CAMARA Number Verification flow, how a device-bound network token completes verification without an OTP, how it compares to SMS OTP and passkeys, and how to wire it on the Orbit by Devotel Verify API with shipped fail-closed behavior.
SMS aggregator path disclosure, decoded — what aggregators publish about gray routes and the GDPR Article 6 basis for sharing path data
Path disclosure is the one honest answer an SMS aggregator can give about where your traffic terminates. This explainer reads what aggregators publish about gray routes and SIM-pumping risk, maps the EU GDPR Article 6 basis for sharing per-route path data, and shows how a tenant reads a route-quality report to test the disclosure.
Turkey messaging rules, decoded — KVKK scope vs GDPR, BTK's reserved sender prefixes (GOV/BANK/SGK/MEB), the restricted_prefix strict-mode gate, sender-ID registration, the TR opt-out vocabulary (DUR/İPTAL/ÇIKIŞ), and residency pinning for TR voice records
A deep-dive on launching SMS into Turkey on Devotel Orbit: KVKK and the GDPR-tricking scope question (controller obligations, foreign representative, cross-border transfer), BTK's reserved sender prefixes (GOV, BANK, SGK, MEB), strict sender-ID mode's restricted_prefix code, sender registration with KYC documents, Turkish opt-out vocabulary (DUR, İPTAL, ÇIKIŞ), and the data-residency posture for TR records.
Provisioning-capable country numbers — the per-country capability inventory behind the country-capabilities endpoint, announced GA
Devotel Orbit's per-country capability inventory — provisioning-ready bucket counts by line type via the country-capabilities endpoint — is generally available on every workspace, announced here on the record. This post consolidates the capability rollout and names the verification destination.
Closed-loop knowledge mining — resolved conversations drafted into review-queued help articles, human-approved before they ground AI agents
Closed-loop knowledge mining on Devotel Orbit — resolved conversations ranked by contact reason, recurring article-shaped reasons drafted automatically into a review queue, and human-approved publishing into the knowledge base that grounds AI agents
SMPP certification checklist — the buyer-side battery (throughput + TPS, throttling, hard failover, encoding/UDH mapping) run sandbox-first, then the tenant-owned BYO plan it feeds
Before high-volume SMS moves to an SMPP bind, buyers run a certification battery: baseline throughput against the negotiated window, throttling response under saturating TPS, hard failover with sequence-safe resubmission, and encoding plus UDH mapping on the languages they actually send. This checklist gives buyers the four test classes, a sandbox-first order of operations, and a BYO-SMPP plan where the tenant owns every control.
Multi-region SIP and failover design — the four failure domains (trunk chain, route fallback, webhook backup URL, edge proximity) and the regional launch checklist
Enterprise voice continuity comes from four layers that each fail independently — trunk failover chains, per-number route fallbacks, webhook fallback URLs, and media-edge proximity. This guide maps each failure domain of a SIP deployment to the control Orbit ships for it, with a design checklist for multi-region rollouts.
This week in Orbit — October 22, 2026: OpenAI's 2026 deprecation cycle decoded, the VoLTE/VoNR + IMS retirement explainer, eIDAS 2.0 mapped to SMS verification, and the AI-voice compliance audit consolidated to one deep link
This week in Orbit by Devotel: the time-bound announcement series runs again — OpenAI's 2026 deprecation cycle decoded, the VoLTE/VoNR and IMS-retirement wave explained, eIDAS 2.0 mapped to SMS verification, and the AI-voice compliance audit consolidated to one deep link.
Number masking explainer — two-party proxy sessions from Numbers → Masking, per-session TTL + expiry, the recording-consent boundary, and how it differs from shared lines
Number masking on Devotel Orbit — per-session proxy numbers for ride-hailing, delivery, and marketplace buyer-seller contact, configured from the Numbers dashboard
Number lifecycle beyond the port — CNAM branding, lookup, masking, E911, regulatory preview, and per-number health as a buyer's audit checklist
Number operations on Devotel Orbit — CNAM registration, lookup and enrichment, number masking, E911 emergency-address registration, regulatory preview, and per-number health monitoring across the Numbers dashboard
SMPP vs REST for high-volume SMS — a practical choice framework: decision tree, both paths anchored end to end, a worked campaign with MPS numbers, and the bind-in-front/REST-behind hybrid
High-volume SMS senders must eventually decide whether traffic enters the platform as an SMPP bind or as REST API calls with webhooks. Both doors reach the same routing and receipts on Orbit — so the choice is about throughput, latency, and how much session machinery you want to operate. This framework gives you a decision tree, both paths with real anchors, a worked campaign with MPS numbers, a hybrid migration pattern, and a trade-off table.
Tracking pools and dynamic number insertion (DNI) explainer — DNI vs DNC vs DNO vs TRACED, sticky vs fixed session binding, attribution reads, and IVR/AI-agent routing answered
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.
E911 in practice — the four-state address-registration walkthrough (registered → valid → dispatchable), the carrier-vs-tenant obligation split, and the stated U.S. scope
A hands-on walkthrough of E911 address registration on Devotel Orbit — the four-state lifecycle from registered to dispatchable, which duties sit with the carrier and which stay on your side of the ledger, worked API and dashboard examples, and the U.S. boundary of the feature.
The compliance-audit deep-link — AI voice/e911/attestation consolidated: EU AI Act checklist, RMD lifecycle, STIR/SHAKEN + recording consent, E911 address, resolved to shipped tenant-owned controls
A buyer-side consolidation of the four voice-compliance classes Devotel Orbit ships as tenant-owned controls — EU AI Act Article 50 disclosure, the RMD filing lifecycle, STIR/SHAKEN attestation with call-recording consent, and E911 emergency-address registration — resolved to the shipped endpoints and docs so a legal-team review can run start to finish from one page.
On-call + escalation, explained — PagerDuty-style primitives as four compute endpoints: rotation resolve, policy planning, and the incident lifecycle over your existing channels
Devotel Orbit's On-Call API packs the primitives incident tooling is built on — rotation resolve, escalation-policy planning, and the incident lifecycle — into four compute endpoints over channels you already run. This explainer covers what each primitive is, how the pure-compute shape works, and where the tenant-owned controls sit.
This week in Orbit — September 24, 2026: RSS feeds for the blog and changelog, Meta's per-user WhatsApp cap decoded, and vertical compliance bundles
This week in Orbit by Devotel: the blog and changelog now serve coded RSS feeds, Meta's per-user WhatsApp marketing frequency cap decoded, one-click vertical compliance bundles announced, new head-to-head compares against Bird (MessageBird) and Klaviyo, and setup tips in the ToS channel picker.
QR codes for SMS and WhatsApp — generate sms: and prefilled wa.me deep links server-side: safety scheme floor, sizing bounds, and the print-campaign use cases
Generate PNG QR codes over the API — sms: deep links, prefilled wa.me WhatsApp links, and arbitrary URLs — server-side, 50 to 1024 pixels, with the payload never leaving the platform.
OpenAI's deprecation cycle, decoded — Assistants/Evals/Agent Builder surface sunsets vs legacy-model retirements vs fine-tuning restrictions, and the two-bullet migration take
OpenAI's public deprecation schedule is retiring whole API surfaces in 2026 — the Assistants API, the Evals platform, and Agent Builder — plus entire legacy model families — while Chat Completions itself is explicitly not deprecated. What actually shuts down, which integrations are hit, and how an AI-first agent platform reads the timeline.
VoLTE, VoNR, and the IMS-retirement umbrella — the mobile-side counterpart to the PSTN switch-off, mapped to shipped attestation and programmable-voice controls
Mobile operators are shutting down 2G/3G and moving voice onto VoLTE and VoNR, with the IMS core that carried both now being trimmed back itself. This explainer covers the sunset track, how it runs in parallel with the PSTN switch-off wave, and the tenant-owned posture it demands of every fixed-line voice estate.
Pattern usage analysis, explained — cluster repeated message bodies deterministically and hunt dead templates, worked end to end with a library hit to archive
How deterministic pattern usage analysis clusters repeated message bodies in Devotel Orbit — what clustering surfaces, a worked dead-template hunt, and the limits of the analysis.
eIDAS 2.0, decoded — where digital-identity regulation meets SMS verification: Lookup + SIM-swap pre-send, the Verify loop, the boundary with KYC document collection, and the tenant-owned control statement
The EU's eIDAS 2.0 regulation expands digital-identity trust services, and CPaaS buyers are asking what it means for their OTP and verification stack. Here is what the regulation says, where identity-proofing meets SMS verification on Devotel Orbit, why it is not the same thing as KYC, and which of the controls are tenant-owned.
Zapier vs n8n vs Make (with Workato) — the cross-shop pairwise head-to-head scored against Orbit workflows on one matrix
Buyers shortlisting a workflow-automation hub query the pairwise matchups: Zapier vs n8n, Zapier vs Make, Make vs Workato. This head-to-head scores each brand's strengths and limitations on one matrix, then shows where Devotel Orbit's platform workflows and journeys replace the hub entirely.
UCaaS operations guide — shared lines, call park, ring groups, hot-desking, with the vocabulary fix (hunt group = ring group) and the SMB buyer checklist
The UCaaS operations surfaces on Devotel Orbit — shared lines, call park, ring groups, paging groups, and hot-desking — configured from the Voice dashboard
Q1 2027 forward look — the next quarter's operator agenda, grounded in the shipped record
Q4 2026 review and the forward look at Q1 2027 — What shipped during Q4, including WhatsApp Flows validation, localized video waiting rooms, PII-vault batch grouping, and multi-WABA deep links, plus the operator agenda for the next quarter, grounded only in what is live today.
UK PECR/ePrivacy, decoded — the opt-in layer beside UK GDPR: soft opt-in scope, the omnichannel consent matrix beside TCPA/CAN-SPAM/CASL, and the tenant-owned consent baseline
The UK's Privacy and Electronic Communications Regulations sit beside UK GDPR and ask a separate question about marketing SMS, email, calls, and push — was the message itself something you could send before consent. This explainer covers where PECR fits in the omnichannel consent matrix beside TCPA, CAN-SPAM, and CASL, and the tenant-owned consent baseline a UK program configures.
Do-Not-Originate (DNO) explainer — the origin-side caller-ID guard: what DNO filters vs DNC, the TRACED-Act backdrop, prefix matching, and the tenant-owned extend/replace/subtract override
Do-Not-Originate registries list numbers meant to receive calls, never place them — inbound hotlines, government lines, support queues. This explainer covers what DNO is, the legal backdrop behind it, where screening happens in the call path, why an outbound caller ID that sits on a registry gets blocked, and the tenant-owned guard Devotel Orbit runs at dial time.
Orbit vs SimpleTexting — the SMB marketing-texting app against the AI-first omnichannel platform
Orbit vs SimpleTexting: what the lightweight self-serve SMS-marketing tool publishes, an honest parity table backed by a public head-to-head, where the simpler tool still wins, and how a 10DLC-marketing move onto the omnichannel platform works.
Orbit vs Grasshopper — the per-account virtual-PBX front door against the AI-first omnichannel platform
Grasshopper's per-account virtual PBX — published numbers whose extensions route calls to team devices — against Devotel Orbit's AI-first omnichannel platform, with the /compare/grasshopper matrix and an FAQ.
Orbit vs OpenPhone — the per-line SMB phone app (Quo) against the AI-first omnichannel platform
OpenPhone (rebranded Quo) per-line SMB phone app — shared team inbox for calls, texts, and voicemail — against Devotel Orbit's AI-first omnichannel platform, with the /compare/openphone matrix and an FAQ that names the migration runbook.
OpenPhone vs Grasshopper head-to-head — the SMB phone-system cross-shop scored on porting, IVR/menus, team inbox, omnichannel breadth, and migration friction, with the Orbit frame-in clearly labeled
The OpenPhone vs Grasshopper head-to-head a small-business phone-number buyer actually needs: phone-number app vs virtual PBX, scored on number porting, IVR and menus, team inbox, omnichannel breadth, and migration friction — with an honest-fit verdict for each and Devotel Orbit's frame-in clearly labeled.
Talkdesk vs Five9 head-to-head — the first CCaaS-incumbent cross-shop, scored on omnichannel routing, WEM, WFO, and the AI layer, with the Orbit frame-in clearly labeled
Talkdesk and Five9 both ship enterprise cloud contact centers — omnichannel routing, workforce engagement, and their own AI agent layers — but differ on the AI architecture, the commercial posture, and how much stack sits off the suite. A sourced side-by-side for SSOT shortlists, with the Devotel Orbit frame-in at the end.
Cost centers, GA — allocate spend per ledger, export revenue-recognition schedules, reconcile CDRs, and guard with tenant-owned caps
Devotel Orbit's Billing dashboard now carries cost-center chargeback ledgers, straight-line revenue-recognition schedules, CDR reconciliation feeds, and finance-grade spend guards. This walkthrough shows the full allocation loop — from tagging sends with metadata.cost_center to the month-end close.
First-IVR setup walkthrough — greetings, menus, fallback logic, and the measurement layer (post-call CSAT/NPS digit capture, sentiment, ring-all handling) in one guided post
A guided first-IVR runbook for inbound callers — what the parts of an IVR actually are (greeting, menu, fallback logic), how to migrate off a legacy tree step by step, what Orbit layers on top of the bare menu (post-call CSAT/NPS digit capture, sentiment analytics, horizontal ring-all call handling), and a worked three-level route you can copy. Written for ops and engineering standing up their first inbound tree.
Flow builder vs journey builder — Twilio Studio vs Braze Canvas vs Orbit's two surfaces, the taxonomy explainer that disambiguates the two automation shapes
Twilio Studio is a flow builder, Braze Canvas is a journey builder, and Devotel Orbit ships both — inbound conversations route as flows and outbound campaigns step as journeys. Define the two shapes, compare them row by row, and choose the right builder for the work.
The A2A protocol, explained — Agent Cards, JSON-RPC task envelopes, MCP vs federation vs squads, and what Orbit's shipped A2A surface actually exposes
Agent-to-agent (A2A) is the open protocol for letting one AI agent delegate a task to another, with discovery via a public Agent Card and a task lifecycle over JSON-RPC. This explainer decodes what A2A actually specifies, how it complements the Model Context Protocol (MCP), and how Devotel Orbit's multi-agent squads sit on top of it.
Querying your Orbit data with the read-only GraphQL API — the /developer/graphql Explorer, auth and tenant scoping, the schema, and twelve paste-ready query patterns
A practical guide to Orbit's GraphQL Explorer at /developer/graphql — how the endpoint, auth, and schema work, and twelve ready-to-run query patterns for contacts, conversations, messages, and segments.
The smishing-prevention playbook — register the sender identities you own, protect your own drafts, watch hostile candidates off your watchlist, file takedowns with a prepared evidence pack
Move defense left: register the sender identities you own (10DLC, alphanumeric sender IDs, RCS verified senders), protect your own drafts with a compose-time URL-reputation linter, watch hostile candidates off a tenant-owned watchlist, and file takedowns with a filing-ready evidence pack. The four-layer playbook, mapped to shipped Orbit controls.
This week in Orbit — September 17, 2026: PSTN switch-off explainer, agent squads, and three new compares
This week in Orbit by Devotel: a plain-English explainer for the EU/UK PSTN switch-off, agent squads for multi-agent orchestration, a Click-to-WhatsApp ads entry point, head-to-head compares against Amazon SNS, Zapier, and n8n, and the September release-notes recap.
CPaaS API security in 2026 — key scoping, webhook forgery, and account takeover at the provider layer, each mapped to a tenant-owned control, with the buyer checklist
SMS pumping made CPaaS fraud visible, but the quieter 2026 discussion is about the API surface itself — leaked keys bought by CAPTCHA farms, forged webhook payloads injecting fraud events, and dashboard takeovers that mint attacker-owned credentials. This explainer walks the three shapes, the shipped tenant-owned controls that answer them, and the checklist to run in a CPaaS deal.
How to register for 10DLC — Brand and Campaign step-by-step through the TCR
The affirmative 10DLC registration walkthrough — Brand registration fields TCR vets (legal entity, EIN, address, vertical), campaign use-case selection with approved sample messages, vetting score and throughput tiers, the console runbook on Devotel Orbit, and the rejection patterns that trip first submissions.
Orbit vs EZ Texting — SMS-marketing app vs the AI-first omnichannel platform
Orbit vs EZ Texting: what the SMS-marketing app publishes, an honest parity table, when the simpler tool still wins, and where Orbit's full omnichannel stack earns its scope.
Recovering from a failed or partial migration — the four failure shapes, the retry / roll-back / escalate paths off Settings → Migrations, and the pre-flight that makes a rerun stick
A halted platform migration on Devotel Orbit is persistent — the job id, failure reason, counters, and conflict list survive, and recovery follows one of three paths. Which path to take (rerun, roll back, or escalate), the four failure shapes that stall most imports, and the pre-flight checks that make the retry stick.
Gmail and Yahoo bulk-sender requirements, decoded — the 5,000/day threshold, SPF/DKIM/DMARC as one acceptance gate, RFC 8058 one-click unsubscribe, and the 0.3% complaint ceiling, each mapped to its Orbit surface
Gmail and Yahoo's bulk-sender rules bind any tenant crossing 5,000 messages a day to Gmail — authentication (SPF, DKIM, DMARC), RFC 8058 one-click unsubscribe, and a spam-rate ceiling enforced in Postmaster Tools. This explainer decodes each requirement, maps it to the Orbit surface that enforces it, and draws the marketing-vs-transactional line both mailboxes already police.
Consent-proof-first messaging — the consent-as-asset explainer, grounded on tenant-owned audience/consent + opt-outs and compliance documents/binder surfaces
How to run messaging consent so the proof arrives before the campaign — the fields a consent record must carry, where Orbit surfaces them, what to hand counsel, and a quarterly review that keeps the ledger true.
Third quarterly review — Q4 opened: shipped, tuned, next
The third Orbit quarterly review — Q4 2026, opened, covering the quarter's shipped changes so far, the preview and mid-check that opened it, the peak-season preparation running across Q3/Q4, and what "shipped, tuned, next" means before the quarter's monthlies close it.
AI agent orchestration patterns, indexed — the orchestration definition, four full pattern subsections deep-linking the published walkthroughs, and a decision table
The four orchestration patterns a Devotel Orbit buyer actually chooses between — one canonical agent, a classifier-and-specialists squad, a champion-challenger rollout, and role-play rehearsal — indexed against the shipped /agents surfaces, with a decision rule and a worked scenario for each.
OpenPhone migration runbook — export prerequisites, numbers ported in waves, call flows rebuilt on the visual journey builder, snippets re-authored as content templates, contacts CSV-imported, with an honest-fit section on where OpenPhone still wins
An OpenPhone-specific migration runbook for small-business phone-system buyers. Export your numbers and message history, then move in order — numbers ported first, call flows rebuilt on the journey builder, reusable message templates re-authored on the content-templates surface, and contacts carried over via the CSV import wizard. OpenPhone's fit is asserted honestly at the end.
Prepaid credits top-up and auto-reload — self-serve wallet funding on /billing plus a tenant-owned threshold config at /billing/payment
Devotel Orbit's prepaid credit wallet now has two self-serve controls live on every workspace — a top-up dialog on the Billing page and an auto-reload threshold that recharges your balance when it falls below a level you set. This post walks through what shipped, where to find it, and how to use it.
The Twilio assembly tax, quantified — the four-bill problem walked through with worked 50k-message arithmetic
The four-bill problem (Programmable Voice + Messaging + SendGrid + Segment) asserted on /compare/twilio, walked through with arithmetic: a worked 50,000-message-month scenario priced on published rates, the hidden line items that ride on top, a footnoted TCO table, and an honest map of when the assembled Twilio stack still wins.
Twilio vs MessageBird (Bird) — the two full-stack CPaaS incumbents compared vendor-on-vendor, with the Orbit frame-in clearly labeled
Stack-dismantling series: Twilio and Bird both cover voice, SMS, WhatsApp, RCS, and email — but they differ on what is bundled, what is billed per product, and which channels each ships first-class. A sourced side-by-side for teams shortlisting both.
Mailgun vs Postmark vs SendGrid — the email-API tri-corner on deliverability posture, marketing bundle, and pricing tier
Stack-dismantling series: Mailgun, Postmark, and SendGrid all ship transactional email APIs — but they differ on deliverability posture, marketing bundle, and pricing tier. A sourced three-corner comparison for teams shortlisting an email API.
Blog and changelog now subscribe-able by RSS — coded feeds at /blog.rss and /changelog.rss, one item per post and per entry
Two coded RSS feeds now serve the whole marketing blog and the product changelog — one item per post and per entry, no account needed. Subscribe at /blog.rss or /changelog.rss.
Orbit vs Klaviyo — the lifecycle-marketing suite head-to-head against the omnichannel platform on one pay-as-you-go bill
A source-based comparison of Klaviyo's Email/SMS/push lifecycle suite with per-active-profile billing against Devotel Orbit's omnichannel marketing surface on one pay-as-you-go bill — evaluation criteria, honest cells from /compare/klaviyo, pricing math on two audience sizes, a five-step dry-run migration path, and where Klaviyo still wins.
WhatsApp per-user marketing template frequency cap — Meta's per-recipient marketing ceiling, decoded
Meta caps how many marketing template messages one WhatsApp user will receive from one business in a rolling window — per-recipient, not per-account. This explainer covers the cap mechanics, what stays uncapped, and the tenant-owned controls that surface cap risk before Meta applies it.
Vertical compliance bundles — one-click HIPAA, fintech-KYC, e-commerce, and PCI packs: what an activation provisions and the go-live checklist it returns
The Devotel Orbit settings catalog ships four vertical compliance bundles — healthcare, fintech, e-commerce, and payments. One activation provisions a draft compliance profile, draft campaigns, a vertical-tuned AI agent, and a double-opt-in flow, then hands you the go-live checklist. Nothing sends until you clear it.
Custom guardrail DSL: tenant-authored literal/regex rules on safety_config.custom_guardrail_rules with block, redact, or warn actions, announced
The Devotel Orbit safety stack now closes the tenant-specific gap the fixed scanners cannot express. Author literal `contains` or regex rules on `safety_config.custom_guardrail_rules` with block, redact, or warn actions, evaluated deterministically on every agent turn and shipped today.
FCC one-to-one consent rule, vacated — what outbound teams must still capture: the tenant-owned consent-record design
The FCC adopted a one-to-one consent rule for comparison-shopping lead generators in December 2023; the Eleventh Circuit vacated it in IMC v. FCC in January 2025, before it took effect. The base TCPA prior-express-written-consent requirement plus state mini-TCPAs still apply. This explainer covers the rule, the vacating, and the tenant-owned consent-record design that keeps lead source, timestamp, scope, and seller identity bound to every contact.
Q4 2026 preview — the operator agenda set at the quarter's start, and the four Preview items that resolved clean-on-chain: Messaging flow-edge polish, Compliance policy scan, Data consent-runtime resolution, Video waiting-room maturing rules (Q1 2027 continues, four-for-four)
Q3 closed with three monthly release-notes installments and a second quarterly review, so this post looks ahead at Q4 2026 and sets the operator agenda for it, grounded only in what shipped between August and October 2026.
Q4 mid-check — the holiday-peak checklist (holiday volume playbook, RCS launch, quiet-hours send windows), grounded in shipped releases
A mid-Q4 checkpoint that closes the loop on the quarter's preview, grounded only in the September–October shipped runbooks — the holiday-volume playbook, the RCS launch checklist, and the quiet-hours send-time guide — with nothing promised that is not live.
PSTN switch-off and copper retirement, decoded — the EU/UK regulatory calendar and the tenant-owned migration checklist
Regulators and incumbents across the EU and UK are retiring the public switched telephone network — copper access lines replaced by IP-only service on announced timelines. This explainer covers what the switch-off actually is, what copper retirement demands of a tenant's carrier and numbering posture, and the tenant-owned migration checklist for moving to SIP.
Orbit vs Bird — what the MessageBird rebrand means if you are choosing a communications platform today
Orbit vs Bird: the head-to-head for the stabilized brand — programmable channels vs a marketing-led omnichannel suite, two matrices, where Bird wins, migration framing, and an FAQ.
Orbit vs n8n — native integrations on the communication platform head-to-head against the self-hosted workflow graph
Orbit vs n8n: n8n's self-hosted workflow graph versus native integrations on the communication platform — honest cells from /compare/n8n, where self-hosting wins, what tenant-owned controls change, and the migration sketch for teams running n8n as messaging glue.
Orbit vs a lifecycle-marketing platform — the archetype head-to-head that scores both shapes on the benchmark rows
Evaluating lifecycle marketing is a choice between two archetypes — a standalone lifecycle vendor with a separate CDP beside it, or a messaging platform with a native CDP. This head-to-head scores both shapes on the same vendor-free rows the benchmark matrix uses, so you can pick the right one for your team.
Meta now gates WhatsApp Business senders on continuous quality signals — per-number ratings, per-template pauses, and dynamic marketing caps. This explainer covers what the telemetry measures, what a template pause actually is, and which tenant-owned controls keep you in the green.
Orbit vs Amazon SNS — omnichannel per-channel delivery head-to-head against a raw pub/sub topic
Orbit vs Amazon SNS: SNS is a raw pub/sub topic bounded to Amazon-centric consumption; Orbit delivers notifications through per-channel APIs (SMS, WhatsApp, RCS, voice, email) with tenant-owned consent controls. Honest cells from /compare/amazon-sns, where SNS genuinely wins, and how the pricing models compare.
Orbit vs Zapier — native integrations on the communication platform head-to-head against the workflow-automation hub
Orbit vs Zapier: Zapier's app directory versus native integrations on the communication platform — honest cells from /compare/zapier, where the directory wins, what tenant-owned controls change, and the migrate-or-compare routes that replace a Zap.
Workflow automation vs platform events — the long-form argument for the communication-platform shape over a raw event bus or an app directory
Automation on customer communications is a choice between two shapes — a raw event bus or an application directory versus events on the customer's own communication platform with consent gating. Here is what runs on each shape, where Zapier, n8n, and Amazon SNS remain the right answer, and how to evaluate the decision.
Klaviyo, Braze, and Iterable vs a native CDP — the named-family counterpart to the vendor-free archetype essay above
The Klaviyo, Braze, and Iterable family ships full lifecycle-marketing suites — and the data model underneath each is either a closed silo or a CDP rented from somewhere else. Here is what naming the vendors changes about the decision, where the family still wins, and how to migrate without a rebuild.
Lifecycle marketing vs native CDP — the long-form argument for choosing between a standalone lifecycle vendor and a messaging platform with a native CDP
Buying lifecycle marketing is a choice between two archetypes — a standalone lifecycle vendor with a CDP bolted on, or a messaging platform with a native CDP. Here is what "native" actually gets you, where the standalone shape still fits, and how to run the evaluation.
Klaviyo migration importer — the five-step wizard that moves lists, segments, templates, flows, and profiles, announced
Devotel Orbit ships a five-step import wizard that moves a Klaviyo account — lists, segments, templates, flows, and profiles — into Orbit with a dry-run preview before anything is written. What the wizard copies, how the conflict policy works, and the first-run checklist that gets you from API key to a monitorable migration job.
Orbit vs Podium — the bundled SMB reviews-and-texting suite against the AI-first omnichannel platform
Orbit vs Podium: what Podium's bundled reviews and texting suite actually sells, an honest parity table, migration notes on number ownership and review-widget decoupling, and the one buyer shape Podium still deserves.
Orbit vs Postmark — dedicated transactional email vs the AI-first omnichannel platform
Orbit vs Postmark: honest cells from /compare/postmark, what Postmark's transactional-only specialization buys, migration framing for a template-payload move, and when the incumbent still wins.
Orbit vs SignalWire — FreeSWITCH-rooted carrier APIs vs the AI-first platform
Orbit vs SignalWire: honest parity where the incumbent earns it (FreeSWITCH network, AI Agent Runtime, Video API), the scope trade-off, migration framing, and when the incumbent still wins.
Orbit vs ElevenLabs — speech-synthesis specialists vs the whole conversation
Orbit vs ElevenLabs Agents: the speech-synthesis lead is genuine, but the conversation spans SMS, WhatsApp, email, video, and a contact center — migration framing, matrix cells, and when the incumbent still wins.
Twilio Signal 2026, decoded — which /compare/twilio rows changed and which tenant-owned controls close the open gaps
An industry-news explainer on the Twilio Signal 2026 announcements as a CPaaS buyer — which comparison rows on /compare/twilio the conversation-layer push confirms or shifts, and which gaps Orbit's shipped tenant-owned controls (quiet hours, the opt-out ledger, the LLM spend governor) close with vendor re-evaluation framed openly. No vendor-shilling, attribution-only claims.
Integrations marketplace — the live Nango catalog in the dashboard plus the public /integrations hub, announced
The Devotel Orbit integrations marketplace pairs a live dashboard catalog — 100+ providers under Settings → Integrations — with a public hub at /integrations that documents every shipped connector in depth. Announcement of record: what the integration layer is, what shipped, and how security is handled.
CRM and commerce integrations — Salesforce, Zendesk, HubSpot, WooCommerce, and Slack activity sync, announced
Devotel Orbit's integration marketplace ships six launch integrations with one junction model — message events written back as CRM activities. This announcement explains the model, what each integration qualifies for today, and which one fits your team.
IVR post-call surveys — CSAT and NPS digit capture inside the call: the config surface, the disposition gates, the analytics
Post-call surveys play at the end of a voice call and capture a digit — 1–5 for CSAT, 0–10 for NPS — with no link and no follow-up message. This explainer covers the Devotel Orbit config surface, the disposition and sampling gates, where the answers land in analytics, and why the toggle ships off.
The FCC Robocall Mitigation Database, decoded — what a filing lifecycle looks like and how Orbit tracks the countdown and the origination guard
Every US voice service provider must file in the FCC's Robocall Mitigation Database before it originates calls, and terminating carriers are required to refuse unfiled providers. What 47 CFR § 64.6305 asks for, the filing lifecycle from draft to recertification, and how Devotel Orbit keeps the record, the countdown, and the opt-in origination guard while the filing itself stays with you.
n8n integration — a node pack for self-hosted workflow automation: trigger and action nodes against your tenant
Devotel Orbit now ships an n8n node pack (n8n-nodes-orbit) — an Orbit trigger node plus message-send and contact-create action nodes, authenticated with your API key — for teams that self-host or extend their workflow automation.
Click-to-WhatsApp ads entry point — a Meta campaign tap opens a WhatsApp conversation on your number, attributed to the ad
Click-to-WhatsApp ads turn a Meta campaign tap into a free-entry-point WhatsApp conversation. This explainer covers the end-to-end flow, what the meta_ads channel key in Devotel Orbit actually does today, the setup handoff, pricing, and the failure modes that reject campaigns.
Quiet-hours settings API — announced and GA: the send-window policy, now scriptable
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.
10DLC sanction sweep — why US campaigns are being deactivated, and the tenant-owned audit
US carriers have moved to enforcing 10DLC registration instead of tolerating drift — unregistered traffic suspended, dormant brands re-vetted, secondary vetting on the campaigns that drifted. This explainer covers what is being swept, why the enforcement window opened now, and the tenant-owned audit that keeps a campaign on the wire.
UCPD/UCDAS dark-pattern rules, decoded — the consent-UX patterns EU regulators prohibit
The EU's Unfair Commercial Practices Directive and its upcoming Digital-Accessibility-era successor get invoked under one label — "dark patterns" — and senders read it as a UI-criticism rulebook. This explainer separates the two instruments, names the manipulative-choice patterns they actually prohibit in consent and marketing flows, and keeps the controls where they belong: tenant-owned, because the flows are yours.
October 2026 release notes — three installments into the monthly cadence
The third monthly Orbit release-notes installment — what shipped through October 2026, why it matters for operators, and where to find each capability in the dashboard and the docs.
A2P SMS carrier-fee shifts, H2 2026 — the repricing checklist for senders
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.
EU UCPD dark-pattern sweeps — what they signal to A2P senders
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.
Personalization on the native CDP — computed traits, decided per visitor
Devotel Orbit's personalization engine turns the native CDP's computed traits into per-visitor decisions on your site and app. Here is what it does, how it differs from a Segment-style collection pipeline, who owns the consent posture, and a buyer checklist mapped to the shipped surfaces.
ITU-T PIN (remote-party determination) — the 60-day AI-voice study, decoded
The ITU-T's PIN (remote-party determination) work item asks how a network should establish whether the remote party on a voice call is a person or a machine — and how that determination should travel. Here is what the 60-day study window is deliberating, what platforms ship today, and which of the controls is yours to set rather than wait for.
Backfill quarterly review — Q1: the foundation quarter, January through March
The backfill installment of the quarterly review cadence — January through March 2026, when the foundation shipped, grouped by channel and anchored to dated changelog entries, with the quarterly convention and an FAQ.
Call-recording consent in 2026 — tenant-owned one/two-party controls
Call-recording consent is not one rule but fifty of them, and the 2026 posture has shifted — carriers and platforms now treat your consent configuration as part of the message-and-call policy you are accountable for. The one-party vs. two-party split, modelled as the two controls every CPaaS tenant owns (which calls record, and how callers are told), and how to set them in Devotel Orbit.
Second quarterly review — Q3 so far: July, August, and September to date
The second Orbit quarterly review — Q3 2026 so far, covering July, August, and September-to-date shipped work, grouped by channel (compliance, voice, messaging, data, video) plus AI agents and platform/billing. Every item is live and resolved to its availability label and public documentation.
First quarterly review — the third cadence slot, alongside weekly and monthly
The first Orbit quarterly review, deepened into a dated retrospective — April through June 2026 grouped by channel (AI voice, SMS, email, video) plus platform and billing, with a numbered ship list anchored to dated changelog entries, an honest what-we-learned reflection, and an FAQ.
Voice of Customer (VoC) — what CSAT, NPS, and CES measure as one platform discipline
What voice-of-customer means when you evaluate a CPaaS, why CSAT, NPS, and CES scores belong next to the channels that produced them, and how Devotel Orbit ships the whole loop — surveys, VoC analytics, quality scorecards, session replay, and loyalty — on one platform.
A2P SMS interconnect fees — what senders must know
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.
WhatsApp per-message pricing, decoded — what the July 2025 model shift means for your bill
Meta has moved WhatsApp Business Platform billing from per-conversation to per-message, while widening free windows from API entry points. This explainer covers what changed, what costs less now, and which tenant-owned controls decide what you actually pay.
STIR/SHAKEN attestation, decoded — tenant-owned A/B/C policy over your owned numbers (target, downgrade, inbound verification)
The attestation level your outbound calls carry is the single biggest caller-identity lever on US voice traffic. What A/B/C attestation (ATIS-1000074) asserts, why owning your numbers beats delegate certificates, and how to read your Orbit attestation posture.
September 2026 release notes — the monthly cadence continues
The second monthly Orbit release-notes installment — what shipped going into September 2026, why it matters, and where to find each capability in the dashboard and the docs. The monthly cadence continues.
How Devotel Orbit's announcement editorial works. Weekly `This week in Orbit` entries, monthly release notes, and a quarterly review, grouped into six topical lanes — AI agents, compliance reminders, integration updates, pricing and fee changes, channel expansion, and industry shifts — with cross-links back to onboarding and the canonical changelog.
The EU AI Act and your AI voice agent — the tenant-owned disclosure controls for Article 50 (voice intro, chat notice, content marking)
The EU AI Act's Article 50 transparency obligations have applied to AI voice agents and chatbots since August 2, 2026. What deployers of human-facing AI on communications platforms must do, and how Devotel Orbit's tenant-owned disclosure controls map to it.
Introducing Orby — the AI assistant built into the dashboard
Orby is the assistant embedded in every Orbit dashboard. It answers questions grounded in your workspace data and the Orbit documentation, looks up usage on demand, and proposes data-changing actions behind an explicit approval step. What it can do, how sessions and availability work, and three workflows to try first.
Agent squads — multi-agent orchestration behind one conversation: a classifier router and specialist agents, announced
How Devotel Orbit's agent squads compose a classifier and specialist agents behind one conversation, why specialization beats a single monolithic prompt, and what routing, memory, model presets, and squads each own.
One year of the native CDP — what launch and support taught us
Devotel Orbit's native customer data platform is a year old. A recap of what shipped in the lane, what the first customers actually broke, what support conversations turned into documentation, and where the CDP stands on the comparison matrices buyers check.
First weekly installment — the cadence starts here
This week in Orbit by Devotel: usage alert rules moved into the dashboard with a one-click spend-throttle preset, a new insight surface for usage and delivery anomalies, and voice agents gained backchannel cues plus a sensitive-words redaction list.
Voice data residency — EU/US region pinning for call media
Devotel Orbit now ships per-region voice data residency covering call recordings, voicemail, live media, and transcription — with tenant-owned region pinning and retention. What stays in-region, what you configure, and a worked EU deployment with recording residency.
SMS pumping and gray-route fraud — the consolidated operator explainer: both halves of the 2026 SMS-fraud class with tenant-owned controls
The 2026 SMS pumping and gray-route wave in plain terms — how artificial traffic inflation to premium numbers and unregistered-origin routes actually work, why regulators and carriers moved this year, and the tenant-owned controls (pre-send fraud checks, sender registration, frequency caps, suppression, conversion-anomaly reporting) that put the cost back on the attacker.
WhatsApp Business Calling API hits GA — what changes for business voice
Meta's WhatsApp Business Calling API reached general availability in July 2025, bringing user-initiated and business-initiated VoIP calls into the WhatsApp Business Platform. This analysis covers what shipped, why it retires the 'WhatsApp is text-only' objection on telephony shortlists, and how to choose between WhatsApp calling and PSTN voice.
First monthly release-notes installment — establishes the cadence
The first monthly Orbit release-notes installment — what shipped in August 2026, why it matters, and where to find each capability in the dashboard and the docs. Establishes the monthly release-notes cadence.
RCS launch checklist 2026 — announcement and operator's runbook: the five go-live elements, sequenced
The practical go-live playbook for RCS Business Messaging — agent registration, verified sender, templates, launch gates, cost model vs SMS and WhatsApp, and a market selection checklist for operators launching in 2026.
Why a native CDP changes launch and support engineering
A CPaaS with a built-in customer data platform collapses the two hardest parts of launch engineering and support — cross-system data sync and fragmented context — into one platform. Here is what "native CDP" actually means, what the bolt-on model costs, and how it changes the day-to-day work of shipping and supporting customer communications.
Recently migrated capabilities
Eleven-language SDK set
Node, Python, Go, Java, PHP, Ruby, C#, Swift, Kotlin/Android, Flutter, and React Native SDKs — one page per language with install, auth, and a first call.
Every announcement above either lists the Settings path in-product or links the docs guide for it — open the dashboard and the exact toggle, and you are done in one session.