1. Select a report
- Open Reports in Admin and find User Stats under Agent Reports.
- Write down the question, such as the activity of one test agent during one shift.
- Confirm the report and database time zone with the administrator before entering the date range.
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
- 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.
- Allow report viewing in the example
View Reports 1 is an unsaved example on a native user form. The report and user scope must also be authorized.
- Keep export disabled unless needed
Export Reports stays 0 for this example. No report was run or exported.
- 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 a still screenshot
Review report viewing and export separately
Open to enlarge
Capture details
No permission was saved, report run or file exported. Neighboring inherited controls do not establish a least-privilege account; review each required function and scope independently. Actual browser capture, November 4, 2026; VICIdial 2.14-969a build 261102-0125.You should seeThe Reports index groups different measures; a live wallboard and a historical report need not count the same events.
2. Set the scope
Choose the report’s agent before reconciling a wallboard. On this capture the user-specific URL already selects learner1, so no editable User box appears. A nonempty Call status filters one exact code; an empty value includes any status. Typing ALL would search for a disposition named ALL.
- For a practice worksheet, enter 2026-11-04 in both date boxes; substitute the actual test-call date and confirmed report time zone when using your own lab.
- Use learner1 only if it is your synthetic user. Enter it if User is visible, or confirm the selected user on the user-specific page. Leave Call status empty to include any status, then submit in your own lab.
- Record the exact filters, time zone and time the report was run.
- Start and end dates
- 2026-11-04 to 2026-11-04Illustrative date; use your authorized test window and confirm its time zone.
- User
- learner1Use only if the companion synthetic user exists; otherwise enter your own test user.
- Call status
- blankExample only; verify the blank-filter behavior on your revision.
Steps and result5 steps
Actual VICIdial form entry with fictional examples. The recording stops before saving; follow the field notes for deployment-specific values.
Entry shownThe native User Stats page for synthetic agent learner1 shows example date and Call status inputs. The user is selected by the page URL, not typed into this form. No report was submitted and no call result was demonstrated.
Read the chapter notes
- Actual VICIdial form — not submitted
The native User Stats page for synthetic agent learner1 shows example date and Call status inputs. The user is selected by the page URL, not typed into this form. No report was submitted and no call result was demonstrated.
- Set the reporting dates
Both dates use the fictional reporting window 2026-11-04. Use the date range and report time zone of your own known test event.
- Optionally filter by an exact status
The page was opened for synthetic agent learner1. Its user is carried in the URL and hidden form input. SALE illustrates an exact disposition filter; it does not demonstrate a saved sale or call.
- Leave Call status empty for any status
Clear the optional status input to include any disposition. ALL would be treated as a literal status code on this revision. No report is submitted.
- Review before any real save
The native User Stats page for synthetic agent learner1 shows example date and Call status inputs. The user is selected by the page URL, not typed into this form. No report was submitted and no call result was demonstrated.
November 4, 2026 · VICIdial Admin 2.14-969a build 261102-0125. The native User Stats page for synthetic agent learner1 shows example date and Call status inputs. The user is selected by the page URL, not typed into this form. No report was submitted and no call result was demonstrated. ViciGeek attribution is encoded in the video and poster. Use fullscreen to read the original field labels.
View a still screenshot
Enter User Stats filters
Open to enlarge
Capture details
Call 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 seeA blank report may mean no matching records, a wrong date or user, or insufficient permissions; it does not prove a call occurred.
3. Check a known event
- Find a known test call by its time and compare DATE/TIME, STATUS, CAMPAIGN, LIST and LEAD to the test record.
- If comparing with another report or wallboard, match the interval, campaign, population and definition of each metric.
- Investigate one unmatched event before using a difference as an agent performance conclusion.
The individual call columns
Open to enlarge
Capture details
This blank report shows the column headings only. VICIdial’s official demo, 2.14-947a; captured November 3, 2026.You should seeAn agent activity interval and a call event are different units. Record definitions alongside any exported metric.
Recorded lab terminal checks
Recorded lab checks were run against the synthetic demo on November 4, 2026. These read-only observations supplement the configuration steps above; they do not establish that a call, route, recording or report workflow succeeded.
Recorded lab observation: Schema metadata only; no application behavior tested.
Recorded lab observation: No matching call log rows at capture; this does not validate reports or prove no calls elsewhere.
- Before you use it
- These historical commands were captured in a root shell using database vicidb and /etc/vicidial-readonly.cnf. The private client file in Create a read-only database account for safe VICIdial queries is root-owned with mode 0600: use the approved root context from that guide, or invoke mysql through sudo as it describes. A regular user cannot read that file. On your own server use your authorized connection and test campaign/list IDs; changed commands are not this exact capture. Do not print the credential file.
mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SHOW COLUMNS FROM vicidial_log WHERE Field IN ('campaign_id','list_id','status','call_date','length_in_sec');"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SELECT COUNT(*) AS call_log_rows FROM vicidial_log WHERE campaign_id='LAB01' AND list_id=90001;"Captured demo response · 2026-11-04T22:38:04.468555Z. Any filtering, hidden values or test-only data are identified in the capture label. Select Replay transcript to read the recorded output.
- Success looks like
- Compare the returned rows with the specific task and capture time. An empty result or zero count is an observation to explain, not a complete diagnosis or evidence of a working call.
- Stop if
- For a connection, permission, schema or missing-test-ID error, check the approved client configuration and installed version first. Do not broaden permissions or change production data to match this demonstration.
Steps and result4 steps
Review read-only aggregate and configuration results; no live call or audio was tested.
Observed read-only resultThe lab contained four inbound groups and two DIDs; LAB01 recording mode was ONDEMAND and its scoped call-log count was zero.
Read the captured terminal transcript
Read the chapter notes
- The database contained four inbound groups.
Read-only captured command and output; rendered for this replay.
- The database contained two DID records. These counts do not prove routing.
Read-only captured command and output; rendered for this replay.
- LAB01 recording mode was ONDEMAND. No recording or audio was tested.
Read-only captured command and output; rendered for this replay.
- The scoped LAB01 and list 90001 call-log count was zero. Reports were not validated.
Read-only captured command and output; rendered for this replay.
November 4, 2026 · ViciBox 12 · SVN 4037. Configuration and counts only: routing, calls, audio, and reports were not exercised. Rendered actual SSH capture using xterm.js; paced still frames, not a live terminal recording. SSH client warning omitted from captured output. Use fullscreen to read the terminal output.
View still screenshots
Recorded lab terminal: report log columns
Open to enlarge
Capture details
Read-only observation, not a completed call or routing test. Display trims blank space; enlargement opens the complete original. SSH client post-quantum warning on stderr omitted; SQL stdout preserved. Aggregate counts or schema only; no customer rows.Recorded lab terminal: lab report count
Open to enlarge
Capture details
Read-only observation, not a completed call or routing test. Display trims blank space; enlargement opens the complete original. SSH client post-quantum warning on stderr omitted; SQL stdout preserved. Aggregate counts or schema only; no customer rows.You should seeThe recorded lab command and output show exactly what the demo returned. Use the original workflow’s separate end-to-end acceptance checks before declaring success.
Checks and sources
What was checked
- In this lab, automated reports were disabled and no report slave was configured at the time of writing.
- No report rows, wallboard screenshots, benchmark, external-analytics implementation or review history was used.
- Reviewed read-only SSH observations were added from the ViciBox 12 / SVN 4037 demo on November 4, 2026. Captures show point-in-time state, not successful calling, routing, audio, API writes or recovery.
Primary references
Sources
- VICIdial demonstrationVICIdial Group · accessed November 4, 2026
- VICIdial Quality Control ManualVICIdial Group · accessed November 4, 2026