Skip to content

SDR dashboard: what to show, and what to leave out

What belongs on an SDR dashboard — activity, conversations, meetings booked and held, per rep and per client — and how to keep it honest instead of busy.

Updated 8 October 20264 min readTypeGuide
dashboard · this monthlive

Activity

1,842

calls · emails

Conversations

214

real person engaged

Booked

41

meetings

Held

33

8 no-show / moved

SDRClientBookedHeldHeld / hr
Ricky R.Northgate Ltd12101.4
Hannah P.Bluefield Labs1191.2
Owen T.Northgate Ltd981.6
Maya L.Corvid Systems960.9
Illustrative example — sample data, not a customer screenshot.

An SDR dashboard shows whether outbound work is turning into meetings — per rep, per client and for the team. Most dashboards fail in one of two ways: so much activity that nobody can see the result, or results assembled by hand that are already a week old.

The four numbers that matter

Read them as a chain, left to right:

  1. 1

    Activity

    Calls, emails and LinkedIn touches. Necessary context, never the goal.

  2. 2

    Conversations

    Touches where a real person engaged. This is where messaging is tested.

  3. 3

    Meetings booked

    The SDR's direct output.

  4. 4

    Meetings held

    What the meeting is actually worth, after no-shows and cancellations.

High activity with few conversations is a list or messaging problem. Plenty of conversations with few bookings is a qualification or offer problem. Bookings that do not hold is a confirmation and reminder problem.

Per rep, per client, per hour

Per rep

Shows who needs coaching and who needs a better list.

Per client

Each client sees their own numbers, and only theirs.

Per hour worked

The fair comparison between full-timers, part-timers and freelancers. Hours exclude holidays and absences.

Keep the dashboard honest

  • Use the record, not a copy. A dashboard built from an exported spreadsheet drifts from the real data.
  • Show outcomes openly. Dropping no-shows from the total looks better for a month and costs trust after that.
  • One definition per metric. Write down what a “conversation” and a “held meeting” are, and use it for every rep and client.

Live dashboards instead of weekly reports

Weekly report

  • Answers last week’s questions
  • A bad list is discovered on Friday
  • Clients ask for an export to check delivery

Live dashboard

  • Shows today’s numbers from the same records the team works in
  • A team lead fixes the list on Tuesday
  • Clients check delivery themselves in the portal

In Dialbrew the dashboards, the client portal and the invoices all read from the same records, so the numbers match by construction. See also SDR KPIs and metrics and outbound SDR.

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

One booked meeting pays for an SDR's seat for the month.

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run