Prepare the list and acceptance rules
Clean spaces, hyphens, parentheses and non-phone fields before upload, and confirm supported countries and file formats. Decide in advance which states are unusable for the specific workflow. Marketing may suppress disconnected and long-suspended records, while support may retain powered-off numbers for a later attempt.
Follow a five-step operating process
First configure organizational and export permissions. Second upload or paste the list while observing batch and billing limits. Third choose basic or extended checks and submit the job. Fourth review state distributions, failure reasons and timestamps, then download the result. Fifth map usable records to approved contact channels, suppress invalid records, and retain the original report for accountable review.
Interpret states correctly
Normal or in-service generally means technically reachable; disconnected means unassigned or cancelled; suspended may be temporary; powered off is not the same as disconnected; and unknown often reflects timeout, a new range or rate limiting. Recheck unknown samples rather than automatically rejecting them. Investigate implausibly high invalid or unknown shares as possible format, source or provider issues.
Avoid common operating mistakes
Headers, row numbers or notes in the phone column can break a batch. Rechecking confirmed disconnected records every day wastes quota. Incorrect CRM column mapping can route invalid records into calling queues. Test mappings with a small sample and restrict access to exported personal data, deleting local copies under the retention policy.
Acceptance and compliance
A complete run should show who uploaded the list, when it was checked and how results were used. Link the task or report ID to the campaign, sample both accepted and rejected records, and verify that suppression changes reached downstream systems. Screening purchased data does not prove consent; authorization records and opt-out mechanisms remain mandatory.
