A successful import is only the first check.

Record where the file came from, its date, the responsible business and the proposed campaign. Identify the relevant source record reference so a later correction can be traced back without relying on an operator’s memory.

Do not label an entire CRM export “warm” or assume a fresh purchased list is eligible. Review the actual relationship, source permissions, applicable registry work, stop requests and intended use under the approved policy.

Keep records with missing or conflicting eligibility on hold. A list provider’s schema and marketing labels do not establish what the customer may do with each record.

This is a mapping checklist, not a claim that DialBreeze accepts particular column names. Confirm the current supported import format with the setup team.

• Identity and reference: how the contact and source record are distinguished.
• Phone: the intended number, country context and any alternate-number meaning. Confirm the accepted format rather than guessing.
• Context: the property or campaign information the operator actually needs.
• Location: the information used by the approved local-time review.
• Restrictions: known suppression and other conditions that must not be lost.
• Ownership and follow-up: any existing responsibility or agreed next step that affects release.

Do not paste unnecessary sensitive data into a public support form to ask about a format. Use synthetic examples with representative field shapes.

During the trial, use only test data and the provisioned sandbox. Do not import a real customer calling list or use a real person’s phone to make the test more convincing.

1. Include an ordinary record and examples of the edge cases you need to resolve: a missing field, alternate number or duplicate source reference.
2. Compare the input with the resulting records. Inspect identity, phone and context rather than checking only an imported-row count.
3. Confirm how invalid or ambiguous data is reported and what the supported correction process is.
4. Inspect the handling of known restrictions with permitted test records.
5. Document the accepted format and unresolved cases before preparing production data.

A screenshot of one correct record does not establish that every row mapped correctly. Keep the input and result references so the review can be repeated.

Check the selected list, authorized outgoing number, supported quiet-hours settings and attempt cap. Confirm the operator’s audio setup before release. Decide the recording process separately with the responsible reviewer and verify that the available configuration supports it.

Do not choose more lines simply because a file is new or a lead was expensive. Inspect the actual answer-handling behavior and the operator’s capacity. A number being below an attempt cap does not make it eligible to call.

If the business uses several systems, identify where the authoritative restriction and next-step records live. A CSV workflow is not a native integration or an automatic two-way synchronization.

Release: the required mapping and eligibility review is complete and the responsible owner approves the record for the campaign. Hold: a missing fact or conflict needs resolution. Exclude: the record does not belong in the campaign under the current decision.

Do not use deletion as the only way to remember why a record was excluded. Follow the customer’s approved data and suppression process so a later import does not restore a known problem without review.

A changed property status, an assigned agent or a requested callback may require coordination rather than a generic “bad lead” label. Preserve the actual reason and the responsible person.

Wrong-number reports: hold or correct the affected identity mapping. Duplicate records with different restrictions: reconcile the conflict rather than selecting the callable version. Missing location: use the approved hold process rather than guessing from the office clock.

Unexpected import result: preserve a synthetic reproduction and report the expected and observed fields. A known stop request becomes callable: pause the affected workflow and investigate; do not call the person to prove the failure.

After a call, confirm that the disposition and next step remain attached to the correct record. If information moves back to a CRM, verify the supported handoff and the values that must survive it.

A useful release record identifies the source file, mapping version or agreed format, review date, owner and the counts released, held or excluded under your process. It also points to the permitted test evidence and unresolved exceptions.

Those are recommended operational records, not a promise that the product creates a particular report automatically. Use the systems your team has actually verified. The next person should be able to explain why a record is in the queue without reconstructing the import from scratch.