VICIfast Support Team
VICIfast Support
The VICIfast support team. We run managed VICIdial full-time and write these guides from the operator's chair.
Posts by VICIfast Support
How to read the Latency Gaps Report and what a gap actually means
A latency gap is a missing stretch of latency log entries while an agent was supposed to be logged in. Here's how the Latency Gaps Report reveals session trouble.
How to read the Agent LAGGED Report to find which dialer is struggling
The Agent LAGGED Report pins lag to a specific dialer and lists every lagged event by user, campaign, and time. Here's how to read both halves.
How to read the Agent Parked Call Report to see hold-time drops
The Agent Parked Call Report shows parked calls by agent and timeframe for one day, the average time on hold, and how many callers dropped while waiting.
How to read the URL Log Report to debug webhook and webform calls
The URL Log Report records every URL VICIdial requested — dispo call URLs and WEBFORM clicks. Here's how to read it to find why a webhook or webform failed.
Human answered vs customer contact: what the difference means in reports
VICIdial reports lean on two status flags: human answered and customer contact. They sound similar but measure different things. Here is the difference.
How to read the Caller ID Log Report to see which CIDs you've burned
The Caller ID Log Report breaks calls down by the caller IDs a campaign used, so you can see which numbers are burned and rotate them before they go spammy.
TEXT vs HTML report format: which to pick
VICIdial reports come in TEXT and HTML formats. Here is the practical difference and when to pick each, plus where to set your default.
How to run a report against archived data
Older VICIdial call data moves to archive tables. Use the Search archived data checkbox to run a report against it without digging through SQL.
How to read the API Log Report when an integration stops working
The API Log Report shows API entries for a date and time range, filterable by API User, Agent User, Function, and Result, so you can find why an integration broke.
How to read the AMD Log Report when answering-machine detection looks wrong
The AMD Log Report shows the result of answering-machine detection on each placed call. Here is how to read it and tell real misfires from carrier noise.
The VICIdial troubleshooting playbook: where to start when something breaks
A symptom-first guide that routes you from what's broken — dead dials, false answers, slow agent screens, drops on hold — to the exact VICIdial report that holds the answer.
How to read the Dial Log Report and what the SIP codes mean
The Dial Log Report groups every placed call by its SIP response code. Here is how to read each column and turn a wall of codes into a real diagnosis.