Understand automatic alternate-number dialing for a VICIdial lead

01 / 05

1. Separate a lead from its destinations

One lead can have a primary number and additional number fields. Automatic alternate-number dialing is a campaign feature for additional attempts; it is not the same thing as importing a second lead with the same customer details. The exact modes, available number fields and trigger statuses depend on the build.

The examples below use MAIN and ALT as labels only. A numbered row in a worksheet is a question to verify, not a promise that a specific number will be selected next.

Download the alternate-number ledger (CSV) →

02 / 05

2. Inspect the synthetic lead

Keep the campaign inactive. Use only numbers approved for a separately authorized internal test. Label destinations in the worksheet instead of copying phone numbers into a shared document.

1. Open Lists → Search For A Lead and find the dedicated synthetic lead by its exact lead ID. Record its list and campaign, current status and current called-since-reset flag.
2. Inspect the primary and available alternate-number fields or records. Record the field names and private labels MAIN and ALT. If a field is missing, stop and ask the administrator which alternate-number feature this build supports.
3. Confirm each destination is owned and approved for the test. If an alternate is blank, duplicated unexpectedly or outside the test scope, resolve it before planning calls.
4. Record existing call-history references and timestamps so later attempts can be distinguished from earlier activity.

You should seeThe worksheet identifies one lead and the source of each proposed number without claiming a call occurred.

03 / 05

3. Inspect the saved campaign controls

Open the test campaign and locate Auto Alt-Number Dialing and the Auto Alt Dial statuses page. In the captured installed help, the feature applies to RATIO and ADAPT, not MANUAL; compare that statement with your own build’s help before proceeding. Record the exact labels, saved mode and statuses shown by your installation. The source archive and on-screen help should be checked together: available options and their effects can differ by build.

A trigger status, list eligibility, call time and DNC checks are distinct conditions. A number existing in a field is not evidence that the campaign will call it.

1. Record the campaign ID, build, Dial Method, Active state and current alternate-number mode before making any change.
2. Open Auto Alt Dial statuses and the local help for that build. Record available modes, which source fields they use and the statuses that trigger another number. If a control or description is absent, stop rather than inventing an equivalent setting.
3. Record Dial Statuses, call time, applicable DNC and attempt limits and any relevant agent or campaign requirements. Ask the owner how these interact with alternate numbers on this version.
4. Have the owner review the proposed mode and stop condition. Do not enable automatic dialing or change a production campaign for this exercise.

Native Auto Alt-Number Dialing and threshold controls

Open to enlarge

You should seeA reviewer can trace the proposed mode and trigger statuses to the installed interface and source.

04 / 05

4. Plan a controlled attempt sequence

Write the desired observation for each row: lead identity, number label, status before the attempt, time, log reference and outcome. Leave actual sequence and result blank until observed. Include a stop after the first unexpected number, status or destination.

The hopper guide explains staging and source codes. A staged row is not a delivered call, and a disposition or an attempt counter should be checked against its own report.

1. Agree who will activate and stop the isolated campaign, the approved test window, and which internal destinations may ring.
2. Set a maximum number of attempts appropriate to the approved test, and record the original campaign settings for restoration.
3. Ask the system owner which report or read-only log identifies the dialed destination, status and time on this build. Confirm access before the test.
4. If no operator or approved destinations are available, leave the worksheet as a plan and do not infer the outcome from configuration alone.

Understand hopper source codes →

Inspect campaign call-count limits →

05 / 05

5. Record and reconcile an authorized test

If a test is separately approved and performed, the operator should observe the actual number selected and compare the lead, campaign and time with call records. Keep a row for each attempt, including attempts that fail or are skipped. Do not represent an expected sequence as an observed one.

1. After each authorized attempt, record the destination label, timestamp and time zone, resulting status, and report or log reference.
2. Compare those observations with the installed mode and trigger-status rules. If the next destination differs from the plan, stop and preserve the evidence before changing a setting.
3. Inspect the lead and relevant counters again; describe each observed value without assuming an alternate attempt counts the same way as a main-number attempt.
4. Restore the recorded campaign settings under the owner's procedure, verify the saved state and leave the campaign inactive until the owner accepts the results.

You should seeThe completed ledger distinguishes configured intent, a staged item and a real observed attempt. This guide itself has not placed calls.