Feature request: multi-brand sender support for OTP ("Verify email") emails

Summary

OTP emails sent by the "Verify email" step in Workflows do not respect brand configuration. They are always sent from a single workspace-wide sender — the first custom domain listed in Email settings (or a temporary Intercom address if no custom domain exists). We need the OTP sender address to follow the brand associated with the conversation or workflow.

Current behaviour

1. A customer starts a conversation with the non-default brand (Messenger and all other brand-aware emails correctly use support@custom_brand.com).
2. The workflow reaches an OTP / "Verify email" step.
3. The verification code arrives from support@default_brand.com — the workspace default brand — instead of support@custom_brand.com.

Confirmed by Intercom Support: multi-brand functionality is not supported for OTP emails; the whole workspace shares one OTP sender.

Expected behaviour

The OTP email should be sent from the sender address of the brand that owns the conversation / workflow — the same brand resolution already applied to other outbound email. At minimum, allow an explicit sender-email override per brand (or per workflow) for the "Verify email" step.

Why this matters to us

• Trust and conversion. We operate a multi-brand workspace where each brand is a separately branded, regulated legal entity. A verification code arriving from an unrelated company's domain reads as a phishing attempt. Users hesitate, abandon the verification step, or contact support to confirm the email is legitimate.
• Compliance and brand separation. As a financial-services provider we are required to keep client communications within the correct legal entity's brand. Sending identity-verification emails from a different entity's domain conflicts with that requirement.
• Deliverability. Codes sent from a domain the user has no relationship with are more likely to be filtered as spam, which turns a self-service step into a support ticket.
• Blocks rollout. OTP verification is part of our workflow design for non-default brands. Today we cannot enable it for those brands, which limits our ability to move these flows from Zendesk to Intercom.

Impact / scope

• Affects every non-default brand in the workspace.
• Affects all end users of those brands who reach an identity-verification step.

Workarounds considered

• Reorder Email settings so the desired brand is first — only shifts the problem to another brand; there is no correct single choice in a multi-brand workspace.
• Drop the OTP step for non-default brands — loses identity verification, which we need.
• Custom verification outside Intercom — requires a separate integration and breaks the workflow experience.

None of these is acceptable long-term; we are asking for native brand-aware OTP senders.

Questions for Intercom

1. Is multi-brand OTP sender support on the roadmap, and is there an indicative timeline?
2. Is a per-brand or per-workflow sender override feasible as an interim step?
3. Is there any beta or early-access programme we can join for this?