ZapBounce + SalesCrew
Each address in your data bank carries a verdict before a cadence touches it, and an unknown result never costs you a credit.
- Checked on import and before every send
- Your own key, stored in Vault
- Unknowns and duplicates never billed
The short answer
- SalesCrew sends each new address to ZapBounce's own SMTP check and writes the answer on your contact. You get valid, invalid, catch-all or unknown, plus role, disposable and free-provider flags. The check opens a connection to the receiving server and closes it before any message is sent.
- Invalid addresses drop out when you freeze an audience and go straight to the suppression list. Catch-all and unknown results stay in the pool with a bounce-risk flag, and you decide per cadence whether flagged addresses get the send.
- Billing follows ZapBounce's rules. Valid, invalid and catch-all results cost one credit each; unknown results, duplicates and errors cost nothing. SalesCrew never re-checks an address inside the window you set, so a list you imported last week isn't paid for twice.
How it works
From a fresh import to a cadence that only sends to addresses with a verdict.
- 1
Import or source a list
Your CSV import into the data bank, an Apollo pull or a scraper drop lands in the pool as usual. SalesCrew queues each new address for a ZapBounce check the moment it arrives.
- 2
ZapBounce checks the mailbox
The check runs the syntax, looks up the domain's MX record, then opens an SMTP handshake on port 25 with the receiving server. It asks whether the mailbox exists and closes before DATA, so no email ever goes out.
- 3
The verdict lands on the contact
Valid, invalid, catch-all or unknown, with the role, disposable and free-provider flags and the date checked. Segments filter on all of them, so "valid, not a role address, checked in the last 30 days" is one saved query.
- 4
Freeze, then send
At audience freeze, invalid addresses drop out and join your suppression list, and any address older than your re-check window is checked again. At send time your cadence reads the same verdict before each email leaves your mailbox pool.
What syncs
Every call ZapBounce makes on your behalf, what it writes, and what it costs you.
| What | Mechanism | Direction | Objects | Credits |
|---|---|---|---|---|
| New address on import | POST /v1/verify on your ZapBounce key, one call per new address | SalesCrew → ZapBounce | Contacts | One for valid, invalid or catch-all; none for unknown |
| Verdict and flags | Written to your contact with the checked-on date | ZapBounce → SalesCrew | Contacts, segments | None |
| Audience freeze | Addresses past your re-check window are checked again; invalid goes to suppression | Both | Audiences, suppression list | Only the addresses past the window |
| Cadence send | The verdict is read at send time, beside your suppression check | Internal | Cadence steps, mailbox pool | None |
| Bounce-risk flag | Set on catch-all, unknown, role and disposable results; a segment filter | Internal | Contacts, segments | None |
| Hard bounce after a send | Feedback from the mailbox pool writes the address to suppression, as it already does | Internal | Suppression list | None |
| Bulk re-verify | A whole segment goes to ZapBounce's file endpoint and the results are read back | Both | Segments, contacts | Same rules, per result |
Mechanisms as of September 2026. Result names, billing rules and prices are ZapBounce's own, from zapbounce.com; its API reference is the authority on the response fields.
On the ZapBounce side
SalesCrew and ZapBounce are both built by Hashlogics, so your connection is one API key and nothing in the middle. ZapBounce's own pages cover the verifier itself. Read the ZapBounce home page for what it checks and reports, then how the SMTP check works step by step. ZapBounce pricing lists every volume from 1,000 to 1,000,000 checks.
Setup
One key, two settings, and a test import you can read back.
- 1
Get a ZapBounce key
Sign up at zapbounce.com. A new account starts with 100 free credits and the free tier recurs every month, so your first list costs nothing to check.
- 2
Store it in SalesCrew
Settings → Integrations → ZapBounce, or integration_set_key from any MCP client. The key goes into your instance's Vault and is never displayed again.
- 3
Set the window and the flag rule
Choose how old a verdict may be before an address is checked again, and whether catch-all and unknown addresses may be sent to. Both settings apply per cadence, so a warm list and a cold one can differ.
- 4
Import one list and read the verdicts
Import a CSV, open the data bank and filter on the verdict. Every row shows what ZapBounce answered and when, and the audit log shows the import that triggered it.
Questions
- Does verifying an address send the person an email?
- No. ZapBounce opens an SMTP connection to the receiving mail server, asks whether the mailbox exists, and closes the connection before the DATA step. Nothing is delivered, so nobody on your list sees a message until you send one.
- What does a catch-all result mean for my cadence?
- A catch-all domain accepts mail for any address. ZapBounce probes a random address at the same domain and labels your real one catch_all instead of guessing. SalesCrew keeps the contact, sets the bounce-risk flag, and sends only when your cadence allows flagged addresses. Yahoo and AOL domains answer this way by design.
- What does ZapBounce cost?
- Pay as you go from $5 for 1,000 checks down to $949 for 1,000,000, and your credits never expire. Only valid, invalid and catch-all results use a credit; unknown results, duplicates and errors are free. Your account also gets 100 free credits a month. Prices as of September 2026 on zapbounce.com/pricing.
- Which SalesCrew plan includes it?
- Every tier, from Core at $299 a month with unlimited seats. ZapBounce credits are bought on your own ZapBounce account, and SalesCrew adds no fee per check.
- Can an agent run the verification?
- Yes. Every SalesCrew action is also an MCP tool. An agent or a Claude session can import your list, read the verdicts and refresh a segment on its own. A send still waits in your approval queue by default, and you can stop every agent with the kill switch.
Import one list and watch the verdicts land
Valid, invalid, catch-all or unknown on every contact, in the same database as your cadences.