1. Regulatory focus
The immediate UK issue is not a new messaging-content prohibition; it is how Ofcom calculates regulatory fees and penalties under the Online Safety Act. Based on the May 2026 court reporting, Meta is challenging the use of qualifying worldwide revenue as the base, arguing that UK regulation should not sweep in group-wide global income. Ofcom’s position, however, is that if a regulated service is offered to UK users, the relevant worldwide revenue can be counted. For businesses operating direct messages, community chat, support messaging, or other user-to-user functions, the regulatory focus is expanding from takedown controls to group-level revenue mapping, service classification, and legal-entity accountability.
2. Business impact
This changes the economics of UK compliance for multinational communications providers. Many teams historically budgeted the UK around moderation operations, abuse handling, vendor review, and complaint workflows. If fees and penalties are linked to worldwide revenue, even a relatively small UK business line can trigger group-level reserve planning, board reporting, and internal cost-allocation disputes. The issue is especially acute for CPaaS and SaaS providers that bundle SMS, OTT support chat, in-app messaging, and account notifications: they must determine which modules qualify as regulated user-to-user services, which UK-linked revenues must be mapped upward, and whether private messaging or group features pull the product into a heavier compliance perimeter.
3. Operating recommendations
The most useful step now is not waiting for the litigation outcome, but building a UK service-boundary map. Break down every UK-facing communication feature into one-to-one messaging, group chat, customer support chat, notifications, comment replies, and file sharing; then mark whether each function includes user-generated content, forwarding, minor access, and complaint-handling loops. Next, align those functions to contracting entities, billing paths, and group revenue ownership so legal, finance, and product teams share one accountability map. If you run both SMS and OTT channels, create a UK-specific penalty scenario model now and compare exposure under a UK-revenue basis versus a worldwide-revenue basis.