The weekly installment aggregates what is already live and announced. This week's scope summary spans the WhatsApp, SMS, voice, RCS, and email capabilities in the current release window — what shipped since the October 1 briefing, and the tenant-owned controls each one hands you. Everything below resolves to a page you can open today; nothing here is promised future work.
What shipped this week
- WhatsApp Flows validate cleanly on first upload — the WhatsApp Flows editor (Channels → WhatsApp → Flows) now stamps every new flow with the schema version Meta's servers accept, whether the flow came from AI Generate, the visual editor, a template, or raw JSON. The version pins again at upload, so a stale draft can no longer reintroduce the "Flow JSON version is not supported" error that blocked the create-to-publish path.
- Multi-WABA deep links scope correctly — on a workspace with more than one WhatsApp Business account connected, a bookmarked or shared
?waba=link now resolves by WABA id as well as phone-number id, so the Messages page opens the exact account instead of the workspace default. Messaging teams sharing scoped links land on the right account on the first render. - Voice operations guides published end to end — three new docs guides — conferences, hot-desking, and parked calls — cover the dashboard surface, the flows, and the API for call-group operations. These are routeable tenant-owned features, documented as such.
- Email API reference in six languages — the email endpoint pages now ship worked request and response samples across all six published SDKs, so the send and status payloads read the same in the language your backend already runs.
- RCS brands console deepened — the Messages → RCS → Brands surface now documents per-state affordances across all six brand states: what you can edit, delete, resubmit, or link in each state, and what happens to linked agents when a brand is deleted.
Where this shows up
The anchors matching this week's scope are the standing capability surfaces:
- Features overview — the catalog of every live channel capability, where the GA entries above land.
- SMS API — the SMS capability page the messaging and quiet-hours work routes through.
- WhatsApp Business API guide — the long-form WhatsApp reference the Flows and multi-WABA fixes belong to.
Operator takeaways
Two actions are worth the minutes they take this week.
- Re-run any WhatsApp Flow that failed Meta validation. If a Flow was blocked at upload by a schema-version rejection, re-open it in the Flows editor and publish again — the version now stamps on save and pins again at upload.
- Bookmark your exact WABA in a multi-account workspace. Re-create the link from the Messages page with the
?waba=selector and share that; scoped links now resolve to the account you intended regardless of the workspace default.
Reading path
If you came here from a search and want the standing reference instead of the weekly slot, the fallback is the Orbit weekly briefing archive — every past installment, in order. Next week's installment covers only what ships between now and then; the anchors already live at the October release notes and the Q4 2026 forward look, both grounded in shipped releases.