The monthly convention reaches its third installment. September's post covered the quiet-hours API and the stuck-call sweep fix; this October issue covers a broad set of shipped work — numbers inventory automation, channel onboarding depth, voice and video reliability improvements, and operator documentation that turns reference pages into complete workflows. Each section names the capability, why it matters, and where to find it. Nothing below is promised future work — every item is live today.
Numbers surface: backorder waitlist and low-stock replenishment
What shipped — The Numbers pillar now has two complete documentation surfaces that were previously gaps. The number backorder waitlist guide documents subscribing to a standing backorder for a country, area code, and number type that is out of stock at the provider, polling the same live inventory the buy flow uses, and placing the purchase when the pool reports enough depth. The low-stock replenishment concept page ties together the daily 04:30 UTC sweep, the number.inventory.low webhook and dashboard banner, and the replenishment plan and run endpoints, with a worked example that walks a 3-DID pool from depleted to restocked.
Why it matters — Sender pools and geo-matched dialers are only as resilient as their available number stock. Before these pages, the backorder process and replenishment loop were documented as separate references with no connecting narrative. An operator now has the full cycle: detect depletion, subscribe to a backorder, poll availability, and trigger a policy-backed purchase.
Where to find it — The backorder guide under Guides → Numbers; the replenishment concept under Concepts, cross-linked from the numbers overview and number lifecycle pages.
Channels: MMS, RCS, WhatsApp, Instagram, LINE, Telegram
What shipped — October brought depth across six messaging channels. The MMS retry and downgrade fix closes a gap where retrying a text-only MMS went back to the MMS provider and was rejected instead of downgrading to SMS; the opt-out check now runs against the channel the message actually leaves on. RCS agent registration and editing no longer fails with a generic "temporarily unavailable" error. WhatsApp gained two new guides: a turn-by-turn onboarding walkthrough and a Meta Cloud API migration parity map. The Instagram onboarding guide now carries SDK send samples in six languages plus webhook IGSID capture. LINE onboarding expanded from three to six languages with worked sticker and flex message samples. Telegram inbound messages are restored — a misconfigured callback address was silently dropping every inbound message. And the MMS channel page now shows every send in six languages with a worked group-MMS sequence.
Why it matters — Each of these fixes a concrete pain point. The MMS retry gap meant a retried message silently failed; the RCS registration bug blocked channel setup entirely; the Telegram outage meant bots appeared connected but received nothing. The onboarding guides close the gap between "the API reference exists" and "a developer can copy a working send in their language."
Where to find it — Each channel page under Channels, plus the onboarding guides under Guides → WhatsApp / Instagram / LINE.
Voice and Inbox: live-call failover, meeting layout, and device reliability
What shipped — Live transcription on Classic and outbound calls now fails over to a configured backup speech provider after the primary exhausts its reconnection attempts. Joining a meeting from Voice → Video Rooms → Meetings no longer opens a scrambled call window. The "Raise Hand" button now works on inbound and conference calls. Signing out of a mobile device actually stops incoming calls and alerts. Video rooms can stream live audio to your WebSocket server via a media fork in PCM format. A video media diagnostics guide covers pre-join preflight and in-call per-track stats. Participant name tags stay anchored inside the correct video tile.
Why it matters — Voice reliability gaps compound: a call that loses transcription, a meeting that renders wrong, a device that keeps ringing after sign-out — each erodes trust in the platform. These fixes close known failure modes, and the diagnostics guide gives operators the tools to debug what used to be a black box.
Where to find it — Voice → Video Rooms for meetings and media fork; the diagnostics guide under Guides → Video; the device push endpoints under the API reference.
Compliance and privacy: glossary depth and SIM swap coverage
What shipped — Five glossary entries — contact, cursor pagination, fallback channel, GSM-7, and panic button — now carry an Orbit-specific paragraph below the industry definition, connecting each term to the concrete API field or dashboard control. The glossary also gained a standalone SIM swap definition covering what a swap is, why a recent one is an account-takeover red flag, and how to check the signal.
Why it matters — A glossary entry that only defines the generic telecom term is not useful inside the platform. "Contact" now names the identity-resolution and segments surface; "GSM-7" now explains that a single non-GSM-7 character forces the whole body into UCS-2 and changes the billable segment count. SIM swap, previously only documented as the API, now has a standalone definition so the compliance surface is readable end to end.
Where to find it — Reference → Glossary in the docs.
Quiet-hours preview guidance
What shipped — The quiet-hours documentation now brings configuration and preview together: which setting applies to a send, how unresolved timezones behave, how to schedule the DST-safe next_allowed_at value, and when a recently changed organization setting is visible to preview requests.
Why it matters — Quiet hours are tenant-owned and opt-in per channel, and the policy is now API-configurable (shipped in September). The updated docs close the "I set it but when does it take effect" gap that operators hit on first configuration.
Where to find it — Under workspace settings in the dashboard, or via the API; the updated docs under Compliance → Quiet hours.
Subaccounts console guide
What shipped — A new guide for the Subaccounts console documents the full operator workflow: listing child organizations, suspending or reactivating a subaccount, recovering a pending setup, reading live credit balances per subaccount, and running a reseller invoice across every child.
Why it matters — The Subaccounts console was previously a dashboard surface with no docs page at all, so a reseller operator had to figure out the suspension confirmation copy, the role scope table, and the invoice run through trial and error. The guide closes that gap.
Where to find it — Settings → Subaccounts in the dashboard; the guide under Guides → Subaccounts.
Operator intelligence: sales conversation scoring and Verify coverage
What shipped — A new Sales Conversation Intelligence guide documents the per-call deal-risk score, rep talk-time share, competitor mentions against your own tracker list, next-step extraction, and the rollup API. The Verify page's "Top Countries by Volume" table now lists every country with verification activity instead of silently capping at five.
Why it matters — The sales conversation intelligence surface was live but undocumented beyond the raw endpoint reference; the guide explains what each score means and how to configure the workspace opt-in and competitor tracker. The Verify fix restores a complete country-level fraud picture that a five-row cap was hiding.
Where to find it — The sales intelligence guide under Guides; the Verify page under Verify → Fraud Indicators.
The canonical changelog
These sections are the editor's picks from the release history, not the whole of it. The full, per-release record stays at orbit.devotel.io/en/changelog — every section above traces back to an entry there, and anything that ships before the next monthly post lands there first.
What we're watching for November
October's work deepened the operator surface — numbers inventory automation, channel onboarding coverage, voice reliability fixes, and documentation that turns reference pages into workflows. The shape that is already visible for November includes deeper AI agent observability, multi-language SDK parity for the remaining stub packages, and the CDP catalog infrastructure that the streaming SDKs filter fix previewed. Nothing here is a commitment — it is just the direction the shipped work points toward.
Next installment: November 2026.