Define objective, scope and compliance
Batch platforms process existing phone lists; they do not acquire contacts. Identify source, intended use and records that should never enter the workflow. Campaign, member, event and support data require different actions.
Confirm a lawful basis. Number state does not replace user consent. Unclear provenance or incompatible use remains a risk even when the technical job succeeds.
Prepare consistent input
Upload a clean text or spreadsheet with one number per row and only necessary reference fields. Deduplicate, remove impossible lengths, normalize country notation and exclude row numbers and comments.
For merged sources, deduplicate before assigning traceable batch names such as campaign and export date. Split very large work into manageable files so one exception can be rerun independently.
Upload, select the type and submit
The standard path is sign in, create task, upload, choose the relevant screening type, review parameters and submit. Select basic state only for a reachability question and detailed states where suspended, disconnected or inactive distinctions drive actions.
Verify file identity, local and platform counts, and rule coverage. Review estimated duration and credits and retain the task ID for progress and reconciliation.
Accept before routing
Do not send results directly to dialers or messaging systems. Sample tens or hundreds of records against known or permitted test evidence to confirm the classification definition.
After acceptance, route usable, clearly invalid and review-required records separately. Use an export compatible with the downstream system and preserve the original result so an import mistake cannot destroy evidence.
Avoid errors and make the process reusable
Hidden characters, wrong check type, duplicates and permanent use of stale results are common failures. Re-screen on a documented cycle because states change.
For team work, define owners for export, cleaning, submission, acceptance and downstream import. The platform's durable value comes from making pre-contact validation a standard operating step rather than completing one isolated task.
