Recommended Approach for Using Experian Email and Phone Validation Results

Kumar, Gargi

Purpose

This article provides a recommended approach for interpreting Experian Email and Phone Validation results and converting them into practical downstream actions. The goal is to help teams decide whether a contact point should be accepted, rejected, corrected, retested, or manually reviewed.

Experian’s validation outputs should not be treated as a single universal pass/fail outcome. The correct action depends on the validation result, the confidence level, the communication channel, and the business context. For example, a result that may be acceptable for a low-risk marketing campaign may be unsuitable for healthcare, financial, identity, or safety-critical communications.

The source material confirms that email validation is performed first at syntax level and then through real-time mailbox-level validation. The output includes validation result, verbose result, and, where available, a suggested correction. It also notes that suggested corrections should be used at the client’s discretion because they may not always be the correct email to use going forward.  The confidence-level guidance also states that email and phone validation responses are real-time checks and can change depending on the email provider, mailbox state, phone network, or telco response at the time of query.

Recommended Output Columns

The validation file should retain the original Experian outputs and add recommendation fields for business use. The recommendation should be appended, not used to overwrite the raw validation result.

Column	Purpose
EDQ Email Validation Result	Original Experian email result, such as Verified, Undeliverable, Unknown, Disposable, or Illegitimate.
EDQ Email Verbose Result	More detailed reason, such as mailboxFull, acceptAll, syntaxFailure, roleAccount, timeout, or typoDomain.
EDQ Email Correction	Suggested email correction, where Experian provides one.
EDQ Email Recommendation	New derived column indicating the recommended action.
EDQ Phone Type	Phone type, such as Mobile, Landline, VoIP, Toll free, Premium, or Unknown.
EDQ Phone Validation Status	Phone validation confidence or status, such as Live, Dead, Absent Subscriber, No Coverage, or Inconclusive.
EDQ Phone Recommendation	Derived action for phone use.
EDQ Contact Recommendation	Overall preferred contact action across available channels.
EDQ Recommendation Rationale	Plain-English reason for the recommendation.
EDQ Industry Policy Applied	Indicates whether the recommendation was based on Healthcare, Marketing, Financial Services, Government, Retail, or another policy profile.

Recommended Email Recommendation Column

The following table extends the same concept used in the phone recommendation guidance by adding a recommended action for email results.

Email Validation Result	Verbose Result Examples	Baseline Recommendation	Suggested Handling
Verified	verified	Accept	Use the email address for normal communications, subject to consent and business rules.
Undeliverable	mailboxDoesNotExist, mailboxDisabled, syntaxFailure	Reject	Suppress from email use. Request an updated email address through another channel.
Undeliverable	mailboxFull	Retest / Conditional Accept	Treat as potentially temporary. Retest before rejecting permanently, especially for non-critical communications.
Unreachable	unreachable	Retest / Review	Do not rely on the email for critical communications. Retest later or use an alternate channel.
Illegitimate	illegitimate, localPartSpamTrap, profanity	Reject	Suppress from campaigns and customer communications. Investigate source quality if volume is material.
Illegitimate	roleAccount	Industry Dependent	Accept only where a shared mailbox is appropriate, such as some B2B or support use cases. Reject or review for personal, healthcare, financial, or identity-related use cases.
Illegitimate	typoDomain	Correct and Retest	Use the suggested correction only after retesting and confirming the corrected email validates appropriately.
Disposable	disposable	Reject	Do not use for ongoing customer communications, account verification, or regulated communications.
Unknown	unknown, timeout, relayDenied, blank	Retest / Conditional Accept	Use only where business risk is low. Retest before critical use. Monitor bounce and engagement results.
Unknown	acceptAll	Conditional Accept	The domain accepts all emails, so mailbox-level confirmation is not conclusive. Accept for low-risk marketing only; do not rely on it for critical notifications.

Recommendation Values

Use a controlled list of recommendation values so the output is consistent and easy to operationalise.

Recommendation	Meaning	Typical Downstream Action
Accept	Result is suitable for the intended use case.	Use the email or phone number.
Conditional Accept	Result is not fully confirmed but may be usable for low-risk purposes.	Use with controls, such as bounce monitoring, consent checks, and fallback channel.
Retest	Result may be temporary or inconclusive.	Revalidate before using, especially if the record is valuable or the communication is important.
Correct and Retest	A suggested correction exists but should not be trusted automatically.	Apply the correction to a separate field, retest, and only promote if verified.
Review	Human or business-rule review is required.	Send to data stewardship, contact centre, CRM queue, or operational review.
Reject	Result is unsuitable for the intended use case.	Suppress from the relevant channel and request updated details.

Handling Experian Confidence Levels

Experian validation confidence should be interpreted as a contactability indicator, not as proof of customer identity or permission to contact. The confidence level should be combined with consent, purpose of communication, channel, customer value, and industry risk.

The source guidance for phone validation includes a recommendation table where some results are clearly accepted or rejected, while others vary by context. It also explicitly states that the table should be used as a guide and that the best approach should be confirmed with the client for each response type and confidence level.

Suggested Confidence Handling Framework

