If you use Twilio Lookup only to avoid texting landlines, you can get the same result from a messaging platform that validates numbers at send time. The question is whether you want a separate lookup call or a check built into the send.

We make Ready, so we're comparing a lookup product with a built-in check. We haven't re-checked Twilio's current lookup pricing, so check its page for rates.

What a lookup is for

A number lookup answers a few questions before you spend money on a send:

Landlines can't receive a standard text, so sending to them wastes money and hurts your reputation.

Two ways to get it

ApproachHow it worksTradeoff
Separate lookup APIYou call it first, store the result, then sendAnother call and another bill to manage
Built into the sendThe platform checks as it sendsLess code, less control over timing

Our phone carrier lookup post explains what each field means.

How Ready handles it

Ready has a number validation switch in Settings under Compliance. Numbers its own sends have already seen as landlines are refused on every account, free. Switching on landline validation adds a send-time lookup for the rest, and a refused landline still bills its number check. Screening on the bill is $0.003 extra per segment when a switch is on.

That's a convenience for platforms that don't want to run lookups themselves. If you need raw carrier data for analytics, a dedicated lookup API gives you more.

Frequently asked questions

Do I need a lookup before every text? Not necessarily. Validate when you import a list, and re-check older numbers before big sends.

Can validation tell me a number is reachable? No. It tells you the line type, not whether the person will read the text.

The practical takeaway

Decide whether you want lookup data for its own sake or only to block bad sends. The second case is simpler with a check built into the send path.