Email verification for CRM hygiene
CRM contacts go bad without anyone touching them: people change jobs, companies change domains, inboxes get abandoned. Re-verify your contacts on a schedule, mark the dead ones as bounced instead of deleting them, and verify new records as they arrive.
Why CRM email data decays
A CRM decays even if nobody touches it. People change jobs and their work addresses are switched off. Companies rebrand, merge or move to a new domain. Contacts arrive from event lists, enrichment tools and old imports with no record of when the address last worked.
Some of that decay is invisible. Catch-all domains keep accepting mail for people who left years ago, so no bounce ever comes back and the contact looks healthy in every report. The rest shows up as bounces on sales sequences and marketing sends, which count against your sending domains. And if your CRM or email platform is priced by contact count, you're paying for every dead record.
Re-verify on a schedule
- 01
Export with the record ID
Include the email address and the CRM's record ID, plus anything you segment on. The ID is what lets you import results back as an update.
- 02
Upload the file
MailVet removes duplicates and malformed addresses for free, then verifies the rest, catch-alls included.
- 03
Download every row
Your columns come back unchanged, with
mailvet_result,mailvet_reason,mailvet_scoreand flag columns added. - 04
Import it as an update
Match on record ID and map the result columns to custom fields, such as Email status, Email status reason and Email verified on.
- 05
Act on the results
Exclude undeliverable contacts from email, review the risky ones, and re-run unknowns a day later.
- 06
Repeat every quarter
Keep a view of contacts whose verified date is more than 90 days old, and run it again.
What to set in your CRM for each result
| Result | Set in the CRM | Why |
|---|---|---|
deliverable | Email status: valid, plus the date | Safe to email; check again next cycle |
undeliverable | Mark as bounced and exclude from email; keep the record | History and deal links stay, and the address can't sneak back in |
risky · mailbox_full | Flag and exclude until re-checked | Full mailboxes are often abandoned ones |
risky · disposable | Flag | Rare in B2B; usually a form signup that was never real |
unknown | Leave the status alone and re-run later | No credit used, and a later run usually settles it |
role flag | Keep, but leave out of one-to-one sequences | Shared inboxes like info@ rarely reach the person you want |
Mark bounced, don't delete
Deleting a dead contact feels like cleaning, but it throws away things you'll want later:
- History. Emails, calls, meetings and deal associations go with the record.
- Memory. The next lead-database export or enrichment run can re-create the contact with the same dead address, and nothing warns you it bounced before.
- Suppression. A bounced status that syncs to your sequencer and email platform stops every tool from sending to it, not just the CRM.
- The person. Someone who changed jobs is often still a prospect at their new company. Update the record with the new address instead of deleting it.
Verify new contacts as they arrive
A quarterly clean fixes the backlog. Checking at the point of entry stops it from building up again.
Signup and lead forms
Verify in real time from your backend so bad addresses never get in. See /use-cases/signup-form-verification.
Before every CSV import
Run event lists, partner lists and enrichment exports through /bulk-email-verification before they reach the CRM.
When records are created
Have your workflow tool or a small worker call the API when a contact is created and write the result to a field. Pending checks finish by webhook; see /docs/webhooks.
Before a big send
Re-verify a segment that hasn't been emailed in months before it goes into a campaign.
Automate the quarterly run with the bulk API
Send the export as a bulk job and download every row when the bulk.completed webhook arrives. Your original columns, record ID included, come back unchanged with the result columns appended, so the file can go straight back into the CRM as an update. Reference in /docs/bulk.
# 1. Send the CRM export as a bulk job
curl https://api.mailvet.app/v1/bulk \
-H "Authorization: Bearer mv_live_…" \
-F "file=@crm-contacts.csv" \
-F "email_column=Email" \
-F "webhook_url=https://example.com/hooks/mailvet"
# 2. When bulk.completed arrives, download every row with results
curl "https://api.mailvet.app/v1/bulk/blk_01JD9A4ZK2/results?format=csv" \
-H "Authorization: Bearer mv_live_…" \
-o crm-contacts-verified.csvCRM hygiene questions
How often should I verify my CRM contacts?
For an active B2B database, every three months, and always before a large campaign to contacts you haven't emailed recently. Verify new contacts as they arrive so the backlog doesn't build up again.
Should I delete invalid contacts from HubSpot or Salesforce?
Usually not. Mark them as bounced and exclude them from email instead. Deleting loses the activity history and makes it easy for the same dead address to be re-imported later.
Does verifying contacts send them an email?
No. Verification works at the DNS and mail-server level and stops before any message is sent, so contacts see nothing.
Can I verify only part of my CRM?
Yes. Export just the segment you care about, such as contacts in active sequences or a list you're about to email, and verify that file.
What happens to my contact data after verification?
Uploaded files and results are deleted automatically 30 days after the job finishes, or straight away when you delete them. MailVet doesn't sell, share or reuse your contacts.
See how much of your CRM still works
Export a segment, upload it, and get a result and reason for every contact. Your first 100 are free.
Related
Last updated November 13, 2026