Sales KPI dashboard for a calling team: the 8 tiles you need and 4 ways to build it

In short

A calling team's dashboard needs eight tiles: call attempts, connect rate, conversations, meetings booked, meetings per conversation, meetings held, calls per meeting and the reasons for 'not interested', filtered by period, campaign and caller. You can build it in a spreadsheet, a BI tool, your CRM or a calling workspace. The hard part is not the chart but getting every call logged the same way, by every caller, every day.

A sales KPI dashboard for a calling team needs eight tiles: call attempts, connect rate, conversations, meetings booked, meetings per conversation, meetings held, calls per meeting and the reasons for "not interested". Each tile can be filtered by period, campaign and caller. Together they show in one look how much was done, where the funnel leaks and why prospects say no. You can build it in a spreadsheet, a BI tool, your CRM or a calling workspace. The chart is the easy part; the hard part is getting every call logged the same way. The definitions behind each tile are in our guide to sales KPIs.

Below: the eight tiles with their formulas, the filters that matter, a layout for one screen, four ways to build it with honest pros and cons, and what Ringlane shows and does not show.

The eight tiles

Each tile answers one question. The full definitions are in our article on cold calling KPIs; here is what goes on the dashboard:

#TileFormulaQuestion it answers
1Call attemptsCount of dialsHow much did we call?
2Connect rateConnects ÷ attemptsDo we reach people? (list, numbers, timing)
3ConversationsCount of real conversations with the right personHow many chances did we create?
4Meetings bookedCountWhat did the calling produce?
5Meetings per conversationMeetings booked ÷ conversationsDoes the message and the ask work?
6Meetings heldHeld ÷ booked (show rate)Were the meetings real?
7Calls per meetingAttempts ÷ meetings bookedWhat does one meeting cost us?
8Reasons for "not interested"Count per reason ÷ all "not interested"What does the market tell us?

Tile 7 is the planning number. Tile 8 is the one most dashboards forget, and the cheapest market research you have; our article on win/loss analysis shows how to read it.

Context lines, not targets

You can show public benchmarks as a thin line next to tiles 2 and 5. In Gong's analysis of more than 300 million cold calls, the average rep reached the prospect on 5.4% of dials and booked a meeting from 4.6% of conversations. For tile 1, The Bridge Group's 2025 survey found a median of 56 dials a day on phone-centric SDR teams. Mark the line as context; your own history per campaign is the real comparison.

The filters that matter

A number without a filter hides more than it shows. Four filters cover almost every question a manager asks:

  • Period: this week, last week, this month. Compare equal periods.
  • Campaign: each list and message is its own test. A team average mixes a good list with a bad one.
  • Caller: compare callers on the same campaign, never across campaigns.
  • Team: for larger organisations or agencies with several client teams. Agencies can use our appointment setting report template for the weekly client report.

Two filters many teams add later: hour of day and attempt number. Hour of day shows when your list picks up; attempt number shows when to stop. In Cognism's 2025 data, 93% of conversations happened within the first three attempts, a good reference for that view.

A layout that fits on one screen

Put effort at the top, conversion in the middle and the people at the bottom. One screen, no scrolling, so the whole team reads it the same way.

RowWhat goes there
Top: effortCall attempts, conversations, meetings booked, meetings held (four big numbers with last period next to them)
Middle: conversionA funnel from attempts to conversations to meetings booked to held, with the rate at each step; calls per meeting
Bottom left: peopleA table per caller: attempts, connect rate, meetings per conversation, meetings
Bottom right: reasonsThe reasons for "not interested", most frequent first

Four ways to build it

Each option trades setup effort against data quality. The cost of any option is mostly the time someone spends keeping it up to date.

OptionSetup effortData qualityBest forWeak spot
SpreadsheetLowDepends on every caller filling it inOne or two callersBreaks when several people edit; no history per call
BI tool on an exportMedium to highAs good as the exportTeams with an analyst and several data sourcesSomeone must refresh and maintain it
CRM dashboardMediumGood for deals, often weak for callsPipeline and revenue viewsCallers log calls late or not at all
Calling workspaceLowHigh, because every call ends with one outcomeCalling teams and agenciesDoes not cover revenue or pipeline value

Spreadsheet

