Outreach
Build outreach lists that protect your sender reputation
For Sales teams, lead generation agencies and outbound operators
The problem
A bought list with a 30% bounce rate does not just waste a campaign: it damages the sending domain in a way that takes months to repair, and it is invisible until the damage is done.
How the data solves it
Enrich contacts on demand rather than reading from a stale cache, and inspect the deliverability signals before sending. Mailbox provider and category identify catch-all and role addresses so you can exclude them up front.
The filter set this maps to
Every field below exists in the shop schema. This is the query, not an illustration.
- Has email
- yes
- Mailbox category
- exclude catch-all and role addresses
- Mailbox provider
- segment by provider
- Status
- live
Build it
Four steps to this list
Every column named here exists in the schema, and the request below runs as written.
- 1Set has_email = yes.
- 2Set mailbox_category = business to exclude catch-all and role addresses.
- 3Set status = live so you are not writing to a dead storefront.
- 4Export mailbox_provider to segment your sending patterns by provider.
The same query through the API
POST this to /api/v1/search for a count, or /api/v1/rows for the shops themselves.
{
"filters": [
{
"kind": "dropdown",
"col": "has_email",
"values": [
"yes"
]
},
{
"kind": "dropdown",
"col": "mailbox_category",
"values": [
"business"
]
},
{
"kind": "dropdown",
"col": "status",
"values": [
"live"
]
}
]
}Playbook
What to do once you have the list
A list is not a campaign. These are the three things that decide whether it converts.
Drop the risky addresses first
mailbox_category identifies catch-all and role inboxes before they ever reach your sending tool. Those are the ones that damage a sending domain.
Segment sends by provider
mailbox_provider lets you pace Google Workspace and Microsoft 365 separately, which matters once you are sending at volume.
Verify at send time
Contacts are fetched when you ask, not served from a cache of unknown age — so the address you send to was checked recently, not last quarter.
Outcome
What you end up with
Lists filtered by deliverability before the first send
Contacts verified at request time rather than cached
Provider segmentation for sending-pattern control
Questions
Outreach: frequently asked
Do you guarantee email deliverability?
No, and nobody credibly can: mailboxes change without notice. What we do is expose the signals that predict a bounce (mailbox provider, category, MX host) and verify at the moment you request the contact rather than serving a cached value of unknown age.
How do I avoid catch-all addresses?
Mailbox category identifies catch-all and role-based addresses, so you can exclude them from an export before they ever reach your sending tool.
How do I keep a list from damaging my sending domain?
Send only to routes that were verified when you asked for them, and use the deliverability signals before you send rather than after. Mailbox provider and mailbox category tell you what sits behind the address, so you can treat a role account differently from a personal one and drop anything that looks risky before it enters the sequence.
Are the contact details verified at the moment I export them?
Enrichment is on demand rather than served from a cache of unknown age, so the check happens when you ask for it. That is the whole reason it costs a credit: you are paying for a fresh result rather than for a row somebody verified a year ago.
What is the responsible way to use business contact data?
Treat it as business contact routes published by businesses to be contacted through, because that is what it is. Comply with the marketing law of every jurisdiction you send into, honour removal requests immediately, and forward any request to support so the record is suppressed at source rather than only in your copy.
Start finding better e-commerce leads today
Free trial with the full dataset and every filter, and the allowance resets daily rather than expiring.