Verification result handling

Email verification should end with a routing decision, and the policy should set that decision before a record enters an outbound sequence. A label alone does not tell you how much risk the campaign can carry. Email verification checks whether an address is correctly formatted, exists, and belongs to an active, deliverable mailbox.¹ Results may be Valid, Invalid, Spam, or Unknown.² Some checks also classify an address as risky.³ The right verification strategy depends on the task and the risk you can tolerate.⁴

Define what the result covers

Record enough context to explain the decision later. The same status can lead to different actions when checks cover different parts of an address.

Store the result with its timestamp and any documented risk indicators.⁵ Address characteristics help interpret a verification result.⁶ Email validation checks whether the format and characters follow required standards.⁷ Email verification can also identify role based and catch-all addresses.⁸

Before routing the record, identify the check that produced the status and any risk indicator that came with it. If either is missing, keep the record in review until someone can answer.

Route each result

Apply the decision policy before the address reaches the send queue. Give every status a defined outcome so the rep or workflow does not make a new judgment at send time.

Apply a decision policy to the verification result.⁹ Use these routes:

1. For Valid, allow the address into the send queue when the campaign policy accepts that level of risk. Keep the result attached to the record so later changes have context.

2. For Invalid, move the address out of the send queue and into suppression or correction. Excluding invalid addresses from sends can reduce bounce rates and improve deliverability.¹⁰

3. For Risky, hold the address for manual review, another approved check, or suppression. The policy should state which condition sends it down each path.

4. For Unknown, keep the address outside active sending until the policy gives it a clear route. Unknown is a decision state, not automatic approval.

5. For Spam, drop the address or place it in a special review queue. A FAILED spam verdict can be handled either way.¹¹

Each status should have one owner, one action, and one condition for release. That keeps uncertainty visible instead of allowing it through as a normal sendable record.

Resolve uncertain records

Use a separate resolution path for Risky and Unknown records. The goal is to find out what the status leaves unclear before exposing the address to sending.

Verification involves multiple types of checks.¹² Review the check details and address characteristics before changing the route. Ask which part of the result is uncertain, whether the address has changed since the check, and whether the record gives you a reason to contact the person through another channel first.

Set a recheck condition in the policy. A record can return to the send queue only when that condition is met, and it should return to review when the condition fails. Verify every email address before it enters the sequence, and give catch-all domains their own handling.¹³

Keep the review outcome with the original result. The next rep then has the reason for the decision and does not have to reconsider the same uncertain address from scratch.

Close the loop

Verification handling continues after the first decision. Use delivery outcomes to adjust routing rules and remove patterns that keep creating bad records.

Review bounce behavior by the data source behind the records. A practice for outbound programs calls for triple verification before sending, suppression of unverifiable catch-alls, and bounce-rate monitoring by data source.¹⁴

Reapply the policy when a status changes. If a record moves from Unknown to Valid, it should pass through the same release condition as every other Valid record. If it moves toward Invalid or Spam, remove it from active sending before the next attempt.

What not to do

• Do not treat Valid as a permanent guarantee. A valid address can fail validation and be reported as invalid.¹⁵
• Do not let a catch-all domain follow the ordinary send rule. Catch-all domains need their own handling.¹³
• Do not judge bounce performance from one blended total. Bounce rates should be watched by data source because one bad provider can damage an otherwise healthy program.¹⁴
• Do not postpone list cleaning until the next campaign. Invalid email addresses cannot be completely avoided, so lists need cleaning.¹⁶