vicigeeksimple guides
Browse
Dialing

VICIdial & agents · Pacing and dial level

Set a campaign dialing mode

Inspect MANUAL, RATIO and adaptive settings and plan a supervised pacing test.

Start the guide

01 / 03

1. Inspect the existing method

These steps target VICIdial Admin 2.14-969a, SVN 4037 / database schema 1748. Substitute unused IDs for LAB01, LABTEAM, learner1, 8001, 90001, SALESDEMO and DEMOIVR if any already exist. Labels and options may differ on other builds. The configuration checks below do not establish that a call, audio, or carrier route has been tested.

MANUAL requires an agent action; RATIO uses a configured level; ADAPT methods adjust pacing using campaign settings. Exact controls vary by method and version.

  1. Open Campaigns → Show Campaigns → the test campaign.
  2. Record Dial Method, Auto Dial Level, call time, Dial Statuses and any adaptive limits before editing.
  3. For initial configuration select MANUAL and save; reopen the campaign to verify the saved value.
Dial Method
MANUAL for the initial isolated test
Auto Dial Level
0 in the recorded inactive MANUAL lab example; record your existing value before changing methods
Choose the behavior before a levelScroll sideways to compare columns
MethodBehaviorUse only when
MANUALAgent initiates each call; ordinary manual-only lesson.The isolated outbound lesson needs no inbound delivery.
INBOUND_MANManual outbound plus inbound between calls; native level1.0, no outbound autodial.A permitted in-group/session and inbound test path are ready.
RATIOA configured ratio governs automatic outbound pacing.Staffing, carrier limits, destinations and an immediate stop monitor are approved.
ADAPT_HARD_LIMITAdaptive pacing constrains dialing against the configured drop target.The owner has reviewed target, maximum level and reporting on this build.
ADAPT_AVERAGEAdaptive pacing seeks an average drop target; it is not a hard legal-rate cap.The owner has accepted its different behavior and a separate stop measure.
ADAPT_TAPEREDAdaptive policy becomes stricter over the configured shift/call-time progression.The schedule and its meaning are verified; no safe rate is inferred from the name.

Set manual dialing and zero dial level

Duration 0:04
Real form entry · not saved
Steps and result4 steps

Actual native VICIdial controls, filled with example values in the browser. This recording stops before submission. Use the field notes to distinguish lab fixtures, missing prerequisites and deployment-specific values.

Entry shownReal native Modify controls with example values entered only in browser state. The form was not submitted; no configuration, route, permission, registration or call was changed.

Read the chapter notes
  1. Actual native form — not submitted

    Real native Modify controls with example values entered only in browser state. The form was not submitted; no configuration, route, permission, registration or call was changed.

  2. Choose MANUAL

    Dial Method MANUAL means agents initiate each call; this unsaved example keeps LAB01 inactive.

  3. Keep Auto Dial Level at 0

    Zero prevents this example from illustrating automatic pacing. No call is started.

  4. Review the unsaved example

    Real native Modify controls with example values entered only in browser state. The form was not submitted; no configuration, route, permission, registration or call was changed.

November 4, 2026 · VICIdial 2.14-969a build 261102-0125. Real native Modify controls with example values entered only in browser state. The form was not submitted; no configuration, route, permission, registration or call was changed. ViciGeek attribution is encoded in the video and poster. Use fullscreen to read the original field labels.

View still screenshots

Set manual dialing and zero dial level

Open to enlarge
Dial Method MANUAL and Auto Dial Level 0 in the native campaign controls.
Dial Method MANUAL and Auto Dial Level 0 in the native campaign controls.
Capture detailsUnsaved example on LAB01; the campaign remains inactive in the saved lab. Verify your own saved method and internal route before enabling a practice campaign. Actual browser capture, November 4, 2026; VICIdial 2.14-969a build 261102-0125.

LAB01 baseline after the call lab was restored

Open to enlarge
LAB01 baseline after the call lab was restored
Actual saved Dial Method MANUAL on retired LAB01.
Capture detailsThis baseline cannot receive the intended inbound handoff. The approved inbound/manual exercise uses INBOUND_MAN; the screenshot does not show that exercise enabled.

You should seeThe saved method is visible on campaign detail. The current lab crop shows MANUAL and Auto Dial Level 0; these are an example, not a tested automatic pacing rate. A saved setting does not prove a call.

02 / 03

2. Plan automatic pacing

Use RATIO only after the owner approves an automatic test; predictive ADAPT modes require separately reviewed limits and reporting. A dial level alone does not establish a safe or compliant rate.

Arithmetic illustration only: with4 agents counted by the configured tally and a fixed RATIO of1.5, the nominal target is6 lines before the dialer’s current live-call/trunk checks. It is not6 completed conversations or a safe production recommendation. Available-only tally, agents already handling calls and server/provider ceilings affect the actual action.

  1. Record original Dial Method, Auto Dial Level, Available Only Ratio Tally, adaptive maximum/drop target, call time and the exact staffing/counter definition. Choose the method from the table before proposing a numeric level.
  2. Write the authorized synthetic destinations, start/end time, maximum attempts, agent count and immediate stop threshold with the operator. Keep the campaign inactive until all are agreed.
  3. For an approved RATIO trial, enter the agreed fixed level, save/reopen and confirm the stored method/value; for ADAPT, inspect that build’s method-specific maximum, target and schedule instead of assuming a manually entered level stays fixed.
  4. Monitor only calls after the effective change timestamp and stop immediately at the agreed threshold. For comparison, use equal later measurement windows with the same status definitions and staffing; avoid a rolling week that mixes old and new settings.
Worked test record, not observed outputScroll sideways to compare columns
ItemSynthetic exampleEvidence to record
Counting assumption4 eligible agents; configured tally recordedActual current agent states and tally field.
Proposed RATIO1.5 → nominal6 lines before other gatesApproved value and reopened campaign.
StopOperator-defined numeric threshold, not supplied by the exampleLive counter name, window, denominator and owner.
RollbackOriginal method/level/tally/limitsReopened values and intended inactive/paused state.

You should seeThe change record identifies the settings, the operator and the rollback. If the fields are absent or differ, stop and consult this build’s field help before saving.

Measure a change without mixing periods

Investigate capacity and overlapping calls

03 / 03

3. Monitor and stop

Review real-time activity and the applicable campaign reports for wait and abandoned or dropped calls; interpret them using the organization’s rules.

  1. Observe the approved test under supervision.
  2. Stop the test when a threshold is reached or unexpected calls appear; pause the test agents and follow the local stop procedure.
  3. Restore the recorded campaign settings, save and reopen to verify.

You should seeThe campaign returns to the recorded settings. This guide has not performed a live pacing or call test.

Checks and sources

What was checked

  • These steps target VICIdial Admin 2.14-969a, SVN 4037 / database schema 1748. Substitute unused IDs for LAB01, LABTEAM, learner1, 8001, 90001, SALESDEMO and DEMOIVR if any already exist. Labels and options may differ on other builds. The configuration checks below do not establish that a call, audio, or carrier route has been tested.
  • Admin form captures are visual orientation only; no live call, audio, or carrier drill was performed for this guide.

Primary references

Sources

  1. VICIdial source and documentationVICIdial · accessed November 4, 2026
  2. VICIdial Non-Agent API referenceVICIdial · accessed November 4, 2026
  3. VICIdial statuses referenceVICIdial · accessed November 4, 2026