Bulk Workflow

Use a bulk job to turn a contact file into a reviewed, segmented list before a campaign. The goal is to reduce avoidable bounces and give your team a clear review path. It is not a substitute for consent or audience expectations.

Prepare the source file

You can paste addresses directly, or upload a .csv, .xlsx or .txt file up to 10 MB. CSV and XLSX files work best when one column contains the contact email. TrekMail extracts addresses and removes duplicates, but a clear column makes the preview easier to check.

Keep the list to 50,000 unique addresses or fewer per job. If you have a larger file, split it into sensible segments, such as acquisition source or campaign type. That also makes the results more useful when you decide what to do next.

Before uploading a list from another system, make sure you are authorized to use it. Verification can identify technical risk; it does not grant permission to email people.

Make the result easier to use later

Split a very large source by a decision you will actually make later, such as campaign, geography, acquisition path or account owner. A single giant export can be difficult to review, while separate jobs make it clear which source produced the Risky or Invalid results.

Keep the original contact identifier in your source system. The verifier export gives you the address, score, provider and risk factors, but your own system should remain the place where you store consent, customer history and segmentation fields.

Choose a mode

• Pick Quick for routine cleaning and a fast first pass. It uses 1 credit per address.
• Pick Deep when a list is older, more important or less familiar. It normally uses 2 credits per address, with provider-specific exceptions shown in the estimate.

For a new source, start with a representative sample. Review its status mix and a handful of result details before you run the entire list.

Review the estimate

In Prepare, check these details before selecting Start Verification:

• the extracted address count;
• the number of duplicates removed;
• the selected mode;
• the exact credits that will be charged.

If the count is wrong, go back and fix the source. Credits are deducted when the job starts. Submitting the same normalized list in the same mode within 24 hours returns the existing job rather than creating another charge.

Check the cost in context

For Quick, each accepted address uses one credit. Deep normally uses two, except for the provider-specific addresses shown at the one-credit rate in the estimate. Compare the estimate with the current balance before starting. If the balance is too low, the job will not start, so you can add credits or reduce the segment deliberately.

Follow the job

The job continues in the background. The Verify stage reports progress and result totals as batches finish. Deep work may take longer when a receiving mail provider offers extra evidence, so avoid planning around a fixed completion time.

You can leave the dashboard and return later. The history table retains the job and its status.

Work with the result

Once the job completes, filter by status and review the reasons for addresses that matter to your campaign.

Download the group your next tool needs. Dashboard exports support all results, individual statuses and combined groups. The CSV includes the address, status, score, provider and risk factors.

A low-risk campaign handoff

1. Export Safe + Valid only when that matches the campaign's permission and risk policy.
2. Keep Risky as a separate review segment rather than merging it silently.
3. Correct obvious address errors in the original contact system.
4. Keep Invalid and opted-out contacts out of future sends.
5. Save the export with the campaign record before the 15-day retention period expires.

If you cancel a job

You can cancel a pending or processing job. TrekMail keeps processed rows, refunds credits for unprocessed work and leaves a downloadable result when at least one row was completed. A cancelled source file can be deleted from the dashboard after the job is no longer running.

Keep the list healthy

Verification is a point-in-time review. Re-check a list after a long pause, before an important campaign or when bounce rates increase. Keep invalid addresses out of future sends, honor opt-outs and use campaign results to improve the source, not just the score threshold.

If a repeated import produces the same problem, update the integration or form that created it. Re-running the same data may show the symptom again, but it will not repair a source that collects typoed or unwanted addresses.

See Reading Email Verification Results for the meaning of each status.