Contact verification is the gate between a researched contact and a live cadence. Treat it as a decision process: confirm the route, check the record against another source, and decide whether to send. Match the depth of the check to the cost of a bad record. A routine record may need only a light check. A record with greater delivery or identity risk needs more checking across its reachable routes and current context. This keeps verification from becoming a ritual and puts effort where a wrong address or stale contact can do the most damage.
Run contact verification in order
Use a fixed order so every record reaches the same decision point. Keep the result beside the contact, including the reason for any repair or hold.
| Stage | What you are trying to learn | Example question |
|---|---|---|
| Record | Which contact fields and context need checking | Which email and phone are attached to this person? |
| Email route | Whether the address can accept outreach | Is this address ready for outreach? |
| Phone route | Whether the call route works | Which number should the caller try? |
| Identity | Whether the record still describes the right person | Does this person still match the record? |
| Decision | Whether the contact should be sent, repaired, held, or suppressed | What would make this record safe to send? |
Start with the record you plan to use, then test each route separately. Move forward when the address, phone path, and identity tell the same story. Send the contact back for repair when they disagree.
Check the email route
Email checks show whether an address is ready for a cadence and when to stop. Tie the check to the exact address you plan to use.
A verification process can check spam traps, formatting and syntax errors, domain records, and individual mailbox validity.1 An email bounce occurs when the receiving server refuses to accept a sent message.2 Emails commonly bounce when the recipient does not exist, including addresses with typos or addresses that are no longer used.3
Use the result to route the record. Send a syntax or domain failure to repair. Send an invalid mailbox to hold or removal. A passing result moves the contact to the identity check. Preserve the failure state so the next person who touches the record knows what needs fixing.
Check the phone route and identity
Email status covers one route. Check the phone path and the person behind the record separately before treating the contact as ready.
Validation can check whether the phone path works and whether the email was delivered.4 Cross-check CRM contacts in Sales Navigator when you review the record.5 Stop when the sources disagree. A different name, company connection, or current contact path means the record needs repair before it enters a cadence.
When a contact has several possible routes, choose the one still supported by the current record. If the email passes while the phone path fails, keep the contact in repair until you know which route is usable. If the identity is unclear, pause the send and resolve the record first.
Compare verification tools by workflow
A tool earns its place when its output changes what you do with a record. Compare tools by coverage, timing, result detail, and how much checking they support when a bad record carries more risk.
Run new contact lists through a verification tool before the initial send.6 The result should explain why a contact failed, stay with the record, and fit the way your list enters the cadence. If calls are part of the motion, an email-only result leaves the phone decision open.
Set the depth of the check to the risk. Higher risk calls for more extensive verification.7 A tool that handles only basic email status may suit a low-risk list. A record with uncertain identity or several possible contact paths needs a process that helps you check each route and explain the final decision.
Test the workflow on a representative batch before committing the whole list. Look for clear pass, repair, and hold states. If the output leaves you guessing, the tool has added a result without giving you a decision.
Use bounce rate to find list problems
Bounce rate is feedback for the list and sending setup, so review it during the campaign.
Email bounce rate is the proportion of sent cold emails that cannot be delivered to the recipient.8 Calculate it by dividing bounce-back messages by total emails sent, then expressing the result as a percentage.9 Inspect the bounce-back message for the receiving server's reason.10
A consistently high bounce rate harms sender reputation with email providers and can lead to blocklists.11 Bounce rate can help you troubleshoot technical setup, mailing-list quality, sender reputation, and email copy.12 Start with the record-level reason, then check whether the same pattern appears across the list or the sending setup.
Bounces fall into soft and hard categories.13 Soft bounces are temporary delivery problems, such as a full inbox, server error, or message size issue.14 Route temporary issues to review and give the record another decision later. Route permanent address problems to repair, suppression, or removal so the same address does not keep entering future sends.
What not to do
These mistakes turn verification into a box-ticking exercise. Keep the stop conditions visible to anyone who builds, reviews, or receives the list.
- Do not add a contact to a sequence until the email address and phone number have been verified.15
- Do not hand off a contact while its contact information is still unverified.16
- If a person is not seeing the outreach, check whether they are a new hire or whether the contact information is wrong.17
- When calls are part of the motion, an email result does not finish validation. Check whether the phone path works and whether the prospect is active on social media.18