A list of numbers lands on your desk. What comes next?

From organizing a list to reviewing records, see where carrier lookup fits into the work.

MayaOperations manager

How do you add carrier data to a US number list?

Maya receives a US number list to hand to her team. It has phone numbers but no fields they can use to group records by original assigned carrier. She submits the list for lookup, downloads the result CSV, and adds carrier and country_code beside each number so teammates can filter and review the records.

Read the story

Organize the list with lookup results

The table shows three real test rows from a downloaded bulk-task CSV. Each row keeps the original number alongside carrier, line type, country, and area fields so the team can filter and review the list.

She uploads a same-country number file and downloads the result CSV when the bulk task completes.

The returned carrier and country_code fields let the team filter the list in its own spreadsheet.

View the file task workflow

Carrier filecarrier_batch.csv

Real test result

The returned file

03 sample rows

Number	number_type	country_code	carrier	underlying_carrier	region	city
19802984181	Fixed Line or Mobile	US	AT&T	—	NC	CHARLOTTE
19087088280	Fixed Line or Mobile	US	T-Mobile	—	NJ	LINDEN
15715016304	Fixed Line or Mobile	US	AT&T	—	VA	WSNGTNZN17

These rows come from a carrier_batch test CSV. Scroll horizontally to see all seven columns. “—” means the field was not returned; it does not mean the lookup failed.

One new record, one conflicting field

One new contact needs context; another signup needs a country-field review. Here is how the team handles each.

AlexCRM operations

A new contact has a number but little context.

A new lead reaches Alex with a phone number, but the contact record has no carrier or country context. Sales needs a clearer record before following up.

Alex runs a single-number lookup and reviews the original assigned carrier, number type, and country code, keeping any customer-submitted details separate.

Alex adds T-Mobile and US as lookup fields in the team’s own contact record. The next teammate can see them beside the number and decide whether anything needs another check.

Contact record+12345678900

Before lookupcarrier —country_code —

After lookupcarrier T-Mobilecountry_code US

Lookup values come from a verified test sample. Saving them in a CRM is illustrative; this site has no built-in CRM integration.

View the API request

SamData quality analyst

The submitted country and allocation country differ.

While reviewing signups for the Canada team, Sam finds a record where the user selected CA but the number lookup returns US as its original allocation country. She needs to trace the difference to the form entry, phone number, or data sync.

Sam places submitted CA beside returned country_code US in the review record, then checks the original number, form source, and submission time so the two fields are not conflated.

She marks the record for review and asks the lead owner to confirm the customer-submitted details. The reviewer records the owner and outcome before changing any team assignment.

Record review+12345678900

Saved valueCA

Lookup resultUS

Submitted country to review

Illustrative review record: CA is a hypothetical form value; US is the lookup result. Both values and their sources stay visible for the team.

Try a number

Lookup results show original allocation information, not the current carrier after porting. These examples do not establish consent, ownership, reachability, or real-time location.

Start with the workflow that fits your team

Explore a number in the browser, then use the API when you are ready to connect your own application.

Try a lookup Read API documentation →