Phone Confidence Score Property
Quantify phone number quality with a single, actionable score
Overview
Section titled “Overview”Clean Dial’s Phone Confidence Score property provides a 0-100 integer score that summarizes the overall quality and reachability of a contact’s phone number. Instead of interpreting multiple fields (status, carrier, line type, etc.), you get one number that’s easy to use in workflow conditions, lists, and reports.
How It Works
Section titled “How It Works”When contacts pass through a Clean Dial HLR Lookup workflow action, the system:
- Performs the HLR lookup and collects all available data points
- Calculates a weighted score based on multiple factors
- Updates the Phone Confidence Score property on the contact record
Scoring Breakdown
Section titled “Scoring Breakdown”The confidence score is calculated from these factors:
| Factor | Max Points | Description |
|---|---|---|
| Live Status | 40 | LIVE=40, ABSENT_SUBSCRIBER=25, NO_COVERAGE=15, etc. |
| Line Type | 20 | MOBILE=20, LANDLINE=18, VOIP=12, etc. |
| Carrier Info | 15 | Has known carrier = 15 points |
| Not Disposable | 10 | Non-disposable number = 10 points |
| Ported Status | 10 | Not ported = 10, Ported = 5 |
| Syntax Valid | 5 | Valid phone format = 5 points |
Example Scores
Section titled “Example Scores”| Scenario | Score |
|---|---|
| LIVE mobile, known carrier, not ported, not disposable | 100 |
| LIVE landline, known carrier, not ported | 98 |
| ABSENT_SUBSCRIBER mobile, known carrier | 75 |
| DEAD number with carrier info | ~30 |
| Invalid/unparseable format | 0 |
When the Score is Blank
Section titled “When the Score is Blank”The confidence score will be blank/empty (not zero) when the HLR lookup fails due to:
- API timeouts
- Rate limiting
- Server errors
- Authentication issues
This means “we don’t know” - the lookup didn’t complete. A score of 0 means “we checked and it’s bad.”
Setting Up the Custom Property
Section titled “Setting Up the Custom Property”To view the confidence score on your contact records:
- Navigate to CRM > Contacts
- Select any contact record
- Go to the Key Information section
- Click Actions > Customize Properties
- Search for “Phone Confidence Score”
- Add the property to your view
Recommended Actions by Score
Section titled “Recommended Actions by Score”Use these guidelines to build tiered routing logic in your workflows:
| Score Range | Quality | Recommended Actions |
|---|---|---|
| 90-100 | Excellent | Priority queue for sales calls. Safe for SMS campaigns. High-value lead routing. |
| 70-89 | Good | Standard outreach. SMS with fallback to email. Normal sales queue. |
| 50-69 | Medium | Email-first approach. Verify before calling. Consider re-validation in 30 days. |
| 30-49 | Low | Email only. Flag for data enrichment. Do not use for paid SMS. |
| 1-29 | Poor | Suppress from campaigns. Request updated contact info. Review before any outreach. |
| 0 | Invalid | Remove from active lists. Do not attempt contact. Mark for cleanup. |
Understanding Score Components
Section titled “Understanding Score Components”A score isn’t just “good or bad” - understanding why a number scored the way it did helps you take smarter action:
-
High score (90+) but VOIP line type? The number is technically reachable, but may be a virtual number. Consider email verification first for high-value transactions.
-
Medium score (50-69) with ABSENT_SUBSCRIBER status? The number is valid but the device is off or out of coverage. Worth retrying in 24-48 hours rather than removing.
-
Low score (30-49) but LIVE status? Likely a disposable or ported number. The person is reachable, but may be using a temporary number - proceed with caution for sensitive communications.
-
Score of 0? The number failed parsing or HLR returned BAD_FORMAT. This is confirmed invalid data - safe to remove.
Use Cases
Section titled “Use Cases”Tiered Lead Routing
IF confidence_score >= 80 → Route to priority sales queueIF confidence_score 50-79 → Route to standard queue, send email firstIF confidence_score < 50 → Marketing nurture only, no direct outreachSMS Campaign Protection
Only include contacts where confidence_score >= 70 AND phone_line_type = MOBILE to maximize delivery rates and minimize wasted spend.
Fraud Prevention
Flag new signups where confidence_score < 50 OR phone_is_disposable = true for manual review before activating accounts.
Data Quality Reporting Track average confidence scores by lead source to identify which channels provide the cleanest phone data. Sources consistently below 60 may need validation at point of capture.
Re-engagement Campaigns
For contacts with confidence_score between 50-69 and hlr_status = ABSENT_SUBSCRIBER, create a delayed retry workflow that re-checks after 48 hours before suppressing.
Technical Details
Section titled “Technical Details”- Property Name:
phone_confidence_score - Property Type: Number
- Scope: Contact records
- Range: 0-100
- Updates: Automatic via HLR Lookup action