Confidence Category	Email Examples	Phone Examples	Recommended Approach
High confidence contactable	Verified	Live, Verified Mobile	Accept for the approved use case.
Temporary or inconclusive	mailboxFull, timeout, unknown, acceptAll, relayDenied	Absent Subscriber, Unknown, Inconclusive, No Coverage	Retest, conditionally accept, or route to alternate channel depending on risk.
Hard failure	mailboxDoesNotExist, mailboxDisabled, syntaxFailure	Dead, Bad Format, No Teleservice Provisioned	Reject for that channel and request updated details.
Risk indicator	spamtrap, disposable, profanity, illegitimate	Premium, Shared Cost, Pager, Voicemail Only, Stage and Screen	Reject or review depending on policy. Usually suppress from automated use.
Context-dependent	roleAccount, acceptAll	Landline, VoIP, Personal Number, Mobile or Landline	Apply industry and use-case rules before deciding.

Phone Recommendation Summary

The phone validation article provides a useful baseline for handling common phone confidence outcomes. Mobile numbers with Verified or Absent outcomes are generally recommended as Accept, while Dead, No Teleservice Provisioned, Bad Format, Premium, Toll Free, Shared Cost, Pager, and Voicemail Only outcomes are generally recommended as Reject. Some outcomes, such as Landline, VoIP, Personal Number, and Mobile or Landline, are marked as Varies and should be assessed against the intended use case.

Phone Type / Status	Baseline Recommendation	Suggested Handling
Mobile / Verified or Live	Accept	Suitable for SMS or call use, subject to consent and communication purpose.
Mobile / Absent Subscriber	Accept or Conditional Accept	May be acceptable for marketing or low-risk contact; retest for critical communications.
Mobile / Unknown	Conditional Accept	Use for lower-risk use cases only; monitor failures and retest periodically.
Mobile / Dead	Reject	Suppress from phone use and request updated number.
No Teleservice Provisioned	Reject	Do not use for calls or SMS.
No Coverage	Industry Dependent	Retest or use alternate channel. Reject for high-risk use cases.
Inconclusive	Review / Retest	Do not rely on for critical communications.
Landline	Varies	Accept for voice calls if appropriate; reject for SMS-only use cases.
VoIP	Varies	May be acceptable for service calls, but review for identity, OTP, or regulated use cases.
Premium, Shared Cost, Toll Free	Reject	Usually unsuitable for customer contact records.
Bad Format	Reject	Standardise, correct if possible, then retest.

Industry-Specific Recommendation Policy

The same Experian result can lead to different recommendations depending on industry and communication purpose. The recommendation column should therefore be generated using a policy profile.

Industry / Use Case	Recommended Strictness	Email Handling	Phone Handling
Healthcare – clinical, appointment, patient safety, care instructions	High	Accept Verified only. Reject or manually confirm Unknown, Disposable, Illegitimate, Role Account, Undeliverable, and Unreachable before use.	Accept Live or Verified mobile only for critical communication. Review or confirm Absent, Unknown, Inconclusive, No Coverage, VoIP, and Landline depending on channel.
Healthcare – general engagement or wellness campaign	Medium	Accept Verified. Conditional Accept for acceptAll or timeout only where consent exists and the message is low-risk. Reject Disposable, Spamtrap, Illegitimate, and Undeliverable.	Accept Verified or Live mobile. Conditional Accept for Absent or Unknown if campaign risk is low.
Marketing / Retail campaigns	Low to Medium	Accept Verified. Conditional Accept for Unknown, acceptAll, mailboxFull, or timeout with bounce monitoring. Reject Disposable, Spamtrap, Profanity, and mailboxDoesNotExist.	Accept Verified, Live, Absent, and sometimes Unknown mobile numbers where consent exists. Reject Dead, Bad Format, Premium, Shared Cost, and No Teleservice.
Financial Services / Insurance	High	Accept Verified for regulated, transactional, or account-related messages. Review or reject Unknown, acceptAll, Role Account, Disposable, and Illegitimate.	Accept Verified or Live mobile for customer contact. Retest or confirm uncertain results before OTP, collections, claims, or regulatory notices.
Government / Utilities	Medium to High	Accept Verified for service notices. Retest or review inconclusive results. Use postal or call-centre fallback for important notices.	Accept Verified or Live mobile. Treat No Coverage, Unknown, VoIP, and Landline according to the communication channel and obligation.
B2B / SaaS	Medium	Accept Verified. Role accounts may be acceptable for support, procurement, or general enquiry use cases. Reject Disposable and spamtrap indicators.	Accept verified direct numbers. Review shared, VoIP, or generic numbers depending on sales, support, or billing use case.

Example: Same Result, Different Recommendation

