info@ is not a person - and your reply rate already knows it
Every outbound list contains two kinds of address: 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 single word is where an outbound plan quietly stops being about people.
What a role mailbox actually 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 filtered into a queue with a ticket number. Deliverability is not the problem: role mailboxes often accept mail more reliably than personal ones, because they are built to receive from strangers.
The problem is ownership. Nobody wakes up responsible for the inbox, so nobody has a reason to answer you personally.
Same list, two very different outcomes
| Personal mailbox | Role mailbox | |
|---|---|---|
| Who reads it | One named person | A shared queue or a 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, and usually by routing the message elsewhere |
| Right for first touch | Yes | No |
| Right for signing up, vendor forms, partnerships | Maybe | Yes - it is the address the company published for exactly this |
This is why 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 mixture instead of a channel.
The numbers behind the mixture
| Observation | Number | Source |
|---|---|---|
| Contacts who change jobs in a year | 23% | ZoomInfo, 2025 |
| Addresses dead within 2 years | 40% | NeverBounce |
| Fresh data vs stored databases | +42% | Harvard Business Review, 2024 |
| Personalised emails: open rates | 3.2x | HubSpot, 2025 |
| Bounce rate: verified vs static list | 2-5% vs 10-35% | TAPAC |
The 23% figure is the one that decides the order of operations. A role mailbox survives a job change and a personal one does not - so a list built mostly on 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 thing to do is keep them in separate columns.
Three rules that keep the buckets apart
- Count usable contacts, not valid ones. The number that matters is addresses that belong to a person and answered at the time you checked. Role addresses belong in a second number, not folded into the first.
- Use role addresses where they are the point. Vendor forms, partnership requests, press, procurement, anything that a queue is supposed to handle. Those queues exist because the company wants that traffic.
- Never let
unknownpromote itself. A catch-all domain that accepts every address without confirming is not a yes. Keep it its own state and decide separately whether to spend a send on it.
info@. The trap is not knowing what share of your list is info@ when the reply rate comes in lower than expected - and then changing the subject line.What TAPAC returns per contact
A search returns the address, the source page or profile it was found on, and its SMTP state as of that call - so a role mailbox arrives labelled as the mailbox it is, next to the source that shows whether a named person was available on the same page. There is no stored copy of the mailbox to go stale in the meantime.
npx -y @tapacapi/mcp # tools: tapac_find_contacts, tapac_status # or hosted: https://tapacapi.com/mcp # or REST: POST https://tapacapi.com/v1/contacts/search
100 free searches to start, 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.
← Back to TAPAC