A Lead Has Two or Three Email Addresses: Which One Should You Send To?

Send to one address per person, chosen by evidence. Verify every candidate first. Then prefer, in order: verified valid over catch-all over unknown; a work address over a personal one; the company's current domain over an old one; and the company's usual address pattern over an odd format. Keep the other addresses in a separate field so they never reach the send column, and suppress all of them if the person opts out. Emailing every address you have doubles the bounce risk and, when two are aliases of the same inbox, sends the same email twice.

This comes up whenever leads pass through more than one tool. An enrichment waterfall returns a different address from each provider, a merged list carries two versions of the same person, or a CRM has a "work email" and an "other email".

Where multiple addresses come from

Source	What you get
Enrichment waterfall	Each provider's best guess, sometimes different. See lead enrichment explained
Merging lists from several vendors	The same person under two addresses, one per vendor
CRM fields	Work, personal and "other" email columns, filled over years
Website and directory scrapes	A personal address and a company address on the same page
Company rebrands or acquisitions	name@oldbrand.com and name@newbrand.com
A cell with several addresses	"anna@acme.com; anna.k@acme.com" in one field

If several addresses are packed into one cell, split them into rows first with the free split multiple emails in a cell tool.

Step 1: verify every candidate

The first address in a row is often there because that tool answered first, not because it is the best. Put every candidate through verification and record each result next to it.

Candidate	Result
anna.kowalski@acme.com	Valid
akowalski@acme.com	Invalid
anna@acme-group.com	Invalid, domain has no mail
anna.k.1988@gmail.com	Valid

Here the choice is easy: the valid work address. When results are less clear, the next steps decide.

Step 2: apply the order of preference

Priority	Prefer	Over	Why
1	Verified valid	Catch-all, unknown, invalid	A server confirmed the mailbox
2	Work address	Personal address	Where they read work mail; fewer complaints. See personal emails in a B2B list
3	Current company domain	Old or acquired domain	Old domains are retired or forward for a limited time
4	The company's usual pattern	An unusual format	Patterns are consistent inside a company. See email address patterns
5	Address seen in more than one source	Address from one source	Agreement between sources is weak but useful evidence

Valid beats everything. A personal address that verifies valid still loses to a work address that verifies valid, because of rule 2. But a work address at a catch-all domain is not confirmed, so you are choosing between a confirmed personal address and an unconfirmed work one. For an employee at a larger company, most teams still pick the work address and treat the lead as unconfirmed, or drop the lead, rather than pitching a personal inbox.

Hard cases

Two valid work addresses at the same domain. Both may be real. Many companies give staff an alias (anna@ and anna.kowalski@) that delivers to one mailbox. Pick the one in the company's standard pattern. Never send to both; it is the same inbox. The free email format finder shows a company's most likely pattern.

All candidates at a catch-all domain. Verification cannot confirm any of them. Pick the one in the company's known pattern, if you can find the pattern from colleagues' confirmed addresses elsewhere. Send it in your catch-all segment and let the result decide. Our guide to catch-all leads in a sequence covers what step 1 tells you.

An old domain and a new one. After a rebrand, the old domain may still accept mail for a while, then stop. Prefer the new domain. Our post on bounces from one company's domain explains what a migration looks like in bounce data. Use the free domain age checker and email provider lookup to see which domain is current.

Every candidate invalid. The person may have left. See the email is valid but the person left for the related case, and look for whoever holds the role now.

Step 3: keep one send column

Once you have chosen, structure the file so only the chosen address can be mailed:

Column	Contents
email	The single chosen address
email_status	Its verification result
other_emails	Every other candidate, separated by semicolons
email_source	Which tool or list the chosen address came from

Sequencers and CRMs import the email column as the send address. Anything in other_emails stays as a reference.

Step 4: suppress all of them on opt-out

If the person unsubscribes, replies "remove me" or bounces at the chosen address, suppress every address you hold for them, not only the one you sent to. Otherwise a later import that picks a different "best" address mails them again. Our guide to cold email suppression lists covers keeping one list across tools. If a later campaign rebuilds the list from the raw enrichment output, re-run the same choosing rules and check against suppressions before upload with compare email lists.

Dedupe before you choose

The same person can also appear as two separate rows, each with one address. Before choosing, group rows by person:

1. Normalise addresses: lower-case, trim spaces. For Gmail, dots and plus tags reach the same inbox; the free Gmail address normalizer handles that.
2. Group by name plus company domain, or by a profile URL if your data has one.
3. Collect every address in the group as candidates, then run steps 1 to 3.
4. Remove exact duplicates with remove duplicate emails.

What it costs to verify every candidate

Verifying three candidates per lead costs three checks instead of one. For most teams it is still cheaper than the alternative: a bounce on a wrong address costs a send, adds to your bounce rate and can hold up a campaign. The free verification cost calculator prices it for your volume. If your candidates per lead are many, verify the top two first and only check the rest if neither comes back valid.

A quick checklist

• Split cells with several addresses into separate candidates.
• Group rows by person before choosing.
• Verify every candidate, or the top two first.
• Choose one: valid, work, current domain, standard pattern.
• Keep the rest in other_emails, never in the send column.
• Tag where the chosen address came from, so you can score sources over time. See testing a new lead source.
• Suppress every address for a person who opts out or complains.

Where SimpleVerifier fits

SimpleVerifier checks each candidate with a live mailbox check and returns valid, risky or invalid with a reason, so you choose on evidence. Catch-alls come back risky and graded rather than guessed valid, and rows we could not check come back for retry. Upload all candidates as one CSV on the verify page; the first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.