What bad numbers actually cost a sales team
Bad numbers are usually discussed as a data-hygiene chore. For an outbound team they show up in four places at once.
- Rep time. Each dead number still takes a dial, a ring or an error tone, and a disposition.
- Connect rate you can't trust. Dead numbers sit in the denominator. A team dialing a dirty list looks worse than it is, and nobody can tell if the opener or the data is the problem. See connect rate.
- Caller ID reputation. Analytics engines grade how often your calls are answered and how long they last. Hiya names old or low-consent lists as a cause of poor "connection" grades, and lists of bad numbers produce exactly the unanswered, very short calls that lead to Spam Likely labels.
- Compliance exposure. A reassigned number reaches a stranger who never agreed to hear from you. The FCC built a database specifically to help callers avoid that (more below).
A worked example
Illustrative assumptions, not benchmarks: a team of five reps each dials 300 numbers a day, and 15% of the list is dead, disconnected or reassigned. That is 225 wasted dials a day, or about 4,500 over a 20-day month. If each dead dial costs only 20 seconds of ringing, error tone and disposition, that is 25 rep-hours a month spent on numbers that could never connect, before counting what those calls do to your caller IDs. Put in your own numbers; the point is that small percentages compound across a team.
Morale is the cost that never makes the spreadsheet. A rep who hits three disconnected tones in a row starts the next call expecting failure, and it shows in the opener.
The checks that exist, and what each one can't tell you
"Phone verification" gets used for everything from a regex to a one-time passcode. For prospecting, these are the checks that matter, from cheapest to hardest.
| Check | What it tells you | What it can't tell you | Where it comes from |
|---|---|---|---|
| Format | The number has a valid country code, area code and length, stored consistently (E.164, like +14155550123) | Whether the number is in service | CRM validation rules, any lookup API |
| Line type | Mobile, landline, fixed VoIP, non-fixed VoIP (such as Google Voice), toll-free and more | Whether the line is live or whose it is | Carrier and numbering data, such as Twilio Lookup's line type field |
| Carrier | Which network currently serves the number, after porting | Whether your prospect is the subscriber | Carrier lookup services |
| Active or disconnected | Whether the number is assigned and in service on the network | Coverage is uneven; some networks return "unknown" | Carrier network queries, such as Twilio's Line Status (public beta, mobile numbers) |
| Reassigned | Whether the number was permanently disconnected after a date you give (for example, when you got consent) | Who has the number now | The FCC's Reassigned Numbers Database (paid subscription) |
| Ownership | Whether the number belongs to the named prospect at the named company | Nothing is perfect here; it is a confidence level | Your data provider's matching, prior conversations, rep confirmation on the call |
| Do not call or opt-out | Whether this person asked not to be called, or is on a list you must honor | Whether the call is otherwise lawful | Your own opt-out list, the National Do Not Call Registry where it applies |
Twilio's own documentation is a useful honesty check on the active-or-disconnected question: it lists five possible answers (active, reachable, unreachable, inactive, unknown), says the check "might not return data for some networks", and notes that "active" does not mean reachable. Any vendor that promises a certain answer for every number is rounding.
Valid is not right: the five states of a phone number
Most validation advice stops at "is it working". For a rep, the useful question is what happens when you dial it. Every number on a list is in one of five states, and each needs a different fix.
| State | What the rep hears | How you catch it | What to do |
|---|---|---|---|
| 1. Invalid | Nothing; the dialer errors | Format check on import | Fix or drop at import |
| 2. Dead | A disconnected tone or a carrier message | Active or disconnected check before dialing | Remove from the phone field; find a new number |
| 3. Live, wrong person | "Sorry, there's no one here by that name" | Reassigned check, ownership matching, the rep's disposition | Disposition as wrong number and clear the field |
| 4. Live, right company, not the person | A receptionist, switchboard or main line | Line type and field labels (HQ versus direct) | Move to a company phone field; keep it out of parallel dialing |
| 5. Live, right person | Your prospect, or their voicemail or call screener | Only the call itself confirms it | Mark the number as verified with the date |
States 3 and 4 are where most teams leak. Orum's help center, for example, advises keeping HQ lines out of direct-dial and mobile fields, because in parallel dialing a list with one receptionist line in five means reps keep getting bridged to switchboards. That advice holds for any dialer.
What to say when you reach the wrong person
Rep:Hi, this is Sam from Northwind. I'm trying to reach Dana Ruiz at Acme. Have I got the right number?
Prospect:No, there's no Dana here.
Rep:Sorry about that, I'll take this number off our list today. Just so I fix it properly, is this a business line or a personal one?
Prospect:It's my cell.
Rep:Got it, it's removed. Thanks, and have a good day.
Then actually remove it: disposition "wrong number", clear the field, and tag the data source so you can see which provider is sending you reassigned numbers.
When to validate: at import, before dialing, after every call
A list that was clean in January is not clean in April. Under FCC rules, carriers report permanently disconnected numbers to the Reassigned Numbers Database every month and must wait at least 45 days before giving a disconnected number to someone new, per the FCC. So the window between "disconnected" and "belongs to a stranger" is short, and validation has to repeat.
- On importRun format and line-type checks on every number entering the CRM, from any source. Standardize to one format, put each number in the right field (direct dial, mobile, company), and reject what fails. This is cheap and catches state 1.
- Before each call blockCheck that the numbers about to be dialed are active. This is the check that catches state 2, and it matters most for lists that sat unused for weeks. Ideally it happens inside the dialer, so reps never see a dead number.
- Before calling consented numbers, check for reassignmentIf your calls rely on prior consent (common for inbound leads and customer lists), query the Reassigned Numbers Database with the date consent was given. It answers yes, no or no data.
- After every callMake dispositions do the work: wrong number, disconnected, company line and verified-direct each update the record automatically. Over a quarter this is the cheapest validation you have.
- MonthlyReport bad-number rates by data source and push the worst source to fix or refund. If one provider sends twice the wrong numbers of another, that is a buying decision.
Build it into the SDR workflow
Validation fails when it is a quarterly project owned by nobody. Make it part of the plumbing.
1. Give every number a home
Use separate CRM fields for direct dial, mobile and company phone, plus two helper fields: where the number came from and the date it was last verified by a live conversation. Reps should dial a clearly labeled primary number, not guess between four.
2. Make dispositions specific
| Disposition | Automatic action |
|---|---|
| Disconnected | Clear the number field; flag the contact for re-enrichment |
| Wrong number | Clear the field; tag the data source; never redial that number for this contact |
| Company line / gatekeeper | Move the number to the company phone field; exclude from parallel dialing |
| Connected: right person | Set "last verified" to today |
| Asked not to be called | Add to your internal do-not-call list across every number and channel |
3. Close the loop with your data vendors
Wrong-number and disconnected rates by source are the only honest test of a data provider's phone quality. Share the report with them and ask whether they credit bad records; how they answer tells you something too. For the list-building side, see how to build a cold call list.
4. Know the compliance line
The FCC says callers can lower their TCPA risk by checking the Reassigned Numbers Database, and offers a safe harbor when the database wrongly says a number was not reassigned and the caller had consent. The FTC says most business-to-business calls are exempt from its Telemarketing Sales Rule, with exceptions, but that does not cover a work contact's personal cell, and the TCPA is a separate set of rules. This is general information, not legal advice; check with counsel for your call types.
Frequently asked questions
What is the difference between phone number validation and verification?
Teams use the words loosely. In sales, validation usually means checking the number itself (format, line type, carrier, active or disconnected), and verification means confirming it belongs to the right person, either through a data provider's matching or a live conversation. You need both.
How can I tell if a phone number is disconnected without calling it?
Use a carrier lookup that reports line status, or a dialer that checks the number with the carrier before dialing. Results are strongest for mobile numbers, and some networks return "unknown", so treat it as a strong signal rather than a certainty.
How accurate is phone number validation?
It depends on the check and the network. Format and line type are reliable. Active status depends on carrier coverage, and Twilio, for example, notes its line status check may not return data for some networks. No check confirms ownership; only a conversation does.
How often should a sales team re-validate phone numbers?
Check format and line type once at import, check active status before every call block, and let dispositions update records after every call. Carriers report disconnected numbers monthly and can reassign them after 45 days, so a list unused for a month or more needs a fresh check.
Do B2B sales teams need the Reassigned Numbers Database?
It matters most when your calls rely on prior consent, such as inbound leads or customer lists, and when you call mobile numbers. It is a paid subscription. Whether you need it is a legal question for your call types, and this is not legal advice.
Does validating numbers increase connect rate?
It raises connects per dial, because dead numbers leave the denominator, and it gives reps back the time they spent on them. Over time it can also help caller ID reputation by cutting unanswered calls. It does not make prospects answer; that is timing, reputation and the call itself.
- 1.FCC, Reassigned Numbers Database (2025)
- 2.Reassigned Numbers Database Administrator, Frequently Asked Questions
- 3.Twilio, Lookup: Line Type Intelligence
- 4.Twilio, Lookup: Line Status (public beta)
- 5.Hiya, Caller reputation and spam label help (2026)
- 6.Orum Help Center, Understanding Bridged: Connect Ratios (2025)
- 7.FTC, Complying with the Telemarketing Sales Rule
Spend your reps' day on conversations, not ringing phones.
TwinsAI parallel-dials up to 8 lines at once, validates every number with the carrier before it rings, and bridges a live prospect to your rep in under 450ms. It works inside HubSpot, Salesforce, Close, Attio, Outreach, Zoho and HighLevel, with no seat minimum.