Every list has two kinds of address in it: a mailbox that belongs to a person, and a mailbox that belongs to a function. A verifier calls both of them valid, because both of them exist. That one word is where an outbound plan quietly stops being about people.
What a role mailbox is
info@, sales@, support@, hr@, press@, office@ — the address is a routing rule, not an identity. Mail to it is read by whoever is on the rota, forwarded to a shared tray, or turned into a ticket. Deliverability is not the problem: role mailboxes are often more reliable to deliver to than personal ones, because they were built to accept mail from strangers.
The problem is ownership. Nobody wakes up responsible for that inbox, so nobody has a reason to answer you personally.
Same list, two outcomes
| Personal mailbox | Role mailbox | |
|---|---|---|
| Who reads it | One named person | A shared queue or rota |
| Accepts mail from strangers | Yes, filtered by relevance | Yes, by design |
| Bounces more? | No — it goes stale when someone leaves | No — it is kept alive for inbound |
| Replies | Yes, if the offer is about them | Rarely, usually by routing it elsewhere |
| Right for first touch | Yes | No |
| Right for vendor forms, partnerships, press | Maybe | Yes — it is the address they published for that |
So a list can be 100% deliverable and still be the wrong list. valid describes a mailbox, not a recipient. Mix the two buckets and every metric downstream — reply rate, cost per reply, "our campaign flopped" — measures a blend instead of a channel.
The numbers that decide the order of operations
- 23% of contacts change jobs every year (ZoomInfo, 2025)
- 40% of addresses are dead within two years (NeverBounce)
- Fresh data outperforms stored databases by 42% (Harvard Business Review, 2024)
- Personalised emails get 3.2x higher open rates (HubSpot, 2025)
- Verified lists bounce 2–5% against 10–35% for static, resold databases
The 23% is the one that matters here. A role mailbox survives a job change; a personal one does not. So a list of role addresses ages more slowly and converts worse, while a list of people is fresher and expires faster. Neither is "better". They answer different questions, and the honest move is to keep them in separate columns.
Three rules that keep the buckets apart
- Count usable contacts, not valid ones. The number that matters is addresses belonging to a person that answered at the time you checked. Role addresses are a second number, not part of the first.
- Use role addresses where they are the point. Vendor forms, partnership requests, press, procurement — the queues that exist because the company wants that traffic.
-
Never let
unknownpromote itself. A catch-all domain that accepts anything without confirming is not a yes. Keep it its own state and decide separately whether to spend a send on it.
The trap is not sending to info@. The trap is not knowing what share of your list is info@ when the reply rate comes in low — and then rewriting the subject line.
Where the API sits
TAPAC verifies inside the search request: each contact comes back with the address, the source page or profile it was found on, and its SMTP state as of that call. A role mailbox arrives labelled as the mailbox it is, next to the source that may hold a named person instead — and there is no stored copy of the mailbox to go stale in the meantime.
npx -y @tapacapi/mcp # tools: tapac_find_contacts, tapac_status
# hosted: https://tapacapi.com/mcp
# REST: POST https://tapacapi.com/v1/contacts/search
100 free searches, then $0.10–0.50 per verified contact, pay-per-use. You pay for the lookups you make, not for a seat on a database you then have to clean.
Published from tapacapi.com — TAPAC is an MCP server and REST API for verified B2B contacts.
Top comments (0)