From
Send as picks where the From address comes from.
A user’s email must be on one of your connected domains to send as From. The user picker disables users whose domain isn’t connected, and publishing fails if a specific or fallback user’s domain isn’t connected. For a related user, the domain is checked at send time, since each contact can point to a different user.
A related user can’t be used when the field is empty, points to a queue or a record that isn’t a user, or the user is inactive or has no usable email. Pick a Fallback to cover those contacts:
Sender name
Name sets the display name recipients see.
A name you enter replaces the user’s name for this email only. It doesn’t change the User record.
Using the sender in Liquid
When a user is the From, the email’s Liquid can read their User record assender, using the User object’s field keys, such as {{ sender.Name }} or {{ sender.Title }}. Type / in a Liquid field to pick a field. sender is available when your workspace syncs a User object.
sender is set only when a user, including a fallback user, becomes the From. With an email sender or a fallback sender, sender fields are empty, so use a default for anything that must render. A custom sender name doesn’t change sender.
Reply to
Replies go to picks where replies are delivered.
A reply-to user needs a valid email, but not a connected domain. A related user can fall back to an email sender or a specific user, the same as From.
CC
CC copies your team on each contact’s email. Each contact gets one email with the contact in To and your teammates in CC, so a copied account executive can reply-all to start the conversation. CC is for your own team. It isn’t an extra audience, and copied teammates aren’t added as contacts or campaign members.
Each recipient is resolved on its own for every contact:
- A recipient that can’t be used is skipped, and the contact still gets the email. A dynamic recipient uses its fallback first.
- A copied address that has bounced or complained before, or is on Conversion’s global bounce list, is skipped.
- Copied teammates don’t need a subscription status, topic subscriptions, or a connected domain, and they don’t count toward communication limits.
- Addresses aren’t deduplicated. If two recipients resolve to the same person, or a recipient is also the contact, they get the email once per entry.
- An email can have up to 49 CC recipients, since an email can’t go to more than 50 addresses.
- Test sends never CC anyone.