Safely manage your Zendesk from the AI assistant you already use, via the Deltastring MCP. Beacon configuration platform →
← Back to news

Announcing brand filtering for Mobile SDKs

Zendesk

Zendesk has released brand filtering for its mobile SDKs on iOS and Android, enabling end users to view only conversations associated with their current brand context. The feature addresses a genuine operational friction point: organisations managing multiple brands through a single mobile application previously saw conversations from different brands mixed together in conversation lists, creating confusion about which brand was handling requests and degrading the user experience when customers switched between branded applications. Brand filtering operates automatically when multiple conversations are enabled and an account has two or more brands, filtering conversation lists, new conversations, updates, messages, real-time events, and push notifications all within the correct brand context. The rollout began in late September 2026 with no authentication model changes required.

The implications for multi-brand CX operations are straightforward but material. Teams managing complex brand portfolios through unified mobile infrastructure now have clearer conversation segmentation, reducing the cognitive load on end users and eliminating a source of support escalations caused by misdirected or miscontextualised conversations. For administrators, the feature ships enabled by default, meaning most organisations will benefit immediately without configuration overhead—though opt-out controls remain available in Admin Center. The question for larger enterprises is whether this addresses only the symptom or the underlying architecture: does brand filtering solve the user experience problem sufficiently, or does it mask the need for more fundamental separation between brand instances? For teams already operating sophisticated multi-brand strategies, this update represents incremental maturity in Zendesk's mobile offering rather than transformative capability, yet it removes a documented pain point that likely contributed to support ticket volume and user frustration in the field.