Wireless vs landline homeowner lists: the flag that runs the whole day

A search for “cell phone lists for homeowners” assumes there is another kind. There barely is. The federal health survey that has tracked telephone coverage since 2003 put 78.7% of US adults in wireless-only households in the second half of 2024, and among adults in homes they own or are buying — the people on a homeowner file — 74.0% were wireless-only and another 14.8% wireless-mostly. Landline only: 1.6%. Landline-mostly: 2.9%. The mobile is not a premium tier of homeowner data. It is the homeowner’s phone, and a landline on the row is the exception that needs explaining.

Which is why the wireless flag, a single yes/no column, is the most consequential field on a dialing file. It decides which rules apply to the dial, which mode of the dialer may place it, and — because a mobile reaches a person and a landline reaches a house — how often anyone answers. This page covers those three differences, how a vendor knows a number is wireless in the first place, and how to check a vendor’s flag on a sample before the floor trusts it.

Different rules

The federal consent requirement for automated calls attaches to wireless numbers: an autodialer or a prerecorded voice reaching a mobile needs prior express consent that a cold homeowner file cannot supply, and the 2021 Facebook v. Duguid decision narrowed what counts as an autodialer without narrowing the state statutes and litigation appetite that grew up around the federal one. The do-not-call registry applies to both line types; the automated-dialing consent rule is specific to wireless. None of this is legal advice, and the fuller treatment — consent-based versus cold, what a vendor’s “compliant” label can transfer, the records a claim turns on — is in TCPA-compliant homeowner leads.

What it means for the file is simple: the floor’s compliance setup routes on the flag. A blank in the column is a number the setup cannot classify, and a wrong value is worse than a blank because it will be trusted. The flag is a compliance field before it is a performance one.

Different connect behaviour

A mobile is carried by one person and answered by that person. A landline is answered by whoever is nearest to it, or by a machine, or by nobody, because the household stopped picking it up years ago and keeps it for the alarm panel. That difference is why the machine rate is the first number to read on any export. On a New Jersey solar floor’s predictive dialer, 72.7% of answered calls hit a machine over 107,574 calls in August 2026 — and that was a mobile-only file graded “strong” by the floor’s own bands on 16 of 22 days. Expect a landline-heavy file to push the machine share higher and the live-human share lower, and expect the live humans it does reach to be the wrong party more often — then measure both on a sample rather than take them from us.

Within the mobiles, activity matters as much as line type. On two 25,000-record files a Bay Area solar floor dialed between 31 August and 10 September 2026, records whose mobile showed carrier activity in five or more of the last twelve months produced 3.65 times the appointments per dial of the rest of the file. A wireless flag says the number is a mobile; an activity window says the mobile is in someone’s pocket. A file should carry both.

There is one behaviour that runs the other way. Mobile carriers label and filter inbound calls in ways landline switches never did, so a caller ID that dials mobiles hard from a bad list earns a “spam likely” tag that a landline campaign would not, and the tag follows the number, not the list. A wrong-party mobile is therefore not just a wasted dial; it is a small deposit against the floor’s caller-ID reputation. The caller-ID layer, and how to rotate and rest numbers, is in outbound dialer setup for a solar floor.

Different dialer modes

Every major dialer platform separates its modes by how the call is initiated: predictive and power modes place calls ahead of agent availability; preview and manual modes place one call because a person chose to. The wireless flag is what a floor uses to decide which mode a number may enter, according to whatever compliance basis it operates on — some floors run everything through the same predictive campaign, some route wireless rows to a manual or “cell-safe” campaign, and some hold mobiles for reps who click to dial. The point for the list is not which of those is right for your floor; it is that none of them can be configured on a file where the column is blank.

Two consequences for the file’s shape follow. Attempts have to be counted per household and not per number, or a home with a mobile in one campaign and a landline in another gets twice the cadence the floor thinks it is running. And a file that mixes line types needs the flag on every row rather than in the file name, because campaigns get merged and files get blended at import. Both are in the spec in dialer-ready lead lists.

How a vendor knows a number is wireless

