When the Dispo Call URL doesn't fire: finding it in the URL Log

Your Dispo Call URL is supposed to ping your CRM or webhook every time an agent dispositions a call, but the records aren't landing on the other side. Before you assume the integration is broken, check whether the request even left the dialer. VICIdial records every Dispo Call URL request in the URL Log Report, so you can tell the difference between "VICIdial never sent it" and "the far end dropped it" in about a minute.

What the Dispo Call URL does

The Dispo Call URL is a per-campaign hook that fires when an agent sets a Disposition on a call. VICIdial takes the URL you configured, substitutes the live call data into it — the Lead ID, phone number, the disposition code itself, and any Custom field tokens you added — and requests that URL (in VICIdial). It's the standard way to push call outcomes into an outside CRM as the agent works.

Because the URL Log Report records each requested URL the system builds, a Dispo Call URL request shows up there as a row with the fully assembled URL. That row is your proof of life.

Step one: check the campaign Dispo Call URL setting

Open the Campaign and find the Dispo Call URL field. Confirm it's actually populated, that the hostname is correct, and that any substitution tokens are spelled the way VICIdial expects. A single mistyped token means the substitution silently leaves a blank where data should be, and your CRM rejects the malformed request without ever telling you.

Step two: confirm the request in the URL Log

Have an agent disposition a test call, then open the URL Log Report for that minute. The flowchart below is the whole decision in one picture.

flowchart TD
  A[Agent sets a disposition] --> B{Row in URL Log Report?}
  B -->|No row| C[Request never built]
  C --> D[Check campaign Dispo Call URL field]
  B -->|Row present| E{URL fully substituted?}
  E -->|Blank token| F[Fix the substitution token]
  E -->|Looks correct| G[Request left the dialer]
  G --> H[Problem is on the receiving end]

No row means VICIdial never built the request — go back to the campaign setting, because the hook isn't firing. A row with an obviously broken URL, like a blank where the Lead ID should be, means a substitution token is wrong. A row with a clean, correct URL means the dialer did its job and the request went out the door.

Step three: test the exact URL by hand

When the logged URL looks correct but the data still isn't landing, copy that exact URL out of the URL Log and request it yourself from a machine on the same network as the dialer. If it works by hand, suspect a firewall or timing issue between the boxes. If it fails the same way, the problem is on the CRM side — wrong endpoint, an auth header it expects, or a field it can't parse. Either way, you've moved the investigation off VICIdial and onto the real culprit.

For the full behavior of this report, read how to read the URL Log Report. When the Dispo Call URL is one piece of a broader integration that's misbehaving, work the VICIdial troubleshooting playbook from the top.

Integration hooks like this need a dialer that's reliably reachable from your CRM. VICIfast runs a managed, hardened VICIdial box on a Branded subdomain over HTTPS, live in under 40 seconds, so your Dispo Call URL fires from a host you can trust. See our plans and pricing.