How to read the Caller ID Log Report to see which CIDs you've burned

If your answer rate slid this week and nothing else changed, the numbers you dial from may be the cause. The Caller ID Log Report gives you a breakdown, by caller ID, of calls from chosen campaigns and statuses inside a date range. Its whole purpose is to show which caller IDs a campaign has used so you can control them better — in plain terms, to see which of your numbers are burned.

What "burned" means

A CID (caller ID) is the number that shows on the called party's screen. Dial too many calls from one number and carriers start flagging it as Spam Likely label, so fewer people pick up. That is a burned number. The fix is rotation: spread your volume across many caller IDs so no single one gets hammered. To rotate well, you first have to see which numbers you have already leaned on — and that is exactly what this report shows.

Setting up the report

You pick the Campaign or campaigns, the call Disposition statuses you care about, and a date range. The report then lists each caller ID with its call counts. Most fields are standard, but one deserves attention:

• Log Second Diff — the maximum number of seconds difference allowed between the call_date in the vicidial_log table and the call_date in the vicidial_dial_log table for records with matching lead IDs to count as the same call. Set it too tight and one real call shows up as two; too loose and unrelated calls merge.

That field exists because the same call is recorded in two tables a fraction of a second apart. The diff is how the report decides those two rows are one event tied to the same Lead. Leave it at the default unless your counts look obviously doubled or obviously merged — then nudge it and re-run. Getting the diff right matters because every conclusion you draw about a number's usage rests on the report counting each call once.

From counts to a rotation plan

flowchart TD
  A[Run Caller ID Log Report] --> B{Any CID over-used?}
  B -->|Yes| C[Mark it for rest / retire]
  B -->|No| D[Spread looks healthy]
  C --> E{Answer rate dropping?}
  E -->|Yes| F[Add fresh CIDs to rotation]
  E -->|No| G[Keep monitoring weekly]

Sort by call count. Any caller ID carrying a wildly larger share than the rest is your candidate to rest. Pull it from active rotation, let it cool, and add fresh numbers so the campaign keeps its spread. Run the report weekly and over-use never sneaks up on you. The pattern to watch for is a number that climbs steadily week over week while its share of answered calls slides — that gap between volume and results is a burning number, caught early. Compare the same date range against last week's run so a single busy day does not read as a burned number when it is just normal variation.

Where to go next

To see how individual calls from a given caller ID actually ended, pair this with the Dial Log Report, which lists the outbound caller-ID per call. If the calls connect but get rejected fast, the Hangup Cause Report may show a pattern. The troubleshooting playbook ties these together.

VICIfast gives you a clean managed dialer where rotation and reporting just work — live in under 40 seconds. See plans and pricing.