Work Email vs Personal Email for B2B: Which One Do You Send To?

Send B2B outreach to the work email, the address on the person's current employer's domain. Use a personal address only when no work address exists, and treat it as a different kind of list.

This page defines both, compares them side by side, and shows the filter that separates them. It is not legal advice.

Key takeaways

• A work email sits on the current employer's domain. A personal email sits on webmail such as Gmail or Outlook.com.
• Work addresses can be verified. LeadOcean's verifier does not test personal addresses, so you read the risk yourself.
• A work address that belongs to a former employer is a third type, work_other. Treat it as stale.
• LeadOcean filters on emailType: work, work_other, work_any, personal, other, unknown or none.

What it is

A work email is an address on the domain of the person's current employer, and a personal email is an address the person holds outside any employer, usually on webmail.

The domain decides the type, not the content. jane.doe@acme.com is a work email while Jane Doe works at Acme. janedoe84@example.org, on a free webmail domain, is personal.

The edge case is the former employer. If Jane leaves Acme, her old Acme address is no longer her work email. LeadOcean types it work_other. Treat it as stale.

How it works

A data provider attaches each address to a person, then compares the address domain to the person's current company domain. A match is work. A mismatch with a business domain is work_other. A webmail domain is personal.

1. The provider holds a person record with a current employer and its domain.
2. Each address found for that person is checked against that domain.
3. The address gets a type: work, work_other, personal, other or unknown.
4. Deliverability is checked separately, so type and status are two fields.

Worked example, with placeholders:

Type tells you whose address it is. Status tells you whether the mailbox answers. You need both before you send.

The two fields can disagree. A work address can still be catch_all or risky. A personal address can be a real, active inbox that nobody has tested. Never read one field as a stand-in for the other.

Work email vs personal email

The two types differ in who controls the inbox, how well you can verify it, and how long it stays valid. The table sums it up.

The work endpoint returns one address or data: null, and only from the current employer. The personal endpoint returns a list with no status field, with known-bad addresses withheld (LeadOcean OpenAPI, September 2026).

When it matters

Cold outbound to a role

Use the work address. The person expects business mail there, the employer's domain gives you a verifiable mailbox, and replies reach a real inbox. Filter emailType to work and emailStatus to verified before you pull anyone.

Building a list from old data

Check for work_other. Job moves are common, and a list pulled a year ago carries addresses at former employers. Filter to work, or pick work_any if you want both kinds on purpose.

Reaching someone with no work address

A personal address is the fallback, and it carries more risk. You cannot confirm the mailbox the way you can on a company domain. Send in a small batch and watch bounces.

Choosing a send order

Set a rule before you pull the list, not after the first bounce report. A simple order works for most teams.

1. Send work addresses with verified or catch_all_valid status first.
2. Send work addresses with catch_all status second, at lower daily volume.
3. Use personal only for people with no work address, in a small separate batch.
4. Leave work_other out unless you chose work_any on purpose.

Keeping the groups separate also tells you where a bounce came from. If one group climbs, you pause that group and keep the rest running.

Privacy and consent rules

Both types fall under email rules, and neither is exempt. In the US, the FTC says CAN-SPAM makes no exception for business-to-business email (FTC CAN-SPAM guide, September 2026). In the EU, GDPR defines personal data as any information relating to an identifiable person, and a named work address can qualify (GDPR Article 4, September 2026). Ask your lawyer which rules apply to your list. This is not legal advice.

How LeadOcean handles it

LeadOcean exposes the type as a filter and a field. The filter is emailType, with seven values: work, work_other, work_any, personal, other, unknown and none. Every people-search row carries email_type, email_status and has_email.

Sizing is free. On 2026-10-01, leadocean_count_leads returned 919,502 mailable people with emailType work, jobLevel VP and country US. The same filters with emailType personal returned 5,782. Mailable here means the default emailStatus of verified, catch_all_valid or catch_all. The personal count is small because LeadOcean does not verify personal addresses, so few carry a mailable status.

The first call below sizes work-email VPs in the US for 0 records. The second is the lookup for one person, at 1 record per call. The app does the same on its Exports page, which shows the record price before you start (LeadOcean docs, September 2026).

curl -X POST "https://api.leadocean.io/v1/people/search?count=true&limit=1" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emailType": ["work"], "jobLevel": ["VP"], "country": ["US"]}'

curl -G "https://api.leadocean.io/v2/people/email/work" \
  --data-urlencode "linkedin_url=https://www.linkedin.com/in/jane-doe" \
  -H "x-api-key: $LEADOCEAN_API_KEY"

Swap the path to /v2/people/email/personal for personal addresses. The MCP server does the same sizing through leadocean_count_leads. For the lookup walkthrough, see the find work email skill and how email finders work. For the share of each type by seniority, see work vs personal email share by seniority.

Pricing is two plans: Free (1,000 records, one-off, no card) and Pro at $499 a month. See pricing. More guides live in the blog hub.

FAQ