One row per lead or per call, a column with a fixed list of outcomes, and COUNTIFS or a pivot table per caller and week. It is free and fast to start. Our free cold call tracker template has the columns, a download and the signs you have outgrown it.

BI tool on an export

A BI tool such as Looker Studio or Power BI reads exports from your CRM, dialer and spreadsheets and combines them. It gives you the most freedom and the most maintenance. It pays off when you already have someone who builds reports and several systems to combine.

CRM dashboard

Your CRM is the right place for pipeline, deal values and win rates. For calls it is only as good as what callers log in it, and logging a call in a CRM often takes several clicks. That is why call numbers in CRMs are often incomplete; the time it costs is covered in our article on sales time vs admin.

Calling workspace

When callers work from a screen where every call ends with one outcome key, the dashboard fills itself. Data quality is high because logging is part of the call, not an extra task. The limit is scope: a calling workspace covers the top of the funnel, not the deal after the meeting. Our guide to cold calling software explains how the layers fit together.

The real problem: logging

A dashboard shows what was logged, not what happened. Three rules make the numbers trustworthy:

  1. One outcome per call, from a fixed list. Not reached, conversation, call back, meeting, not interested, invalid number. Free text is for notes, not for counting.
  2. Logged during or right after the call. End-of-day logging forgets the unanswered calls, which makes the connect rate look better than it is.
  3. The same definitions for everyone. Write down what a conversation is and what a meeting is, and keep it next to the dashboard.

How often to look at it

Read activity and rates every week, per caller; read outcomes such as meetings held, opportunities and revenue every month. Daily swings on small numbers are mostly noise. Our guide to sales coaching with data turns the weekly read into a 30-minute routine.

What Ringlane shows, and what it does not

Ringlane's reports are the calling-workspace option: every number comes from the outcomes your callers log with one key.

Shown todayPlan
Call attempts, connect rate (share of attempts that became a conversation), conversations, meetings booked, "not interested" with the top reason, the funnel and the split over six outcomesAll plans
The same per caller and per campaign, with open leads per campaign and the reasons for "not interested" from frequent to rarePlus
Per team, and the rhythm: how much calling one new customer per week takes, from your own ratesPro
Export to CSV, one row per caller and campaign, for your own spreadsheet or BI toolAll plans

Not shown today: meetings held, revenue, pipeline value, forecasts and call recordings. Revenue and pipeline stay in your CRM. You can also build your own reports on your own dashboards and click through to the leads behind every number: from Plus a funnel from call attempt to meeting and a leaderboard of callers on booked meetings, and on Pro the best time to call per weekday and hour. Ask Ringlane, an assistant you can ask how a campaign is going, comes from late November 2026. See the roadmap for the status, the interactive demo to click through the reports with fictional data, and the Academy guides to reports and exporting leads.

Frequently asked questions

What should a sales dashboard show for a calling team?
The chain from effort to result: call attempts, connect rate, conversations, meetings booked, meetings per conversation, meetings held, calls per meeting and the reasons prospects say no. Show each number per period, campaign and caller, and keep it on one screen. Revenue and pipeline belong on a second view, fed from the CRM.
Can I build a sales KPI dashboard in Excel or Google Sheets?
Yes. One row per call or per lead, a column with one fixed outcome, and a pivot table or COUNTIFS formulas per caller and week give you every tile on this page. It works well for one or two callers. It gets fragile when several people edit the same sheet or forget to log, which is when a tool pays off.
How often should a sales team review its dashboard?
Activity and rates weekly, per caller, in a short meeting or a 1:1. Outcomes such as meetings held, opportunities and revenue monthly, because they move too slowly for a weekly read. Daily checks are useful for the caller's own activity, but daily rate swings on small numbers are mostly noise.
Which benchmarks can I put next to my dashboard?
Use them as context lines, not targets. Gong's analysis of 300M+ cold calls gives a 5.4% average connect rate and 4.6% meetings per conversation; The Bridge Group's 2025 survey gives 56 dials a day on phone-centric SDR teams. Your own history per campaign is the better comparison.

Sources

  1. Gong Labs: The hidden power of cold calling, insights from 300M calls (18 July 2024)
  2. The Bridge Group: SDR Models, Motions and Metrics 2025 (6 February 2025)
  3. Cognism: The State of Cold Calling in 2025 (online since February 2025)