Number Validation Labels

Complete user-facing reference — every label, what it means, and how it's calculated

Last updated: May 22, 2026 · Plain-English companion to the Validation Pipeline doc

When a user uploads or pastes numbers in the campaign wizard, our system runs them through two analyses and tags each one with two badge types: a Line Type badge (what kind of phone) and an Eligibility badge (how likely the drop will land). The labels below are exactly what customers see on the validation screen.

Label 1 — Line Type Badges

Identifies what kind of phone line this is. Pulled from carrier lookup (Telnyx/Twilio).

BadgeMeaningRVM Compatibility
MobileCell phone on a wireless carrier (Verizon, AT&T, T-Mobile, etc.)✅ Ideal — virtually all mobiles have voicemail. Highest delivery probability.
VoIPInternet-based phone (Google Voice, RingCentral, Vonage, Bandwidth, etc.)⚠️ Unreliable — VM behavior varies by provider; results can change between lookups.
LandlineTraditional wired residential or business phone⚠️ Variable — only works if carrier voicemail is enabled. Often skipped by RVM.
UnknownCarrier lookup didn't return a definitive line type❓ Treat as risky — test with a small batch first.

Label 2 — Eligibility Badges

Predicts whether Drop Cowboy will successfully deposit a voicemail. Based on score + delivery history.

ProvenScore ≥ 80

We've successfully delivered a voicemail to this exact number recently.

Triggered When

  • ≥1 successful delivery in the last 30 days
  • Score ≥ 80
  • Lifetime success rate ≥ 50%

Recommended Action

Send with full confidence.

Sendable / Ready to SendScore 60 – 79

Strong signals say this will deliver. Typically a clean mobile with no negative history.

Triggered When

  • Mobile line type confirmed
  • No prior failures or carrier flags
  • Or a previously-proven number that aged past 30 days but still scores well

Recommended Action

Good to send. Default state for clean mobiles.

Watchlist / Test FirstScore 35 – 59

Reachable but uncertain. Often VoIP, landline, mixed history, or stale 'Proven' that decayed.

Triggered When

  • VoIP or landline line type
  • Mixed success/failure history
  • Older successes only (no activity in last 30 days)

Recommended Action

Include with caution. Worth monitoring after the first run.

Blocked / Do Not SendScore < 35

Strong signals say this will fail. Automatically excluded from campaigns.

Triggered When

  • Carrier reported bounce / disconnected / invalid
  • IVR or gatekeeper detected
  • 3+ failures with zero successes
  • Known-bad voicemail

Recommended Action

Excluded automatically. Do not retry without manual review.

Roll-up Counters Shown to the User

The four big numbers at the top of the validation screen group eligibility into action buckets:

Checked

Total numbers validated

Ready to Send

Proven + Sendable

Uncertain

Watchlist (Test First)

Do Not Send

Blocked

Footer note shown to users: "Eligibility based on line type + Drop Cowboy delivery history. 'Test First' numbers are included but may have uncertain compatibility."

How the 0–100 Score is Built

Every signal that raises or lowers the score. Final score is clamped 0–100, then mapped to an eligibility badge.

SignalImpact
Valid format + not on suppression list(Base score)+40
Mobile line type+40
VoIP line type+5
Landline line type+0
Unknown line type+5
Prior successful delivery to this exact number+40
Confirmed working voicemail+10
Strong prefix history (≥70% success across NPA-NXX, 5+ attempts)+15
Each prior failure (when no successes recorded)(Capped at 3 failures (max −45))−15
Known-bad voicemail flag−40
Carrier flag: IVR / gatekeeper detected−50
Carrier flag: voicemail unavailable / mailbox full−40
Carrier flag: number disconnected / invalid (bounce)−60
Carrier flag: spam-filtered / blocked−30
Weak prefix history (≤20% success across NPA-NXX, 5+ attempts)−20

The 30-Day Freshness Rule

"Proven" status expires after 30 days. If a number was successful months ago but has been failing recently (or has had no activity), it automatically demotes to "Sendable", "Watchlist", or "Blocked" based on its current score. This prevents stale labels from misleading customers into trusting numbers that no longer deliver.

Eligibility is re-evaluated on every delivery webhook (functions/dropCowboyWebhook) using the exact same scoring model as the wizard (functions/scoreNumberEligibility), so labels always stay honest and consistent.

Probability, Not Guarantee

Labels reflect the likelihood of delivery based on the signals available at check time. The only way to confirm a voicemail was actually deposited is to send one and receive a success callback from Drop Cowboy. Even "Proven" numbers can fail (e.g. voicemail turned off, number ported).

Source Code References

Bulk Validation Lookup

functions/lookupNumbers

Wizard-Time Scoring

functions/scoreNumberEligibility

Eligibility Re-computation

functions/dropCowboyWebhook

UI Badge Definitions

components/shared/ValidationStatusBadge

DropDialer™ Validation Labels Reference · For internal use and customer-facing help docs