The third installment of the monthly convention that started in August and continued in September: one post per calendar month covering what actually shipped. Each section names the capability, why it matters, and where to find it in the dashboard and the docs. Nothing below is promised future work — every item is live today.
WhatsApp Flows validate cleanly on first upload (messaging pillar)
What shipped — The WhatsApp Flows editor (Channels → WhatsApp → Flows) now stamps every new flow with the WhatsApp Flows schema version Meta's servers accept — whether the flow was drafted with AI Generate, built in the visual editor, started from a template, or pasted as raw JSON. The version is pinned again at the upload step, so an old draft or a pasted fragment can no longer reintroduce a stale version.
Why it matters — Every flow created by any authoring route was previously failing Meta's validation on first upload with a "Flow JSON version is not supported" error, which blocked the whole create-to-publish path. The error is gone at the editor and caught again at upload, so the channel most commerce teams use for interactive journeys stays publishable on the first try.
Where to find it — Channels → WhatsApp → Flows in the dashboard.
Video waiting rooms: full at capacity, localized end to end (video pillar)
What shipped — Video rooms with a waiting room now handle the waiting queue properly at capacity. A host fill rule picks the new-entry or existing-entry lane deliberately (a lobby lists waiting guests instead of silently dropping the excess), and the whole flow — lobby lists, capacity labels, kick-ban control — is fully localized.
Why it matters — Waiting-room lane choice decides how join attempts behave once the room fills; before this, creating a room without a deliberate choice meant the wrong lane could silently drop late joiners. For clinics, consultancies, and support desks running branded video rooms, the waiting room is the guest's first impression — and it is now correct and readable in every supported language.
Where to find it — Create a video room from the dashboard; the hosting guide covers the lobby and capacity behavior (video conferences guide).
Conferences, hot-desking, and parked calls — voice guides (voice pillar)
What shipped — Three voice operations guides are now published end to end in the docs: conferences, hot-desking, and parked calls. Each covers the dashboard surface, the flows, and the API surface a tenant uses for call-group operations.
Why it matters — Call-group operations (parking a call into a team lobby, hot-desk a shared desk phone, or open a conference bridge) are routeable tenant-owned features, not provider exceptions — and until the guides existed, they were effectively discoverable only via the dashboard. The voice pillar documents tenant-owned controls only, and these guides close that gap.
Where to find it — Docs → Voice → Conferences, Hot-desking, Parked calls.
Multi-WABA deep links scope correctly (messaging pillar)
What shipped — On a workspace with more than one WhatsApp Business account connected, the WhatsApp Messages page picker now resolves a deep-link or bookmarked ?waba= selector by matching the account's WABA id as well as its phone-number id, so external and bookmarked links open the exact account instead of the workspace default.
Why it matters — Multi-WABA workspaces were previously silently resolving WABA-id-keyed links to the default account, which meant the conversations view and the template scope line showed the wrong account. Messaging teams that share scoped links (analytics, process flows, templates) get the right account on first render.
Where to find it — The WABA picker in Channels → WhatsApp → Messages.
Number compliance resubmission in place (numbers pillar, compliance)
What shipped — When a carrier review of a number-purchase compliance profile comes back declined with a request for corrected or extra documents, the resubmit now carries the same carrier review forward instead of silently starting a brand-new one.
Why it matters — Before this, resubmitting the profile orphaned the declined review and kept the number waiting on an approval that never arrived — a caught-up number held blocked. Regulated number purchase can proceed on a resubmit, which matters wherever a number's purchase depends on a compliance profile remaining in an in-flight carrier review.
Where to find it — Numbers → compliance profile for the number; resubmission uses the same form as the original submit.
---
The cadence continues
Three installments in, the convention holds: every capability above is shipped, every pillar is represented (messaging, video, voice, numbers-plus-compliance), and none of this is a roadmap promise. The per-release record stays at orbit.devotel.io/en/changelog between installments — an item that ships today rather than this week lands there first.
Next installment: November 2026.