Reporting on Sales Calls: The Few Numbers That Matter
Which reports a phone sales team really needs: activity, outcomes, speed to first call, pipeline health and loss reasons, and how to read them honestly.
Sales call reporting has a habit of growing until nobody reads it. Managers add a chart for each anxiety, the dashboard fills up and the numbers that matter are lost among the rest. A better approach is to decide the decisions you make each week, then choose the smallest set of numbers that informs them. This guide gives a practical set for a phone sales team, and warns you about the ways they can mislead.

It is the last piece in the CRM series, after Designing Pipeline Stages for Phone Sales and Logging Calls in a CRM Without Slowing Agents Down; reports are only as good as what those two produce. For general contact-centre numbers see Call Center KPIs and Outbound Call Metrics.
Five groups of numbers
What to report on
- ActivityCalls made and answered, talk time and call attempts per contact.
- OutcomesHow calls ended: interested, callback, sale, not interested, voicemail, wrong number.
- SpeedHow long new leads wait for a first call, and which were never called.
- PipelineDeals by stage, value, weighted forecast and stale deals.
- LossesWhy deals were lost, ranked by value, and to whom.
Each group answers a different question. Activity says whether people are doing the work. Outcomes say whether the work is landing. Speed says whether leads are being treated promptly. Pipeline says what is likely to happen. Losses say what to change.
Activity and outcomes: read them together
Activity numbers alone are dangerous. A target for calls made encourages short, hurried calls. A target for talk time encourages long ones. Read activity beside outcomes: how many calls reached a person, how many led to a next step and how many resulted in a sale. A rep with fewer calls but more next steps may be doing better work than one with many calls and few results.
- Connect rate: calls that reached a person out of calls made.
- Conversion from connection to next step or sale.
- Average call length and its spread; very short and very long calls both deserve a look.
- Attempts per contact before reaching them, to refine your retry rules.
A number and the question behind it
| What it shows | What to ask | |
|---|---|---|
| Many calls, few connections | Lists or timing may be poor | Is the list clean? Are we calling at good hours? |
| Many connections, few next steps | Calls may lack a clear purpose | Are we asking for the next step? |
| Short average calls | Rushing or poor targeting | Listen to a sample |
| Long average calls | Thoroughness or drifting | What is happening in the extra minutes? |
Speed to first call
If you track only one new number, make it this one. Speed to lead is the time from a lead arriving to the first call. It is easy to measure, easy to act on and often reveals leads that were simply never called. Report the median and the count never called. Share the list of never-called leads daily, since each one is a lost chance that can still be rescued.
A delay is not always the rep's fault. It may reflect the routing rules, the staffing at the time or a lead that arrived outside hours. See Routing New Leads to the Right Person for the process side.
Pipeline and forecast
A pipeline report lists deals by stage with counts and values. A weighted forecast multiplies each open deal's value by the probability of its stage. It is useful for comparing weeks and seeing direction, but it is an estimate based on your own assumptions, not a promise. Pair it with stale deals: those that have stayed in a stage longer than expected. A long list of stale deals often says more about the real health of the pipeline than the forecast total.
A weekly pipeline review
- Look at new leadsHow many arrived, how fast were they called?
- Check outcomesWhat did last week's calls produce?
- Review stale dealsWhich deals need a push, help or closing?
- Read the forecastIs it rising or falling, and why?
- Decide actionsWho does what before next week?
Losses: the most useful report
Teams love to count wins, but losses teach more. Record a reason whenever a deal is lost, from a short list, with an optional competitor name. Rank the reasons by deal value. If price leads the list, ask whether it is really price or poor explanation of value. If timing leads, is a nurturing plan missing? If a competitor appears repeatedly, listen to the calls against that competitor. Deals closed lost with no reason are a gap in themselves, so track the count.
Making reporting a routine
The best report is the one that is discussed. Pick a regular slot, such as fifteen minutes on Monday, and walk through the same five groups in the same order. Ask the same questions each time: what changed, why, and what will we do about it? Over a few weeks people learn the numbers, spot odd results quickly and start to fix the underlying data themselves.
Share the reports with the agents, not just the managers. When people can see their own results and the team's, in a form they understand, they are more likely to trust the figures and to tell you when something looks wrong. Keep a short note of decisions made from the numbers; it shows whether the reporting is earning its keep.
Traps to avoid
- Measuring what is easy rather than what matters.
- Targets so tight that people game them, for example by logging fake calls or chopping calls short.
- Comparing agents without allowing for their lead quality or territory.
- Showing percentages from tiny samples as if they meant something.
- Reports no one has a meeting to discuss.
Reporting review
- Each report linked to a decision
- Data comes from normal work, not extra entry
- Activity read beside outcomes
- Speed to first call and never-called leads visible
- Stale deals listed
- Loss reasons ranked by value
- Reports reviewed in a regular meeting
- Unused reports removed
Reporting in Call
Call has several places for these numbers. On the Revenue page under Campaigns, four tiles at the top show the weighted forecast, renewals within sixty days, speed to lead and stale deals, with a ranking of loss reasons by value once deals have been marked lost with a reason. The tabs are Forecast, Quotes, Contracts, Leads and Data hygiene. The Leads tab shows the median minutes from arrival to first call over the last thirty days and a table of the most recent leads. The figures are built from your contacts' stages and deal values, so they show only what your team records, and a contact with no deal value adds nothing to the forecast.
On Home › Reports, the Agents tab compares each agent's calls, connect rate, conversion, talk time, average call and quality score for the last thirty days, with the spread of call lengths. The Report builder lets you group by items such as agent, campaign, queue, outcome, day or hour and measure calls, connected calls, sales, talk minutes, average duration or revenue over seven to 365 days, then export a CSV. Reports can be saved, shared with your organisation and scheduled by email; the emailed summary carries this month's totals for calls, answered, abandoned, handle time and sales. The Call history can be exported as a spreadsheet too.
Frequently asked questions
How many reports does a sales team need?
Usually five groups: activity, outcomes, speed to first call, pipeline and losses. More can be added when a real decision needs them.
What is the most useful single number?
Speed to first call is easy to measure and act on. Pair it with the count of leads never called.
Is the weighted forecast reliable?
It is an estimate built from your own stage probabilities. Use it to compare periods and spot trends, not to promise income.
Should I set call-volume targets?
Be careful. Volume targets can push people to rush. Read activity beside outcomes and look at the calls themselves.
How do I compare agents fairly?
Allow for lead quality, territory and shift pattern, and look at samples of their calls as well as numbers.
Why record loss reasons?
They show where deals leak. Ranked by value, they point to what to change in script, offer or lead source.