For sales ops and SDR teams
Route every lead the moment it arrives. One lookup returns the line type after porting, whether a carrier deactivated the number recently, and the time zone, so mobiles get a text-first cadence, landlines get a call, and dead numbers never reach a rep.
| If the lookup says | Do this |
|---|---|
| Mobile, active | Text first |
| Landline | Call first |
| VoIP (sub-type IPES) | Call-back queue |
| Deactivated in the last 45 days | Drop |
| Known TCPA litigator (+1 credit) | Suppress |
| Outside the rep's shift | Route by time zone |
Built from fields in the lookup response. The litigator check costs 1 extra credit.
Lead validation isn't a fraud problem. It's a routing problem: given what the lookup just returned, which channel, which rep and which urgency tier should this lead get?
About 32% of the numbers we look up are landline or VoIP, and most landlines can't take a text. nanpType and dipCarrierType give you the channel before the lead is assigned.
Source: CheckThatPhone lookup data
nanpTypedipCarrierType deactivationDate flags a carrier deactivation in the last 45 days, and reason carries the carrier id and date. Drop those before assignment.
deactivationDatereason Round-robin within a time zone, not across it. timezone comes from the lead's IP when you pass one, otherwise from the area code.
timezonetzOffsetgeoSource dipCarrierSubType "IPES" marks an IP-enabled (VoIP) line, from a live carrier dip. It can still be a real business line, so treat it as a routing input, not a reject.
dipCarrierSubType = IPES The same routing works for real estate ISAs, insurance agencies, lead sellers and call centers.
Every inbound lead (form submit, demo request, ad-platform lead) reaches your lead-routing service. Call the API there, attach the fields to the lead record and route in one pass. Speed-to-lead is the game, so don't wait for a nightly job.
Fast lane: an active mobile, clean, with a rep on shift in that time zone. Normal: anything else reachable. Call-back queue: landlines and VoIP. Dead: deactivated or flagged, no rep contact. Tune the tiers from your own conversion data.
For purchased or exported lists, upload the CSV before it reaches the dialer: drop deactivated numbers and litigators, tag landlines so the cadence is right, and split by time zone so each rep gets a list for their working hours.
| If the response shows | Field | Do this |
|---|---|---|
| Mobile, active | nanpType = mobileaction = send | Text-first cadence, then call. Queue normally. |
| Landline | nanpTypedipCarrierType | Call first. Ignore action: "unsubscribe", which only says it can't take a text. The landline SMS check (+1 credit) finds the ones that can. |
| VoIP | dipCarrierSubType = IPES | Call-back queue or email first, per your playbook. |
| Deactivated by the carrier recently | deactivationDatereason | Drop before assignment. Re-check if the lead submits again. |
| Blacklisted, or a known TCPA litigator | blackListlitigator | Keep it out of the rep queue. litigator needs litigatorFilter: true (+1 credit). |
| Time zone | timezonetzOffsetgeoSource | Assign to a rep on shift in that zone. From the IP if you pass one, otherwise the area code. |
| Carrier and porting | dipCarrierdipPorted | Attach to the lead record for reporting. |
A demo request submitted with the visitor's IP. It is an active mobile on a wireless carrier, so it goes text-first, to a rep on Mountain time: with an ip passed, location and time zone come from the IP (geoSource: "ip"), not the area code. ipResult only says the IP was valid.
Highlighted fields: action, nanpType, dipCarrierType, timezone, geoSource.
{
"success": true,
"credits_used": 1,
"data": {
"subscriber": "8185550142",
"optDate": "2026-10-08T21:56:26.108Z",
"action": "send",
"deliverable": "true",
"nanpType": "mobile",
"blackList": "false",
"ipResult": "valid-v4",
"dip": "success",
"dipLrn": "8185550142",
"dipPorted": "false",
"dipOcn": "6010",
"dipCarrierSubType": "WIRELESS",
"dipCarrier": "AT&T",
"dipCarrierType": "mobile",
"geoState": "UT",
"geoCity": "Salt Lake City",
"geoCountry": "US",
"geoMetro": 770,
"timezone": "America/Denver",
"tzOffset": 7,
"geoSource": "ip",
"error": "false",
"smsEligible": "true"
}
}Monthly cost, without the TCPA litigator scrub:
Routing needs no add-ons: one credit per lead. Computed from the published plans. Above 500,000 leads a month, contact us about volume.
Not legal advice.
deactivationDate: data refreshed daily, with a 1 to 7 day lag, and entries expire after 45 days. It is not a reassigned-number check.Branch on nanpType and dipCarrierType. A mobile can take a text, so text-first works. A landline usually can't, so call it, unless the landline SMS check returns smsEligible: "true". VoIP shows up as dipCarrierSubType "IPES".
Yes. Drop leads with a deactivationDate, with blackList: "true", or, with the litigator scrub on, with litigator: "true". Don't gate on deliverable alone if your reps call: it is "false" for every landline, because it is a verdict for text lists.
Both. For inbound, call it when the form is submitted, before round-robin assignment: you only get one shot at a demo request. For outbound, upload the list as a CSV before it reaches the dialer.
No. Phone validation isn't a substitute for firmographic enrichment or intent data: a reachable mobile tells you the channel is live, not that the person matches your ICP. Run the cheap check first, then spend on enrichment.
If you pass the lead's IP, timezone comes from the IP; otherwise it is the area code's zone, which is where the number was issued, not necessarily where the lead lives now.
500 free lookups a month. One credit per lead, no add-ons needed.