Skip to main content

Email Configuration

Settings → Email Configuration is where you manage the identities your workspace sends email from - the display name and address recipients see - plus the Reply-To and BCC addresses campaigns and journeys may use.

How this relates to providers and domains
  • Email Providers (Settings → Email Providers) = the sending infrastructure (SendGrid, SES, etc.).
  • Sending domains are attached and verified (SPF/DKIM) by your administrator; their health is shown read-only under Analytics → Deliverability.
  • Email Configuration (this page) = the sender identities and address lists you build on top of those verified domains.

Sender identities​

A sender identity is a display name + address on one of your verified sending domains (e.g. Acme News <[email protected]>).

To add one, click Add Configuration and set:

  • Display name - what recipients see (e.g. "Acme Support").
  • Local part - the part before the @ (e.g. news).
  • Domain - a locked dropdown of your workspace's SPF+DKIM-verified sending domains. You can only build senders on verified domains; if the list is empty, ask your administrator to attach one. Until a sending domain is attached and email can actually be sent, this page and the Customize From box on a campaign or journey say so - "No email can be sent yet" - instead of pointing at a default sender that does not exist; in a demo workspace email sends are simulated until then.
  • Reply-To (optional) - a default reply-to for this sender (see precedence below).
  • Default - the sender pre-selected when creating a campaign.

Sender identities are workspace-scoped - shared by everyone on the workspace, not personal.

Several senders can share one address with different display names (e.g. MODA <[email protected]> and MODA Sale <[email protected]>); campaigns and journeys keep the exact one you picked. The same address and name twice is refused - the address is compared ignoring letter case, the name ignoring case and surrounding spaces.

The default sender. A message that does not pick a sender goes out from the default. A workspace with a single sender uses it as the default even when it is not marked. With several senders and none marked default, messages that pick a sender still send, but one that picks none cannot - this page and Launch Review then say "Make one sender the default" instead of "No email can be sent yet".

Reply-To & BCC address lists​

Below the senders, you maintain the workspace's allowed Reply-To and BCC addresses. The per-message Reply-To and BCC pickers (in the campaign composer and journey email steps) are limited to these lists - to use an address it must be added here first.

  • Require a BCC address for all your email campaigns - when on, every email must pick a BCC (the "No BCC" option is removed in the composer). A separate workspace compliance BCC (Settings → Subscriptions) is always applied on top of any per-message BCC and de-duplicated, so an archive copy is never lost.

Per-message sender (campaigns & journeys)​

When composing an email, the Sender section lets you:

  • Pick a saved sender from the dropdown, or
  • Customize From - tick to override with a custom display name + local part on a verified domain (the domain stays locked).
  • Reply-To - choose a managed reply-to address, or "Exclude" (replies go to the From address).
  • BCC - choose a managed BCC address (or "No BCC", unless a BCC is required).

Per-variant in A/B tests​

For campaigns, the sender is per A/B variant - each variant can send from its own identity (and its own Customize-From, Reply-To and BCC). This lets you A/B test the From line, one of the biggest open-rate levers. See A/B Testing.

For journeys, the sender is set per email node.

Reply-To & BCC precedence (at send time)​

  • Reply-To: a per-message reply-to wins; otherwise the selected sender's own reply-to; otherwise replies go to the From address.
  • BCC: the recipient gets the per-message BCC plus the workspace compliance BCC (unioned, de-duplicated). Adding a BCC sends a copy to that address - it doubles your billable emails.
  • Custom From: the platform refuses to send from a domain that isn't SPF+DKIM verified for the workspace (it never silently substitutes a different sender).
Sign in with Apple

If your app uses Sign in with Apple, every domain you add a sender on - including a Custom From domain - must also be registered with Apple, or mail to people who chose Hide My Email bounces. See Apple Private Email Relay.