How to read the Outbound Lead Source Report

The Outbound Lead Source Report answers one question: which batch of leads is actually producing calls and results? It breaks down call counts and their statuses for every list inside a campaign over a time period you choose. Instead of opening one list at a time and squinting at the numbers, you get a single view grouped by where the leads came from. That makes it the report to reach for when you want to judge a feed, a vendor, or a particular upload rather than a whole campaign at once.

What it groups by

When you run the report you pick how the rows are grouped. The two choices are vendor_lead_code and source_id, and the choice is yours each time you run it. Both are fields you set when you load leads, so they tell you which feed or supplier a Lead came from. The report does not invent these tags. It only groups by what you put on the records, which is why the value of this report rises and falls with how carefully you tag your loads.

• source_id is a per-batch tag you assign at load time, so it is the cleanest way to mark a particular upload or feed.
• vendor_lead_code is the supplier reference that often arrives in the file itself, so use it when each row already carries its origin.

Either way, the grouping is what makes this a Lead source report rather than a plain list report. It pulls every list in the campaign together and rolls the numbers up by the tag you chose, so a single source that happens to span three lists still shows up as one clean row.

What the columns tell you

Each row is one source, and the columns are the call counts split by status. A status here is the same thing the dialer records on every attempt, so you will see the Disposition outcomes your agents pressed plus the system results like no-answer or busy. Reading across a row shows how a single source behaved: how many calls it generated, how many connected, and what those connected calls turned into. Reading down a column lets you compare the same outcome across every source at a glance.

How the report aggregates

flowchart TD
  A[Pick campaign and date range] --> B[Choose grouping source_id or vendor_lead_code]
  B --> C[Scan every list in the campaign]
  C --> D[Bucket each call by its source tag]
  D --> E[Count calls per status in each bucket]
  E --> F[One row per source with status columns]

The report walks every list in the Campaign, drops each call into the bucket for its source tag, then counts the statuses inside each bucket. That is why a source can span several lists and still show as a single row, and why two feeds with the same tag are impossible to tell apart once they are loaded.

Where it fits

This is a focused cut, not a dashboard. For the wider picture of dial volume and outcomes start with the outbound calling report, then come here to see which sources are carrying the load. For the full set of dashboards and how they connect, the reports overview maps everything out. Used together they tell you both how much you dialed and where the good leads were hiding.

Clean source tagging is the difference between guessing and knowing where your results come from. On a VICIfast box every list and lead field is yours to set however you like, and a server is live in under 40 seconds. See our pricing to get started.