How to bulk-move callbacks by campaign, list, or agent

The Callbacks Bulk Move utility in VICIdial lets you move a large set of Scheduled callback records to a different list in one operation. You can scope the move by campaign, by list, by user group, or by individual Agent — or combine those dimensions to narrow the selection further. This is the operational tool you reach for when you need to reorganize callbacks at scale: restructuring a campaign, handling departures, or archiving a finished list while preserving its callback records elsewhere.

Before you start

Decide your source dimension. The utility presents four multi-select lists, each pre-filtered to entries that currently have at least one callback: campaigns with callbacks, lists with callbacks, user groups with callbacks, and agents with callbacks. You can use any combination, but remember that selections across multiple dimensions combine with AND logic — they narrow the result, not broaden it. If you want to move all callbacks from a Campaign regardless of which agent owns them, select only the campaign and leave the agent list empty.

Also decide whether you want to clean up the callbacks table before the move. The two optional purge checkboxes handle stale records: purge called records removes entries the table is holding that are already completed or invalidated; purge uncalled records removes entries that are still active but unworked. Read the count the page shows before confirming either purge — it is a destructive operation.

Step by step

1. Open the Callbacks Bulk Move page in VICIdial admin.
2. In the Campaigns with callbacks list, select the campaign(s) whose callbacks you want to move. Hold Ctrl or Cmd to select multiple entries. Leave this empty if you are scoping by list or agent instead.
3. In the Lists with callbacks list, select specific list IDs if you want to scope to particular lists rather than an entire campaign. Leave empty if not needed.
4. In the User groups with callbacks list, select user groups if you want to scope by team. In the Agents with callbacks list, select individual agents if you want to scope by person.
5. Enter the destination list ID — the list where the callback lead records will land after the move.
6. Optionally enter a new Called status to assign to the moved leads. This is useful for tracking that these leads were bulk-transferred.
7. Check or uncheck the purge options based on whether you want to clean stale callback records before the move runs.
8. Submit. The page will show you how many records match before asking for confirmation on any destructive purge step.

flowchart LR
  A[Choose source dimension] --> B{AND across selected criteria}
  B --> C[Matching callbacks identified]
  C --> D{Purge stale records first?}
  D -->|Yes — called| E[Remove already-completed entries]
  D -->|Yes — uncalled| F[Remove active-but-unworked entries]
  D -->|No| G[Skip purge]
  E --> H[Set destination list ID]
  F --> H
  G --> H
  H --> I[Optional: set new status]
  I --> J[Confirm and execute]
  J --> K[Verify callback count at destination]

Verifying the result

After the move completes, check the destination list to confirm the callback leads arrived. You can also re-open the Callbacks Bulk Move page and look at the same source dimension you selected — it should now show fewer or no callbacks for those criteria. If you assigned a new status, spot-check a few lead records to confirm the Disposition updated correctly.

One operational note: if the destination list is attached to a different campaign, the moved callbacks will now be worked by that campaign on its next dialing pass. Make sure the destination campaign's dialable statuses and callback settings are configured to handle those leads the way you expect. A callback that lands in a list on a campaign that does not have callback dialing enabled will sit idle.

When to use each source dimension

Scope by campaign when you are restructuring or sunsetting an entire campaign and want all its callbacks moved to a new home. Scope by list when a specific list is being retired but the campaign continues. Scope by user group when a whole team is being reassigned. Scope by agent when handling an individual departure — though for the simpler agent-to-agent case, the Callbacks Transferral page is often faster because it is a single-agent, single-destination workflow.

The Callbacks Bulk Move utility is the heavier tool: more dimensions, optional purge, AND logic across criteria. It is worth the extra configuration when you are moving callbacks at a campaign or user-group scale. For individual agent reassignments, start with Callbacks Transferral and step up to Bulk Move if you need finer control over which callbacks get moved.

For an overview of what the utility does and how the AND logic works across dimensions, see what the Callbacks Bulk Move utility does. For the full picture of all VICIdial admin bulk tools, read our VICIdial admin bulk tools guide.

Want a hosted dialer where this just works? See VICIfast pricing - you can be live in under 40 seconds.