ZapBounce and SalesCrew
ZapBounce verifies contacts inside SalesCrew, so a dead address never reaches a cadence. Every row in an import is checked as it lands, a contact with no verdict is checked before its first step goes out, and the result is written to the contact record. 1,000 checks cost $5, and unknown results are never billed.
Both products are built by Hashlogics, which is why the check runs inside the CRM itself. You paste a ZapBounce API key once, SalesCrew keeps it in its Vault, and from then on every check calls the ZapBounce API from SalesCrew's own servers. There's no export, no file to re-import and no middle tool to babysit.
SalesCrew itself lives at salescrew.io, and its side of this connection, with the CRM screens, is on SalesCrew's ZapBounce page. Tiers are on SalesCrew's pricing page; every tier has unlimited seats, so the check runs for your whole team at no per-seat cost.
A dead address in a cadence costs more than one bounce
SalesCrew sends cadences from a pool of mailboxes, with daily caps per mailbox and per domain. A hard bounce lands on whichever mailbox sent that step, and SalesCrew suppresses the address on the spot. The bounce still counts against that sending domain, and a list with a few hundred dead rows spreads those bounces across your whole pool.
The quieter cost sits in your pipeline. A rep enrols a lead, three steps go out, nothing comes back, and the lead is marked as worked. Multiply that over a quarter and your reply rate describes addresses that never existed.
Checking at the import is where the fix is cheapest. A row that comes back invalid never reaches a segment, never gets a step, and never touches a mailbox's reputation. Our bulk verification page covers how a file is checked; here, the file is your SalesCrew import.
How the data moves
Every import is checked as it lands
When you import a CSV into SalesCrew's Data Bank, SalesCrew sends the address column to
POST /v1/filesas one batch. An address that appears twice in the file costs one credit, and each row comes back valid, invalid, catch_all or unknown.A contact is checked before its first send
When a segment freezes for a cadence, SalesCrew finds the contacts with no verdict yet and checks each one through
POST /v1/verify. An invalid contact is suppressed before the first step, so the cadence opens with addresses that can receive it. A contact that already has a verdict is skipped, so nothing is checked twice.Bounce risk becomes a flag on the contact
A catch_all or unknown result sets a bounce-risk flag on the contact. Your segments can filter on it, so those contacts go out as a smaller group, get a call task instead, or stay out of a launch send.
The verdict is written back and stays with the record
SalesCrew stores the result, the role and disposable flags, and the check date on the contact. Segment filters read the same fields, and so do your agents over MCP: a Claude or ChatGPT session sees the verdict your rep sees.
What syncs, and which way
| What moves | Direction | Where it lands |
|---|---|---|
| Import rows (CSV into the Data Bank) | SalesCrew to ZapBounce | POST /v1/files, one batch per import |
| Contacts with no verdict at segment freeze | SalesCrew to ZapBounce | POST /v1/verify, one call per contact |
| Result: valid, invalid, catch_all or unknown | ZapBounce to SalesCrew | A field on the contact record |
| Role flag, disposable flag, check date | ZapBounce to SalesCrew | Fields on the contact record |
| Bounce-risk flag (catch_all or unknown) | Set inside SalesCrew | Contact field, usable in segment filters |
| Invalid result | Set inside SalesCrew | Suppression list; the contact keeps its history |
| Your ZapBounce API key | You to SalesCrew, once | SalesCrew's Vault, never displayed again |
Every check is billed to your ZapBounce account at the pay-as-you-go rate. Unknown results and duplicates are never billed.
Setting it up
- Create a ZapBounce API key on the API key page and label it SalesCrew.
- In SalesCrew's settings, add ZapBounce as an integration and paste the key. SalesCrew stores it in its Vault and never displays it again.
- Import a CSV into the Data Bank. The batch is checked as it lands, and each contact gets its verdict.
- Build a segment that excludes the bounce-risk flag for your main sends, and a second one that includes it for a slower, smaller cadence.
- Enrol the segment in a cadence. Contacts with no verdict are checked at freeze, before the first step.
- Read the verdict on the contact record, or ask for it over MCP from Claude, ChatGPT or Cursor.
SalesCrew: common questions
Does SalesCrew verify emails before a cadence sends?
Yes. When a segment freezes for a cadence, SalesCrew checks every contact that has no verdict yet through the ZapBounce API and suppresses the invalid ones before the first step goes out. A contact that already has a verdict from the import is skipped, so nothing is checked twice.
What does verifying inside SalesCrew cost?
The checks are billed to your own ZapBounce account: 1,000 for $5 and 10,000 for $25. Unknown results and duplicates are never billed, credits never expire, and every new account starts with 100 free credits a month.
Where does the verdict show in SalesCrew?
On the contact record, as a result field with the role and disposable flags and the check date beside it. Segments filter on the same fields, and your agents read them over MCP, so a Claude session sees the verdict a rep sees.
Does ZapBounce email my SalesCrew contacts?
No. ZapBounce opens an SMTP connection to the receiving mail server, asks about the mailbox, and closes the connection before any message is sent. Nothing goes out through your mailbox pool, and nothing counts against its daily caps.
Is my ZapBounce key safe inside SalesCrew?
SalesCrew keeps credentials in its Vault and never displays a key after entry. Each client instance runs on its own database, so the key lives in your instance and nowhere else.
Verify your SalesCrew contacts today
100 free checks a month, no card. Unknown results and duplicates are never billed.