> ## Documentation Index > Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt > Use this file to discover all available pages before exploring further. # Sender, Reply-To & CC > Choose who an email comes from, where replies go, and which teammates are copied on each send. Every blast and workflow email has three address settings on its **Overview** tab: **From**, **Reply to**, and **CC**. Each can use a configured sender, a specific user, or the user a contact field points to, such as the contact's owner. Users are the User records in your CRM, so they don't need a Conversion account. Changes save to the email's draft and take effect once the email is published. ## From **Send as** picks where the From address comes from. | Option | Sends from | If it can't be used | | - | - | - | | **Email sender** | A [sender](/product-docs/workspace-settings/emails-and-domains/senders) from email settings | Not applicable | | **Specific user** | That user's email | The email isn't sent to the contact | | **Related user** | The user a contact field points to, such as **Owner** | The fallback, if one is set. Otherwise the email isn't sent to the contact | A user's email must be on one of your [connected domains](/product-docs/workspace-settings/emails-and-domains/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: | Fallback | Behavior | | - | - | | **No fallback** | Contacts without a usable user aren't sent the email | | **Email sender** | Sends from a configured sender instead | | **Specific user** | Sends from that user instead. Their domain must be connected too | ### Sender name **Name** sets the display name recipients see. | Send as | Name left blank | | - | - | | **Email sender** | The From shows only the address | | **Specific user** or **Related user** | The user's name from their User record. If the user has no name, only the address | 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 as `sender`, 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](/product-docs/liquid/overview#filters) for anything that must render. A custom sender name doesn't change `sender`. ## Reply to **Replies go to** picks where replies are delivered. | Option | Replies go to | If it can't be used | | - | - | - | | **Same as from** | The final From address, including a fallback | Not applicable | | **Email sender** | A sender from email settings | Not applicable | | **Specific user** | That user's email | The email isn't sent to the contact | | **Related user** | The user a contact field points to | The fallback, if one is set. Otherwise the email isn't sent to the contact | 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. | Setting | Copies | | - | - | | **Specific people** | The workspace members and users you pick, on every email. Workspace members are copied at their login email, and users at the email on their User record | | **Dynamic recipients** | For each field you add, such as **Owner**, the user that field points to on each contact. **If unavailable, copy** picks workspace members or users to copy instead when that user can't be used | 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](/product-docs/emails/email-builder/preview-and-test-send#sending-a-test-email) never CC anyone. Everyone on the email receives exactly what the contact receives. Before using CC, make sure your team understands: * Everyone on the email sees the To and CC addresses. * CC recipients get the contact's tracked links and tracking pixel, so their opens and clicks can count as the contact's and can affect how the contact is identified. * CC recipients get the contact's unsubscribe links. Using them changes the contact's subscription, not the teammate's. * A workspace member or specific user gets a copy for every contact the email goes to. A blast to 500 contacts sends each of them 500 copies. If a copied address bounces or complains, its own [recipient status](/product-docs/emails/recipients#subscription-status) changes and later emails skip it. The contact's status and delivery results don't change. ## Checking addresses before you send The [preview](/product-docs/emails/email-builder/preview-and-test-send#previewing-your-email) shows the From, Reply to, and CC a live send would use. Select a contact to see related users resolved for that contact, including any fallback. The preview also shows CC recipients that would be skipped, and why. Publishing reports problems in the email's issues list, such as a user that no longer exists, a user From whose domain isn't connected, or more than 49 CC recipients. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.