How to Validate Mobile Numbers in Bulk with DataSoap

Bulk mobile number validation helps you review an existing file before using it in a calling, messaging or customer-contact workflow. Instead of checking records one at a time, you submit a list and use the returned information to decide which numbers can proceed and which need attention.

This guide focuses on the file workflow with DataSoap: preparing the numbers, choosing mobile checks, interpreting the export and putting the results back into your systems. For the underlying technology, see the HLR lookup service.

Before you start: define the job

A bulk lookup is most useful when the result supports a specific decision. You might be refreshing an old candidate database, preparing an SMS audience or reviewing a CRM export before migration.

Write down what should happen to a correctly formatted number, a confirmed invalid result and an inconclusive lookup. Keep your channel permissions and suppression decisions separate from technical phone status.

1. Export a controlled source file

Use the segment you intend to review, with a stable identifier for each underlying contact. Retain an original copy and note when it was exported. Include only the fields necessary for the job.

• Put one mobile number in each lookup row.
• Keep country information where the file contains international records.
• Store phone numbers as text to preserve leading zeroes and the plus sign.
• Identify duplicate lookup values before checking the same number repeatedly.
• Preserve the link between a shared number and any separate CRM records.

If Excel has already removed a leading zero, changing the cell format afterwards does not necessarily restore the original value. Correct the source using reliable information instead of guessing missing digits.

2. Separate formatting from network status

A number can have a plausible structure without being active. Formatting checks assess the value’s structure; an HLR lookup queries mobile-network information.

Do not interpret a valid format as proof that the number reaches your intended contact. Also, a number reported as switched off is not automatically a permanently disconnected subscription.

Decide whether the job needs mobile validation, number portability information or another check. Current network and original allocation answer a different question from whether you have permission to send marketing.

3. Run a representative sample through the portal

Sign in to DataSoap and use the portal’s bulk upload workflow. Check that your mobile column is being interpreted correctly and select the mobile validation service for the job.

Review the current pricing and account balance before processing a large file. Use a small sample first if the source is new or the country formats are mixed.

The sample should test the data pipeline as well as the lookup: can you recognise the result, match it to the correct record and import it without overwriting other information?

4. Read the exported mobile results

DataSoap’s mobile service page shows a portal export with the mobile number, network, live/dead status, switched-on status and an error message. Use the fields together.

Information	How to use it
Number checked	Match the result back to the original record.
Network information	Understand the network returned by that lookup.
Live/dead assessment	Apply the handling rules agreed for your workflow.
Switched-on status	Treat it as a point-in-time handset status, not a promise that someone will answer.
Error or inconclusive outcome	Distinguish a temporary problem from a permanent invalid result before excluding a number.

The API reference explains error classifications for integrated lookups. Follow the information returned by the method you are using rather than assuming every output has identical labels.

5. Create a review group for uncertain records

Keep confirmed outcomes separate from temporary network failures and ambiguous results. If you retry a temporary failure, use a defined policy with a limit rather than repeatedly charging for the same unresolved lookup.

An illustrative policy might place permanent invalid results outside the operational campaign file, keep inconclusive results in a review queue and allow other records to proceed to the next eligibility checks. That is a business rule to design, not a universal rule that fits every use of a phone number.

6. Reapply campaign and contact preferences

A positive mobile result does not establish identity, ownership or permission. Before live marketing calls, apply the relevant TPS, CTPS and internal suppression checks. For SMS marketing, assess the separate rules for that channel; absence from TPS is not SMS consent.

Apply new objections received while your file was being checked. Never let a technical refresh switch an opted-out record back to “contactable” by default.

7. Update the CRM with dates and reasons

Reconcile the submitted and returned records. Where one lookup serves several customer records, map the result back without merging those people. Preserve the validation date and distinguish technical status from marketing eligibility.

Check a sample of imported records and the final count. Investigate an unexpected jump or drop before using the data in a live workflow.

When does an API make more sense?

Use file-based jobs when the list already exists or the task is occasional. Consider the DataSoap API when records arrive continuously or your team repeats the same export-and-import routine. The result handling still needs to be explicit in either approach.

Frequently asked questions

Can bulk validation confirm who owns a number?

No. Network information does not confirm the person using the subscription or whether the record still belongs to your intended contact.

Should I remove every switched-off number?

No. A handset may be temporarily unavailable. Read the full result rather than treating one status as permanent disconnection.

How long can I rely on a result?

It is a snapshot. Choose refresh points around the age of your data, its use and the consequences of a failed contact attempt.

Prepare the file, then act on the results

Start with a controlled sample and a clear handling policy. Explore DataSoap mobile validation or ask the team about your bulk checking requirements.