Lead email deliverability check

Purpose

Assess whether the email addresses in a lead list are usable and whether their identity and company association are coherent. Produce a reviewable status, never a false guarantee of delivery.

Scope

Syntax, duplicates, domain format, role-to-domain consistency, verification results already present in the corpus, and evidence age.

Excluded: sending test messages, contacting the domain, suppressing records in an external system, and guaranteeing inbox placement.

Data basis

• Lead table with email, person, company and source columns.
• Existing verification results and timestamps.
• Company and domain reference data in scope.

Result

A row-level deliverability assessment with reasons and a list of records requiring verification or correction.

Quality criteria

• Every row receives exactly one status.
• Invalid syntax is separated from unknown verification state.
• Statuses are based only on available evidence and defined rules.
• Duplicate addresses and domain mismatches are cited by row.
• No address is changed without retaining its original value.

Instructions

Use the company's status vocabulary and evidence-age rule. Treat a valid-looking address as syntactically valid only; do not call it deliverable without a verification result. Handle role addresses and free-mail domains according to the adaptation rules. Preserve privacy by displaying only the minimum address detail needed for review.

Adapt before use

Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

• Map the lead columns and define the output status vocabulary.
• Set the acceptable age of a verification result.
• Define treatment of role addresses, free-mail domains, and suppression states.