Why is the wrong sender name appearing in my email variables?

Last updated: May 5, 2026

Context

When using sender variables in email templates (such as sender first name), you may notice that the wrong name appears in both the email draft editor and sent emails. This typically happens when there's a mismatch between the mailbox owner and the assigned user.

Additionally, person/prospect variables like {First Name} have specific normalization behavior that may affect how they display in your emails.

It’s important to distinguish between sender variables (like “Sender First Name”) and person/prospect variables (like “Person First Name”). Sender variables pull information about the email sender, while person variables pull information about the email recipient. Using “Sender First Name” when you intend to personalize with the recipient’s name will result in the sender’s name appearing instead.

Answer

The sender name variable pulls from the "assigned user" field rather than the mailbox owner. However, if you’re seeing the wrong name in personalization fields where you expect the recipient’s name to appear, verify that you’re using person/prospect variables (like “Person First Name”) rather than sender variables (like “Sender First Name”). To ensure the correct sender name appears when using sender variables:

  1. Navigate to the mailbox settings page at Settings > Deliverability > Mailboxes

  2. Verify that the assigned user matches the mailbox owner

  3. If there's a mismatch, update the assigned user to match the intended sender

Important: The assigned user setting determines which name will appear when using sender variables (like “Sender First Name”) in your email templates, even if you're using a different team member's email address. If you want to personalize emails with the recipient's information, use person/prospect variables (like “Person First Name”) instead.

Note: The {First Name} variable (and similar person/prospect variables) automatically normalizes to only the first token before a space. For example, "Hot Girl Soda Team" will display as just "Hot" in emails. This is intentional behavior to avoid awkward greetings in most use cases. If you need the full name to appear for generic team inboxes (like info@, support@, hello@), use a different field such as Company Name or a custom property instead.

Note: If a sender variable is missing a value (such as an empty first name field), the email will be blocked from sending. To work around this, create a smart snippet that uses the sender variable with a fallback value like "hey there" when the field is empty.

Sender Variables with Non-Unify Users and External Contractors

When working with team members who aren't active Unify users (such as external contractors or employees who don't have Unify accounts), sender variables create a specific challenge that requires additional consideration.

Common Scenario with Non-Unify Team Members

If you're sending emails on behalf of team members who aren't Unify users, their mailboxes will be assigned to an active user (often the person managing those mailboxes). In this case, emails sent from those mailboxes will use the assigned user's name in sender variables, even though the email address belongs to the non-user team member.

Example: If you're using a team member's email address who isn't a Unify user (like an external contractor), their emails will still be signed with the assigned user's name and signature, not the email address owner's information.

Resolution for Non-User Scenarios

To properly resolve sender variable mismatches when the mailbox owner isn't a Unify user, the mailbox owner needs to become an active Unify user and log in so their mailbox can be properly assigned to them. This ensures that sender variables will pull from their actual profile information rather than the managing user's details.

Key Clarification

Sender variables always pull from the assigned user's profile information, regardless of which actual email address is being used to send the message. If mailboxes are assigned to the wrong user, sender variables will display that user's information instead of the actual mailbox owner's details.

Team Transition Management for Email Variables

When team members leave your organization, their names may continue appearing in email signatures and sender fields if mailbox assignments aren't properly updated. This creates confusion for recipients and can impact your professional communication.

Understanding the Mailbox Reassignment Process

  • Timeline: The reassignment process takes approximately 1 week to complete.

  • Temporary disconnection: Mailboxes must be temporarily disconnected from Unify during the changeover period.

  • Rewarming required: Mailboxes that are already warmed will need an additional 1‑week rewarming period after reassignment.

  • Enrollment management: All existing enrollments on those mailboxes must be cancelled or reassigned before the transition.

Tip: Consider taking a phased approach when reassigning multiple mailboxes to avoid losing your entire mailbox capacity at once during the transition period.

Prevention Steps for Team Changes

  1. Audit all mailbox assignments - Review which mailboxes the departing employee was assigned to across your account

  2. Transfer assignments proactively - Reassign all their mailboxes to current team members before the employee's departure date

  3. Verify email templates - Check that any templates using sender variables will pull the correct information from the new assigned users