There is no bit in a phone number that says mobile. The flag comes from one of three sources, and a file should say which:

1. The block. Numbers are assigned to carriers in blocks — area code plus exchange, and thousand-number blocks within them — and each block is recorded as wireless or wireline. A file of wireless blocks is published for do-not-call compliance and refreshed on a fixed schedule. Matching a number’s first six or seven digits against it is cheap and covers every number, and it is wrong for every number that has moved.
2. The ported-number files. Since number portability, a landline number can be moved to a mobile carrier and keep its digits, and a mobile number can go the other way. The intermodal ported-number files record those moves, and a flag built from the block alone without them will call a ported mobile a landline. Block plus ports is the standard compliance method, and it is what most list-broker flags are.
3. A live carrier lookup. A query against the number-routing databases that returns the current carrier and line type for that exact number, today. It costs a fraction of a cent to a few cents per number, it catches ports the files have not yet published, and it is the only method that classifies VoIP and prepaid lines with any confidence. A flag that carries a lookup date was made this way.

The failure modes are predictable from the method. A block-only flag misclassifies ported numbers. Block-plus-ports misses recent ports and calls most VoIP lines “unknown.” A live lookup is right on the day it ran and drifts after. Which is why the flag needs a date beside it, and a file older than a quarter should be re-checked rather than re-trusted — the same reasoning that puts a scrub date next to a DNC flag.

Verifying a sample

You do not need to take any of this on faith. An afternoon and a hundred rows, drawn by you and not the vendor, settle it:

1. Pull a hundred rows at random from a sample built to your real spec and geography, with the vendor’s line-type column intact.
2. Run your own lookup on the hundred numbers. Any carrier-lookup service will do; the whole batch costs less than a coffee. Record the returned line type next to the vendor’s.
3. Count the disagreements. Vendor says wireless, lookup says landline; vendor says landline, lookup says wireless; vendor blank. Each is a different failure. The first is a compliance exposure, the second is a connect-rate leak, the third is a file that made you do the work.
4. On connects, confirm it. When the file is dialed, have agents note whether they reached a mobile — the person says so, or the disposition makes it obvious — and reconcile against the flag on the row.
5. Compute the flag’s accuracy as agreements over rows. A flag that is wrong on one row in four is worse than no flag, because the floor will trust it; send the file back. A flag right on 95 or more of the hundred, with a method and a date on it, is one the compliance setup can route on.
6. Ask where the flag came from and write the answer on the order. Block, block-plus-ports, or lookup, and when.

The same sample is the one the four-test vendor audit uses for names, duplicates, disconnects and wrong parties, so run them together: how to audit a lead vendor.

Why our files carry mobiles only

Disclosure: Scout Data is our product, and the position above is the one we build to. A record, for us, is the owner on title with a live mobile — and when that owner has no reachable mobile, the row is dropped rather than filled with a landline or a relative. That is why our yields read as roughly half of a pool rather than 95%: on an 18,309-home Texas pool measured in August 2026, 79.7% of homes yielded the owner and 54.6% yielded the owner with an active mobile; the other 45.4% were not shipped. Line type comes from a live lookup with the date on the row, and a repeat order is re-verified rather than re-shipped, because on re-enriched paid orders this summer 1.4% of records went dead within six weeks.

A landline-first file is a legitimate product for a floor that wants one — the survey’s own numbers say where: adults 65 and over were 57.9% wireless-only, with 12.3% landline-mostly or landline-only, against 88% and above wireless-only for those aged 25 to 44; and the Northeast sat at 65.6% against 81.4% in the South. If that is your market, buy for it, and hold the flag to the same standard. For every other homeowner floor, the file to buy is the one whose wireless column you have checked, and the rest of what that file has to carry is in homeowner phone lists for call centers and, field by field, in anatomy of a dialer-ready record.

Telephone-coverage figures are from the National Health Interview Survey’s wireless-substitution early release for July–December 2024, published June 2025. Dialer and yield figures are from our benchmarks page, each with its sample and month.

Frequently asked questions