Link Leads Blog · October 29, 2026
Most phone-type scrubs return one of two labels — landline or wireless — and treat that as the whole answer. A real batch also contains a third kind of number that doesn't sort cleanly into either bucket, and getting it wrong in either direction costs you either sends or a compliance assumption you shouldn't be making.
The standard advice on an aged list is to run a phone-type lookup before you text anything, split the file into landline and wireless, and send only to wireless — the landline-scrub walkthrough covers that workflow in full. It's the right baseline. What it leaves out is that a meaningful slice of any real list runs on Voice over IP, and VoIP doesn't fit the landline/wireless split cleanly. Depending on the lookup provider and the carrier behind the number, a VoIP line can come back labeled wireless, labeled landline, or labeled VoIP as its own category — and the label you get changes what you think you're allowed to do with the number.
VoIP routes calls and texts over an internet connection instead of a traditional phone network or a cellular radio. It shows up on an aged list in a few common forms: a cable or fiber provider's home phone bundle, a small-business VoIP line from a provider like RingCentral or Vonage, or a number ported to an app-based service. None of those are a copper landline in the old sense, and none of them are a cell phone with a SIM card in someone's pocket either — which is exactly why a lookup tool built around "is this number on a wireless carrier's network" can misclassify them in either direction.
If a phone-type check mislabels a VoIP number as wireless, you'll text it — some VoIP services can receive SMS and some can't, so a chunk of those sends still bounce the way a true landline send would, the waste covered in the landline-scrub post. That's the smaller problem. The bigger one runs the other way: agents often treat "not wireless" as "not covered by TCPA's cellular-number restrictions on autodialed and prerecorded contact," and extend that same assumption to VoIP numbers a lookup happened to label landline. That assumption doesn't reliably hold. Regulators and courts have at points treated VoIP lines as functionally equivalent to cellular service for exactly the restrictions that matter most — the ones governing autodialed calls and texts — regardless of what a line-type lookup prints on the report. A label of "landline" on a VoIP number is a data point about call routing, not a legal conclusion about which TCPA rules apply to it.
Doing this by hand — a manual VoIP lookup, a separate landline check, a separate DNC pass — doesn't scale past a few hundred numbers. A scrubber that returns phone type as more than a binary flag, in the same pass as the DNC and litigator checks, is the practical way to run this on a real batch. The one we point buyers at is Landline Remover (disclosure: that's an affiliate link, and we may earn a commission if you sign up through it) — upload the CSV and it strips landlines, disconnected numbers, and DNC-listed contacts in one pass, so you're not reconciling three separate reports before you can trust a send.
This is a practical data-hygiene guide, not legal advice. How TCPA's autodialer and prerecorded-voice restrictions apply to VoIP numbers is a genuinely unsettled area that varies by circuit, by the specific VoIP technology involved, and by how a given court has ruled on it — this post describes the practical risk, not a settled legal standard. Talk to counsel familiar with TCPA and texting compliance before you build a scrub policy around any phone-type label, VoIP included.
Link Leads' aged SMS lists ship phone-validated and 96% mobile before you run your own scrub — a head start, not a substitute for the phone-type and DNC pass above. Lists run a flat $0.012 per lead, 5,000-lead minimum ($60.00), filterable by state and age in the order builder. Grab the free 100-row sample to see the fields, or read the DNC scrubbing walkthrough next if the rest of the pipeline isn't built yet.