Skip to main content

Managing Email Personas

Strategies and technical controls for managing multiple sender identities (Personas) to achieve horizontal scale.

Updated over 2 months ago

What is a Persona?

A "Persona" is a specific sender identity attached to an email address. For example, [email protected] is a persona. In the world of high-volume outbound, you cannot rely on a single persona to send 5,000 emails. You need a team of personas (digital twins) to distribute the load.

The "5 Accounts Per Domain" Rule

SendScale promotes a strict architectural best practice: Maximum 5 Email Accounts per Domain.

Why this suggestion exists: Deliverability reputation is shared at the domain level.

  • If you create 50 accounts on one domain ([email protected]... [email protected]) and one user gets flagged as spam, the entire domain is penalized. All 50 users go to spam.

  • By limiting it to 5, we force Horizontal Scaling. To send more emails, you buy a new domain. This compartmentalizes risk. If Domain A has issues, Domain B, C, and D continue running smoothly.

Adding & Removing Personas

Adding a New Persona

  1. Navigate to Accounts.

  2. Locate the "Add new" button.

  3. Purchase your desired domain.

  4. Enter the First Name, Last Name, and desired handle for each persona.

  5. The monthly billing will update ($5/seat) automatically.

Managing Existing Personas

In the domain configuration view (as seen in the screenshot), you will see a list of all active personas on that domain.

  • Status: A green checkmark indicates the account is active and authenticated.

  • Deactivating: You can delete a persona by clicking the Red Trash Icon.

    • Warning: Deleting a persona permanently removes its warmup history and data. If you just want to stop spending money, consider pausing it, though billing is typically based on active seats.

Strategic Naming Conventions

When creating multiple personas for yourself, avoid using "Sales" or "Info". Use human names.

  • Why? This looks more natural to spam filters than having 50 identical john@ addresses sending identical content.

Did this answer your question?