Sender Identities

A channel normally sends everything from a single From address — its default sender. Sender identities let one channel hold multiple From addresses, each selectable per broadcast, sequence, and transactional email, without splitting your subscriber list.

The classic use case is separating mail types by subdomain:

• billing@send.yourdomain.com for transactional email (receipts, password resets)
• news@news.yourdomain.com for newsletters and campaigns

A complaint-prone campaign can then never drag down the deliverability of the invoices that must always arrive — each subdomain builds its own sending reputation.

Manage identities under Channel Settings → Sender Details → Identities. The first identity is created automatically from your channel’s sender details, and stays the default: anything that doesn’t explicitly pick an identity sends as the default.

Picking an identity per send

• Broadcasts — the Send As dropdown on the composer’s Settings tab.
• Sequences — the Send As section in the sequence’s settings.
• Transactional email — the sender_identity_id parameter on the Transactional Email API.

The dropdowns only appear once a channel has more than one identity.

Verification

Providers only deliver mail from addresses (or domains) they have verified, so every identity is tracked per email server:

• Verified — the provider confirmed this identity may send, either because its whole domain passes DKIM/SPF (via domain — this covers any future identity on the same domain) or because the address is individually verified (via sender — covers that address only).
• Provider says not verified — Broadcast asked and the provider said no. Complete the verification at the provider or re-run the setup wizard.
• Not checked yet — no check has run for this pairing. This is neutral, not a problem.
• Last check failed — the provider API could not be reached; the badge keeps showing the last known state.

Checks run automatically when an identity is added or its address changes, on a recurring schedule, and on demand via Check verification now, which walks every server and reports each one:

• Servers with API access are checked live.
• Servers whose API credentials are missing show connect API — verification can only be checked through the provider’s API, not through SMTP sending credentials.
• Servers with no verification API at all (plain SMTP relays) are listed as such; verify those addresses directly with your provider.

Deleting an identity reverts anything pinned to it back to the channel default. The default identity itself cannot be deleted — promote another identity first.