Prepare contacts for a voice AI campaign
Map fields, preserve suppression and preview representative records before an authorized campaign import.
Table of Contents▼
Contact preparation determines who may be called and what the assistant will know. Treat import as a data review, not merely a file upload. A phone number in a spreadsheet is neither proof of identity nor permission to contact its holder.
Define the record before importing
Identify the stable contact reference, destination number, source, permitted purpose and any applicable suppression. Add only custom fields needed for the intended conversation. Keep sensitive information out of generic greetings and unnecessary logs.
Use the actual import interface and current schema to confirm accepted formats, required fields and limits. Do not rely on a historical article's file-size or contact-count promise.
Review a representative sample
| Record condition | What to check |
|---|---|
| International number | Country code and intended destination are correct |
| Duplicate | The chosen merge/update behavior preserves restrictions |
| Missing optional name | The message has a neutral fallback |
| Missing required action field | The workflow asks for it or blocks the action rather than inventing it |
| Suppressed contact | Import or later re-import cannot casually reactivate it |
| Unknown timezone | No unverified assumption about a permitted calling window |
A normalized number is not verification of its current owner or location.
Preserve provenance and changes
Record where eligibility information came from and who can change it. Keep campaign membership separate from permission. A segment labelled “active” or “warm” should not overwrite an opt-out or another restriction.
Burki has optional contact and campaign services, but this guide does not promise a managed national-registry subscription, universal automatic opt-out recognition or every CRM synchronization path. Verify the controls required for the actual run.
Preview before dialing
Render the selected message template against normal, incomplete and edge-case records. Review the spoken meaning, not only whether the syntax is valid. Do not start a large campaign to discover that a field was mapped incorrectly.
Use controlled endpoints for execution tests and retain the import/run reference for investigation. The do-not-call guide describes the separate contact-policy questions that must be resolved before a live list is used.
Ready to try Burki?
Create an assistant and check your available browser practice allowance.
Create your assistantTrial eligibility and available practice are shown in your workspace.