Replace a Voice Campaign Audience Without Redialing the Old List

Replacing a voice campaign audience should change who is eligible for the next run without erasing what happened before. If historical recipients remain mixed into the launch count, an operator can approve a call list that is larger or different from the one they intended.

Burki's campaign workflow preserves run history while excluding replaced historical recipients from the new pending audience. Use the review step to verify that behavior with the actual contacts, not just the filename of the import.

Separate the new audience from historical results

The old run answers “who was attempted and what happened?” The current audience answers “who may be called next?” Those views are related but should not be treated as the same list.

When replacing contacts, inspect the resulting audience after processing completes. A saved campaign or uploaded file is not itself evidence that every row was accepted or that the old recipients are no longer eligible.

The contact-management guide provides the broader import context. Preserve the original run history so staff can explain earlier attempts even after the active audience changes.

Normalize numbers before counting people

Two differently formatted rows can represent the same destination. Country context and normalization matter when judging duplicates. Twilio's official E.164 explanation describes the international number format commonly used for telephone destinations.

Do not infer permission from a normalized number. Deduplication identifies repeated destinations; it does not establish whether a person should receive a call. Keep current suppression and recipient preferences in the review.

If the source file includes invalid numbers, decide how the import reports them and verify what data remains after a failed replacement. An error should not be interpreted as a successful empty audience or a reason to launch whatever was there before.

A hypothetical replacement before a second run

Imagine a campaign previously used for a small approved callback list. The operator now imports a different set of requested callbacks. Some old contacts remain visible in history, while the new pending audience contains only the newly intended recipients.

A useful review compares the new list with the actual contact table and checks that old recipients are skipped or otherwise ineligible for the new run. The operator should be able to explain why each pending person belongs there.

If a contact appears in both old and new data, examine their current status and permissions rather than assuming that re-importing them resets everything. A historical failed attempt and a fresh authorization to call are separate facts.

Review the launch summary after the import

Check the selected assistant, calling source, pending recipient count, timing and maximum attempts. Reopen or refresh the review if the audience changed after it was first displayed.

Preview personalized content against real saved contact fields. A sample name can hide missing or incorrectly mapped data. The operator should see what the chosen recipient would actually hear, including any fallback for absent fields.

A campaign saved as a draft should remain a draft until the explicit launch or scheduling decision. Importing contacts should not be treated as permission to start calling.

Keep a simple replacement record

Record which source supplied the new audience, when it was processed and who reviewed the final eligible count. This is useful when a colleague later asks why an old recipient was not included or why an imported row was rejected.

After the run, inspect results for the selected run rather than combining them with all historical attempts. That keeps the outcome of the replacement understandable.

The voice-campaign guide can frame the overall process, but the saved audience and launch review should determine the next action.

Before your next replacement, choose one historical contact, one new contact and one deliberately invalid row in an authorized test dataset. Verify their treatment before approving a real campaign. The goal is a precise active audience with intact history, not a clean-looking table that hides earlier work.