Prepare a CSV, verify the right column, and turn results into reviewable sending segments while retaining your original contacts.
Work on a copy of the original export. Use a header row, one contact per row, and a stable contact identifier. Keep notes or other columns quoted correctly if they contain commas or newlines. Remove contacts you already know must not be contacted; verification does not establish consent.
email,contact_id
person@example.com,contact-001
sales@example.org,contact-002
invalid-address,contact-003Open Bulk validation and choose the CSV. Inspect the preview and the detected email column. If multiple columns look like email addresses, choose the intended one. Review the row estimate and your balance before starting. Default server limits are 200,000 rows and 10 MiB per file; split larger exports and retain which contacts belong to each file.
After starting, use Recent jobs to inspect the same job. Background processing continues independently of the page. If progress refresh fails, wait for the next refresh before assuming the job failed. When a job pauses for capacity or credits, resolve the cause and resume it. Avoid uploading a duplicate just because a response was slow.
Download the completed result file and retain your original contact mapping. Inspect the actual output headers before importing into your CRM. Keep valid contacts eligible under your sending policy, risky contacts in a review segment, invalid contacts suppressed from this send, and unknown contacts in a separate inconclusive segment. Do not delete original CRM records automatically.
Record the verification date, list identity, total rows, outcomes, errors, and credits used. A result is an observation at a point in time; lists age and mail routing changes. Recheck based on the age and use of the list rather than assuming that a previous valid result lasts forever.