This week in Orbit — previewing Q1 2027

Q4 2026 is the current quarter, and the Q4 quarterly review opened it the way the cadence dictates — shipped and tuned, then next. The Q4 preview laid out the operator agenda grounded in shipped work, and the Q4 mid-check closed that loop from shipped runbooks only. This post does the same for Q1 2027: the quarter is not yet under way, so the forward-looking parts stay labeled Preview with no dates attached, and the shipped parts trace to the dated record on the changelog.

What shipped

Each item below is live today and traces to a dated entry on the changelog — the same list the Q4 previews and reviews cited, because the current quarter is still open and the forward look carries it forward.

• WhatsApp Flows validate on first upload. Every new flow, whether drafted with AI Generate, built in the visual editor, started from a template, or pasted as raw JSON, is stamped with the schema version Meta's servers accept, and the version is pinned again at upload, so an old draft cannot reintroduce a stale one. The "Flow JSON version is not supported" error that blocked the create-to-publish path is gone.
• Quiet-hours policy is a settings API. The recipient-local send windows that gate outbound sends are readable and writable through workspace settings, with the effective window resolved per channel, so organizations managing compliance configuration in code no longer click through the dashboard.
• Video waiting rooms are localized end to end. Rooms running at capacity handle the waiting queue deliberately, and the full lobby flow — lists, capacity labels, kick-ban control — reads correctly in every supported language. Guests who hit a full meeting get an honest, translated message instead of a generic error.
• PII vault console groups a batch. Sealed envelopes from a reversible tokenize run group by identifier type, so a whole batch detokenizes in one call instead of one envelope at a time.
• Multi-WABA deep links resolve the right account. On a workspace with more than one WhatsApp Business account connected, a bookmarked or external link carrying a WABA id opens that exact account, and a link pointing at an account you do not have connected says so instead of showing a silent empty inbox.

What comes next (Preview)

This is the forward look, and it is Preview only. Preview means under active development, not generally available, with no dated promise attached. Anything here that ships will appear first on the changelog and then in the monthly installment for its month.

The four pillars keep their established directions as the working agenda for Q1 2027, which opens once Q4 2026 closes.

• Messaging: deepen the Flows authoring path now that every authoring route publishes cleanly. Likely direction: validation and versioning feedback closer to the editor, and a smoother path from draft to published flow.
• Compliance: more of the policy surface scriptable. The quiet-hours settings API is the first policy document exposed this way; the natural continuation is the same treatment for the adjacent compliance controls operators currently manage by hand.
• Data: the PII vault console's batch flow extends toward smoother sealed-envelope handling at scale.
• Video: waiting-room behavior keeps maturing around host control and localization coverage.

None of this is committed scope. The only commitments in this post are the shipped list above and the cadence itself; the rest of this section is where current shipped work points, written so a reader can hold us to the distinction.

Operator takeaways

Three controls are worth putting on the Q4-to-Q1 runway checklist now.

• Read your quiet-hours policy in code. GET /settings/compliance/quiet-hours returns the policy document and the effective window per channel; PATCH /settings/compliance/quiet-hours replaces it. The policy is tenant-owned and opt-in per channel, so audit it the same way you audit the rest of your configuration. The quiet hours guide covers the document shape.
• Cut your detokenize loops. In the PII vault console (Integrations → CDP → PII vault), copy a whole identifier-type group and paste it into the Detokenize pane to open a batch in one call. The PII vault guide covers the console flow.
• Rule on the signals that move an account. Insights → Usage alert rules runs the alert engine the API already exposed: threshold or anomaly rules on SMS delivery rate, outbound volume, and spend, with an in-app notification on breach and an evaluate-now button. The usage anomaly alert rules guide walks through a first rule.

Where to follow the quarter

The announcements hub collects the cadence in one place: monthly release notes, quarterly reviews, and the announcements that matter, each resolved to the docs. Between installments the per-release record stays on the changelog; anything that ships in Q1 2027 lands there first, then in the monthly installment, then in the quarterly review that closes the slot.