The weekly digest turns to the A2P industry lane. The last two installments covered Orbit's shipped work; this one reads what moved in the messaging industry over the past four weeks and what that movement asks of your program. Every claim resolves to a post or page already live on this site.
The October twist loop: OTT channels keep closing on SMS-only programs
The most structural shift in A2P this quarter is not a single carrier ruling: it is the steady twist in the loop between sender and recipient. In market after market, the app recipients actually open is no longer SMS, and the business-messaging offers moving that traffic are Viber business messages, Telegram bots, and the APAC template channels (LINE, Zalo, KakaoTalk, WeChat). A program that still treats SMS as the only reachable surface is losing opens in exactly the countries where the twist matters most. Our Beyond SMS and WhatsApp guide mapped this channel-by-channel when it published; the news frame this month is that markets which looked like exceptions then (Viber in the Balkans, LINE in Japan, Zalo in Vietnam) now read as the default posture and the two-tier models (one-way basic, two-way business) are becoming the competitive floor.
The WhatsApp quality-rating wave, one month in
Meta's quality gate tightened in September and the wave is still moving through everyone's template catalog. Per-number red/yellow/green ratings now move template limits inside the week, individual marketing templates get paused on feedback spikes, and per-recipient marketing caps make an over-sent message fail delivery instead of costing more. The WhatsApp quality-rating and template-pause wave explainer walks what Meta gating measures and what a pause actually is. Two adjacent shifts echo the same direction: the H2 2026 carrier-fee repricing checklist tracks the metering moves sitting under those gates, and the SMS-pumping fraud explainer states the fraud-side pressure regulators and carriers are absorbing at the same time. Read together, the industry spend moved in one direction: quality signals, template discipline, and fraud hygiene are now the same question.
What changed in A2P since Q3
Carrier-level interconnect and metering shifts kept compounding in the second half. Destination operators continued extending registration-side and per-message pass-through fees, and the major vendors split metering into per-message versus per-conversation shapes, so an identical subscriber reach now bills differently on different shelves. The A2P SMS interconnect fees explainer decomposes the three components of a per-message price (termination, inter-operator surcharges, provider margin) and the carrier-fee changes checklist runs the four-step repricing pass against a published per-destination rate card. The October state is not that fees vanished or moved in one direction: it is that the surcharge layer is now priced openly enough for a sender to test any line against a published operator number and treat the rest as margin.
What Orbit shipped in September
Our own September work is in the monthly release-notes installment and the weeklies that preceded this one (September 17, September 24). The durable changes for A2P teams: quiet-hours policy now has a settings API so per-channel recipient-local send windows can be reviewed and updated in code, the usage-anomaly alert rules page moved into the dashboard with a spend-throttle preset, and the blog and changelog both serve coded RSS feeds so this digest can reach a Slack bridge without polling. Each item lands with its dashboard route and docs page in the release notes.
QA checklist for the week
- Re-run the repricing pass from the carrier-fee changes checklist on your top five destinations against the published per-country rate card, and mark any "carrier surcharge" that does not map to a named operator fee.
- Check per-number quality-rating posture on your WABA: one red number pulls its own messaging limit, so isolate marketing and support traffic onto separate numbers before the next campaign.
- Audit your SMS-pumping posture: pre-send fraud checks on OTP, conversion-anomaly thresholds where OTP completion drops, and the channel mix (WhatsApp or Viber OTP in the markets those channels own).
- Open the usage-alert rules page, accept the spend-throttle preset, and subscribe to the blog RSS so next week's installment arrives in your reader.