Registration filtering
Review the returned signal against your own source records before applying a filter.
Append carrier, underlying-carrier, line type, country, region and city context to international phone records. Write the result back to your CRM for routing, regional analysis, registration filtering and list segmentation; number portability and source differences can affect field interpretation.
global_carrier_batch.csvIllustrative preview| number | carrier | underlying_carrier | number_type | country_code | region | city |
|---|---|---|---|---|---|---|
| +12025550101 | T-Mobile USA | T-Mobile USA | mobile | US | California | San Francisco |
| +12025550102 | T-Mobile USA | T-Mobile USA | mobile | US | California | San Francisco |
| +12025550103 | T-Mobile USA | T-Mobile USA | mobile | US | California | San Francisco |
These are the product's declared result fields. Read their meaning before making a decision. Understand your results →
numberThe submitted phone number.
carrierThe returned carrier.
underlying_carrierThe returned underlying carrier.
number_typeThe returned line type.
country_codeThe returned country code.
regionThe returned region.
cityThe returned city.
Review the returned signal against your own source records before applying a filter.
Group records using the defined result and evaluate the segment in your workflow.
Keep source data and consent records separate from detection results.
Sign in, upload your phone list, review the server quote and track processing in the background.
First version: one E.164 number per line, a single column and one country per task. Original multi-column records are not retained.
USD per 10,000 numbers. Each task needs at least 1000 numbers; pay-as-you-go and subscription users pay the same rate.
View pricing →Sign in, upload your phone list, review the server quote and track processing in the background.
Create a task