Validation Scenario	Healthcare Recommendation	Marketing Recommendation
Email result is Unknown / acceptAll	Reject for clinical or patient safety communication. Use alternate channel or confirm with patient.	Conditional Accept if consent exists. Send with bounce monitoring and fallback rules.
Email result is mailboxFull	Retest or confirm before sending important information. Do not rely on it for critical communication.	Conditional Accept or Retest. May remain in campaign audience temporarily.
Email result is roleAccount	Reject or Review for patient-specific communication because it may not identify an individual recipient.	Accept for B2B marketing or general business contact if appropriate.
Phone result is Mobile / Absent Subscriber	Review or Retest before critical communication. Use alternate channel if needed.	Accept or Conditional Accept for low-risk campaign use.
Phone type is VoIP / Verified	Review for identity, OTP, or regulated use cases.	Accept for general contact or service follow-up if appropriate.
Email result is Disposable	Reject.	Reject.
Phone result is Dead	Reject.	Reject.

Recommended Contact-Level Decisioning

The best output is not only an email recommendation or phone recommendation, but an overall contact recommendation.

Email Recommendation	Phone Recommendation	Contact Recommendation
Accept	Accept	Use preferred channel based on consent and communication type.
Accept	Reject	Use email; request updated phone number.
Reject	Accept	Use phone; request updated email address.
Conditional Accept	Accept	Prefer phone for important communication; email may be used for low-risk messages.
Accept	Conditional Accept	Prefer email for important communication; phone may be used with controls.
Retest / Review	Retest / Review	Hold from critical campaigns and route to data quality review.
Reject	Reject	Suppress from automated contact and trigger data capture or remediation process.

Practical Rules for Applying Suggested Email Corrections

Suggested corrections should be handled carefully because the source guidance states that a correction may not always be the correct email to use going forward.

Recommended approach:

Scenario	Suggested Action
Suggested correction exists and corrected email validates as Verified	Accept corrected email, but retain original value for audit.
Suggested correction exists but corrected email is Unknown or Unreachable	Do not automatically replace. Retest or review.
Suggested correction changes the domain materially	Review before updating, especially in healthcare, finance, government, or regulated use cases.
Suggested correction applies to obvious common typo, such as a known mailbox provider typo	Correct and retest before use.
No correction exists and result is Undeliverable or Syntax Failure	Reject or request updated email.

Recommended Governance Approach

To make recommendations reliable and auditable:

Governance Step	Recommendation
Preserve raw results	Keep Experian validation result, verbose result, confidence, and correction fields unchanged.
Add derived recommendation fields	Append recommendation columns rather than overwriting source data.
Apply industry policy	Use different rules for Healthcare, Marketing, Financial Services, Government, B2B, and Retail where required.
Retest uncertain records	Retest Unknown, timeout, mailboxFull, relayDenied, Inconclusive, and No Coverage results before important use.
Monitor outcomes	Track bounces, SMS failures, call failures, complaints, and unsubscribe rates.
Confirm client rules	Agree which results should be accepted, rejected, or reviewed before operationalising the output.
Avoid permanent suppression for temporary states	Results such as mailboxFull, timeout, Absent Subscriber, or No Coverage may change over time.
Separate contactability from consent	A valid contact point does not mean the organisation has permission to use it.

Suggested Default Recommendation Logic

The following default logic can be used as a starting point.

Result Type	Default Recommendation
Email Verified	Accept
Email Undeliverable due to mailboxDoesNotExist, mailboxDisabled, or syntaxFailure	Reject
Email Undeliverable due to mailboxFull	Retest
Email Unreachable	Retest / Review
Email Disposable	Reject
Email Illegitimate due to spamtrap, profanity, inactive domain, or black hole	Reject
Email Illegitimate due to roleAccount	Industry Dependent
Email Unknown due to timeout, acceptAll, relayDenied, or blank	Conditional Accept for low-risk use; Retest or Reject for high-risk use
Phone Mobile Verified / Live	Accept
Phone Mobile Dead	Reject
Phone Mobile Absent	Accept for low-risk use; Review for high-risk use
Phone Unknown	Conditional Accept or Review
Phone No Teleservice Provisioned	Reject
Phone No Coverage	Industry Dependent
Phone Landline / VoIP / Personal Number	Varies by use case
Phone Premium / Shared Cost / Toll Free / Pager / Voicemail Only	Reject

Assumptions, Risks, and Open Questions

Category	Notes
Assumptions	The organisation has already captured consent and lawful basis for the intended communication. Validation results are being used for contactability and data quality decisioning, not identity verification.
Risks	Real-time validation results can change. Overly strict rules may remove usable contacts. Overly permissive rules may increase bounce rates, failed messages, privacy risk, or poor customer experience.
Missing Evidence	The final recommendation rules should be confirmed against the client’s industry, communication purpose, consent model, risk appetite, and channel strategy.
Questions to Confirm	Which communications are critical versus promotional? Which industries or business units need stricter rules? Should Unknown be accepted, retested, or rejected? How should corrected emails be approved? What retention and audit requirements apply?

Recommended Position

Use Experian validation confidence levels as a decision-support input, not a universal pass/fail rule. Create an EDQ Email Recommendation column and align it with the existing phone recommendation approach. Apply a default recommendation first, then adjust it using an industry policy overlay.

For healthcare, financial services, government, and other high-risk use cases, use a stricter model: accept only high-confidence contact points and route uncertain results to review or confirmation. For marketing and retail campaigns, use a more flexible model: accept verified contacts, conditionally accept some uncertain results, and suppress clear risk or failure indicators.