Line Type Lookup for Lead Forms: Stop Paying for Fake Numbers

A line type lookup checks every phone number your lead form collects against carrier records and tells you, before anyone dials, whether the number is real, whether it is a mobile, a landline or a VoIP line, and which carrier serves it. Run at the moment the form is submitted or before a lead is paid for, it removes the disposable numbers that fraud and incentive abuse run on, stops your team texting landlines, and tells you which numbers are cell phones for consent purposes. The check takes about a second per number, and the rules you build on top of it are where the value is.

What form validation misses

Most lead forms already validate the phone field, and most of that validation is cosmetic. It confirms the number has ten digits and a plausible area code, which rules out typing mistakes and nothing else. The numbers that cost money pass it easily.

A number can be correctly formatted and unassigned, so the call goes to a recording and the lead is worthless. It can be a non-fixed VoIP number created two minutes earlier to collect a coupon, a gift card or an affiliate payout, and abandoned two minutes later. It can be a landline typed into a "mobile" field by someone who will never see the follow-up text you send. It can be a toll-free number pasted in by a bot. It can be the same cell phone entered a third time this week in a different format. None of that is visible in the digits, and all of it is visible in the carrier records.

Form validation also cannot see who is behind a pattern. One VoIP number in a day of leads is a customer with a second line. Thirty VoIP numbers on the same wholesale carrier in an hour, all from a single traffic source, are a publisher gaming your payout, and the sooner that shows up in your data, the less it costs. The article on phone carrier lookups explains what the carrier field means and why app-based numbers all tend to share a few wholesale names.

Where to run the check

There are three sensible points, and many teams use two of them.

The first is at submission. The form calls a lookup as the lead is submitted and either accepts the number, asks the visitor to confirm it or asks for a different one. This is the only point at which you can still get a better number from the person, which makes it the most valuable position for the check. It also adds a second of latency to the form and spends a lookup on every submission, including the junk ones, so it belongs behind a format check and a rate limit rather than in front of them.

The second is before purchase or before dialing. Leads that arrive from partners or from forms you do not control are checked when they enter your system, and the result is written next to the lead. Nothing is rejected at this point; the number is scored, routed and, if necessary, held for review. This is where most pay-per-lead buyers put the check, because it gives them a documented reason to return a lead.

The third is on the call itself, for businesses that take inbound calls rather than form fills. The caller's number arrives with the call, and a lookup at ring time decides whether the call is answered, challenged or routed somewhere else. The last section covers that case.

Whichever point you choose, store the result with the lead. A line type that was checked once and written down is free to query forever, and the history is what lets you see a publisher's quality change over a month instead of over a quarter.

What to do with each result

The lookup gives you a line type and a carrier. The decision rules are yours, and they differ by business, but most teams land close to this.

Result	Usual handling
Invalid or unassigned	Reject at submission, or return the lead if it was bought
Mobile, wireless carrier	Accept. Record it as a cell phone for consent handling before any automated call or text
Landline	Accept for calls and email. Do not send texts; they will not arrive
VoIP, business phone provider	Accept. This is a company phone system, and usually a good lead
VoIP, wholesale carrier	Accept but confirm: call before paying for the lead, do not rely on texts, and weight it lower in quality scoring
Toll-free	Reject as a contact number. It is a business line being used to fill a required field

The two VoIP rows are where judgment is needed. Blocking every VoIP number is tempting, and for a few businesses it is correct, but it turns away the growing share of real customers who run their lives on an internet number, including most small businesses. Confirming by voice costs a call and keeps the customer. If you need the background on how fixed and non-fixed VoIP numbers differ and why services treat them differently, the article on what a VoIP number is goes into it.

Mobile numbers and consent

In the United States, automated calls and texts to cell phones are regulated more strictly than calls to landlines. The Telephone Consumer Protection Act requires prior express consent before an autodialer or a prerecorded voice is used to reach a wireless number, and prior express written consent when the call or text is marketing; the FCC's guide to unwanted robocalls and texts summarizes the rules from the consumer's side. The penalties are assessed per call, which is why list-based dialing operations care about this more than any other compliance question.

The practical point is that you cannot apply rules to cell phones unless you know which numbers are cell phones, and a form field labeled "mobile" is not knowledge. A line type lookup gives you a carrier-recorded answer for every number and a timestamp showing when you checked. That is not legal advice, and consent language, record keeping and dialing modes are questions for your counsel, but every one of those conversations starts from knowing the line type.

Pay-per-call: screening the caller instead of the form

When the lead is a phone call, the number arrives with the call and there is no form to validate. The check moves to the moment the call rings. A lookup at that point classifies the caller as mobile, landline or VoIP before the call is routed, and the routing can treat each class differently: ring a VoIP caller through to a short menu that a bot will not complete, send it to a lower-priority buyer, or reject it when a campaign has had enough of them.

This matters most where buyers pay for calls and dispute the bad ones. A buyer who receives a batch of thirty-second calls from non-fixed VoIP numbers will stop paying, and a network that cannot show what it did to filter them will lose the buyer. Line type is one of the few caller attributes that is available before the call connects, which makes it the cheapest filter in the chain. It pairs with the rest of the inbound toolkit: duplicate-caller rules so one person cannot be paid for twice, rate limits so one source cannot flood a campaign, and recording for the disputes that happen anyway. The guides to duplicate call suppression and live call monitoring for fraud prevention cover the other two.

This is the setup CallFlow was built around: numbers on a pay-per-call campaign can look up each caller's line type as the call arrives, and Spam Shield on each number can block, challenge or reroute VoIP callers while real customers ring straight through to the buyer.

Where teams get it wrong

The first mistake is treating line type as a fraud score. It is one input. A VoIP number with a matching name, address and traffic source is a customer; a mobile number submitted forty times from one IP address is not. Combine the line type with the signals you already have rather than letting it overrule them.

The second is trusting an old result after a port. A number that was a landline when the lead was captured can be a cell phone six months later, and if you dial it with automated equipment on the strength of the old check, the old check will not help you. Re-check numbers before a campaign that depends on the line type, and treat results more than a few months old as hints.

The third is spending the lookup budget on junk. Lookups against live carrier data cost money per query, and a form without a format check and a rate limit will burn the budget on bots. Validate the format first, cache every result, and check a number once rather than every time it appears.

The fourth is logging nothing. A rejected lead with no recorded reason turns into an argument with a publisher. A rejected lead with a stored line type, carrier and timestamp turns into a short conversation.

Set it up this week

Start by measuring. Export last month's leads, run the numbers through a lookup and sort by line type and carrier; the free VoIP number lookup handles a handful at a time, enough for a sample, and the pattern in a sample of fifty is usually the pattern in the whole file. If a traffic source stands out, you have your first rule and your first conversation.

Then put the check at the point where it saves the most money. For form leads that is usually submission; for bought leads it is intake; for calls it is ring time. Write the handling table above into your own terms, store every result, and review the rules monthly against what actually converted. If your inbound calls run through CallFlow numbers, turn on the line type check and VoIP handling per number and watch the dispute rate for a month before tightening it. You can create a free account and start with a single campaign.