Mapping your old dispositions to VICIdial statuses

Every dialer platform has its own vocabulary for what happened on a call. Your old system might call it a "disposition"; VICIdial calls it a Status (lead status) or Called status. The names are different, some of the behaviors are different, and a handful of VICIdial statuses are system-reserved and cannot be renamed. Getting this mapping right before you import leads saves hours of reporting confusion after you go live.

Dispositions versus VICIdial statuses

In most hosted platforms a Disposition is a label an agent applies at the end of a call - "interested", "not home", "do not call". VICIdial uses a two-layer system: system statuses (set automatically by the dialer for machine detections, no-answers, and drop events) and agent statuses (set by the agent in the Wrap-up screen). Both live in the same status table, but the system ones are written by the dialer engine, not the agent.

System statuses you cannot rename

VICIdial reserves a set of uppercase status codes that the dialer engine writes directly. These include NA (no answer), ANSWMACH (answering machine), BUSY, CONGESTION, DROP (dropped call), DNC (added to do-not-call), CBHOLD (callback on hold), and a few others. You cannot rename them because the dialer code references them by exact string. Any reporting you build must treat these as immutable.

Building your mapping table

Pull the full list of dispositions from your old system - including counts so you know which ones actually get used. Then create a three-column spreadsheet: old disposition name, VICIdial status code (max 6 characters, uppercase), and the VICIdial status description. Work through each row and decide: does this map to an existing system status, or do you need a custom one?

flowchart TD
    A[Old disposition list] --> B{Maps to system status?}
    B -- Yes --> C[Use system status code]
    B -- No --> D[Create custom status code]
    C --> E[Add to mapping table]
    D --> E
    E --> F{Is it a DNC trigger?}
    F -- Yes --> G[Set DNC flag on status]
    F -- No --> H[Set sale or callback flag if needed]
    G --> I[Mapping complete]
    H --> I

VICIdial status codes are limited to 6 characters. If your old platform had long disposition names like "LEFT_VOICEMAIL_CALLBACK_REQUESTED", you need an abbreviated code like LVMCB and a clear description. Keep the description under 30 characters so it fits cleanly in the agent Wrap-up dropdown.

Keeping reporting comparable across the migration

Once you have your mapping table, document it and share it with anyone who builds reports. Your old platform likely grouped dispositions into categories for management dashboards - "positive", "callback", "unreachable". Replicate those groupings in VICIdial by using a consistent naming prefix on your custom statuses (e.g., CB_ for all callback variants) so SQL filters and the Real-time report can group them the same way.

For teams moving from a platform with a managed reporting dashboard, also read closing the reporting gap after leaving a hosted platform, which covers how to rebuild summary views in VICIdial exports and optional tools like QueueMetrics.

The broader migration process - including how to export historical data before you move - is covered in the VICIdial migration guide. If you want a managed VICIdial environment where statuses come pre-configured and ready to extend, see VICIfast managed plans.