vicigeeksimple guides
Browse
Agent operations

VICIdial & agents · VICIdial Fundamentals

Choose and verify a VICIdial disposition

Select the right disposition for a test call and verify its effect on the lead and reporting.

Start the guide
By Vicigeek Editorial DeskUnderstand the basics2 minute readUpdated November 4, 2026

1. Review the campaign's choices

  1. Open Administration → Campaigns, select the test campaign LAB01 and open Statuses. Record the available code and description for the test outcome and callback.
  2. Separately, Admin → System Statuses contains shared system definitions and flags. The pictured system screen is not the LAB01 campaign-status screen; compare the screen and the owner’s policy before selecting a status.
  3. For a promised callback, confirm the intended callback code and scheduling settings. For DNC, have the campaign owner explain the applicable DNC flag and policy; do not infer compliance from a status label.

Review system statuses

Open to enlarge
System statuses and their configuration flags
Read-only crop of the current lab system statuses, November 4, 2026; Admin 2.14-969a build 261102-0125.
Capture detailsIt shows the header and the first status rows; no status was changed. ViciGeek attribution appears at the top.

You should seeThe campaign’s configured choices control what the agent can select; the screenshot depicts only system status examples.

2. Save the observed outcome

  1. Complete an authorized test interaction and use Hangup Customer.
  2. On the disposition screen choose the status that reflects what actually happened and submit once.
  3. If the expected status is absent, pause and ask the supervisor; do not substitute a misleading outcome.

You should seeThe disposition screen closes after the saved selection; confirm the record rather than assuming a click was saved.

3. Distinguish callback from call outcome

  1. For a promised follow-up, select the campaign's callback disposition and complete the scheduling fields shown.
  2. Check the assigned owner, date and time in the callback list.
  3. If a callback is missing, check the campaign and user permissions and time zone before recreating it.

You should seeThe official status reference describes CALLBK as callback and CBHOLD as a holding state for scheduled callbacks; local workflow may add statuses.

4. Check the record

  1. Filter Reports → User Stats for the test user and date and locate the test by time and campaign.
  2. Compare the saved status to the outcome and check the lead through the authorized lead search if required.
  3. If they differ, ask the campaign owner for the supported correction procedure; do not alter call history directly.

Enter User Stats filters

Open to enlarge
Native User Stats form for selected synthetic user learner1, two example dates and an empty optional Call status input.
User learner1 is selected by the page URL; this build hides its User input. 2026-11-04 is an example date.
Capture detailsCall status is empty for any status; a nonempty value is an exact disposition filter. No report was submitted and no call or report row was demonstrated. Actual browser capture, November 4, 2026; Admin 2.14-969a build 261102-0125.

You should seeThe report and lead can serve different purposes, so confirm which record each screen displays.

Checks and sources

What was checked

  • Instructions are based on the linked project documentation and sanitized interface captures. The captures do not prove registration, a completed call, a transfer, callback or audio quality.
  • The lab runs VICIdial SVN 4037, database schema 1748 and Asterisk 18.26.4-vici. Labels, enabled features and provider requirements can differ on another installation.

Primary references

Sources

  1. VICIdial status definitionsVICIdial Group · accessed November 4, 2026
  2. VICIdial Agent API referenceVICIdial Group · accessed November 4, 2026