Addresses such as sales@, support@, info@, and webmaster@ describe a function, while a named address may identify one person. RFC 2142 documents common role mailbox conventions, but a prefix alone does not prove who reads the address or whether it is appropriate for a campaign. Classification should guide review and routing, not manufacture certainty.

VISUAL LESSON

What you will learn

  1. 01Classify role and person mailboxes cautiously.
  2. 02Preserve evidence and uncertainty.
  3. 03Route and suppress each contact appropriately.
Shared role inboxes and named-person inboxes separate into different verified outreach queues
Mailbox type changes the routing plan, but public evidence and suppression still govern use.

ILLUSTRATIVE WORKED EXAMPLE

Classify an illustrative email review batch

Public addresses reviewedIllustrative batch
100
Functional role mailboxShared-function evidence
46
Named-person mailboxPublic person-role evidence
34
Uncertain or suppressManual review
20
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Move from raw address to governed contact route

Source01Capture the public context

Record URL, page label, business, location, collection date, address as published, and the campaign purpose.

Classify02Normalize and review evidence

Compare prefix, named person, title, domain, contact-page wording, and ambiguity; never guess a person from a shared box.

Route03Apply owner and suppression

Choose shared-inbox or person workflow, check opt-outs and recent contact, send only an appropriate message, and log outcomes.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Public source → mailbox classification → routing rule → suppression check

PreserveSource and date
ClassifyRole, person, unknown
GovernOwner and opt-out

THE LEAD ATLAS METHOD

Lead Atlas Data can research a custom business-contact list for the customer's exact campaign, markets, locations, and categories while preserving source context for role-versus-person review.See how custom list research works ↗
01

Preserve source and purpose

Record the exact public page, visible label, business, location, collection date, address, contact instructions, and campaign purpose. Keep the original string alongside normalized values and do not detach an address from its business context.

Confirm that the campaign is relevant to the business and that the team has a lawful, policy-approved outreach process. Publicly available does not mean permission for every use.

02

Normalize without changing identity

Trim whitespace, standardize casing for comparison, validate basic structure, separate local part and domain, and preserve aliases and plus tags. Review domain ownership and obvious typos without inventing a corrected mailbox.

Treat DNS or domain capability as separate from a specific mailbox. A syntactically valid address is not proof that the inbox exists, is monitored, or will accept a message.

03

Classify from evidence

Use role prefixes, page wording, a published name, published title, about-page evidence, and domain context to classify functional role, named person, generic unknown, or needs review. Record confidence and evidence rather than a binary guess.

Sales, support, info, billing, abuse, postmaster, and webmaster can serve defined functions, but conventions vary. Do not assign a private person or buying authority to a shared mailbox.

04

Choose the communication route

Send operational or sales messages only to a relevant function and adapt the opening accordingly. For a named person, verify that the public role and business context still fit the message and avoid sensitive or personal inference.

Apply customer, active-opportunity, partner, competitor, employee, bad-contact, complaint, opt-out, and recent-touch suppression. Provide clear identification and an honored opt-out route according to applicable rules and policy.

05

Measure quality and update state

Track bounce, routing response, opt-out, complaint, positive reply, referral to another function, stale record, and correction without using opens as proof of human interest. Feed verified changes back into the research record.

Deliverable: source-preserved address table, normalization rules, mailbox classification and confidence, evidence notes, routing owner, suppression results, compliant template, send log, outcome taxonomy, correction queue, and next verification date.

LEAD ATLAS WORKBOOK

Turn this lesson into a research brief.

Apply “B2B Role Mailbox vs. Person Email: Classify the Contact Path Before Outreach” to one campaign before requesting or using a list.

  1. 01Market boundary

    Name the locations and business categories this decision applies to.

  2. 02Fit evidence

    Write the public signals that would make a business relevant enough to review.

  3. 03Exclusions

    List the business types, markets, and records that should not enter the campaign.

  4. 04Outreach use

    State who will review the list, personalize the message, and record outcomes.

THE TAKEAWAY

Classify the mailbox from public evidence, route functional and person-specific addresses differently, and never treat an address pattern as proof of consent, authority, deliverability, or response.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.