Outbound reporting: the Monday morning dashboard

An outbound dashboard exists to decide what to do this week. If it doesn’t lead to any decision, it costs everyone time and saves nobody any.

That’s the test that should settle every block you add to it: can this number change anything on Monday morning? If the answer is no, it doesn’t belong there.

The four Monday numbers

Four are enough to open the week.

Conversations held last week, per SDR. That’s the volume that matters. Not dials, which measure the machine’s activity rather than the team’s.

The conversation-to-meeting-booked rate. It tells you what your pitch is worth once someone is on the line. It’s the only one of the four you improve by listening back to calls.

Meetings held. Not booked. The gap between the two is a piece of information in its own right, and it’s often the one that explains a disappointing pipeline despite flattering reports.

The state of your lists. How many contacts are still callable, how many are paused, how many are out. It’s the most ignored number and the one that warns you earliest: a team that will run out of list in three weeks knows it right now.

Those four fit on one screen and take two minutes to read.

Compare, but against what

Week-over-week comparison is the only one that really concerns you. External benchmarks don’t measure the same thing you do; we explain why in what an honest cold calling conversion rate looks like.

Two precautions. Annotate the unusual weeks: school holidays, public holidays, a new list, an SDR joining. Without that, you’ll read a week shortened by a public holiday as a performance drop.

And look at the rolling average over three or four weeks alongside the raw number. A single week moves for reasons that have nothing to do with what you’re managing.

What alerts and what informs

Not all numbers have the same status, and mixing the two is what makes a dashboard unreadable.

A number that alerts calls for action this week. A pick-up rate falling steadily over three weeks, for instance: it can come from number reputation or from an aging list, and both get handled right away.

A number that informs helps you understand, not act. The breakdown of rejection reasons falls into that category: useful for preparing a coaching session, but it triggers nothing on Monday.

Put the first kind at the top, the second lower down, and accept that half the screen only gets used once a month.

What stays out

The SDR ranking by number of calls. It pushes people to dial rather than talk, and you see it in the numbers two weeks later.

Team averages without the distribution. An average of twelve conversations a day can hide one SDR at twenty-five and another at three. The average says everything is fine; the distribution says where to step in.

Metrics nobody can influence. If a number only moves with the market or the season, it has no place in a weekly review.

And anything that relies on manual entry. A status filled in at the end of the day reflects the SDR’s memory and their fatigue. Managing on that means managing on self-reported data.

Reliability before presentation

It’s the point most teams handle last, even though everything else depends on it.

A dashboard is only worth the statuses that feed it. Before adding a chart, check three things: that call outcomes come back automatically, that voicemails aren’t counted as pick-ups, and that the definition of a conversation is written down somewhere and applied everywhere.

At Ubic, the duration, outcome and recording of every call come back with no manual entry, and statuses sync with the CRM. The reports show performance per SDR and conversion per list, which is exactly what lets you separate what comes from the team from what comes from the list.

That separation is what makes a Monday review useful. Without it, every drop looks like a team problem.

Frequently asked questions

How often should you look at these numbers?

Once a week to decide, once a month for trends. A dashboard checked every day pushes you to react to noise.

Should you share the dashboard with the SDRs?

Yes, and build it with them. A number the team doesn’t understand or finds unfair changes no behavior; it just breeds distrust.

How many blocks at most?

Whatever fits on one screen without scrolling. Beyond that, nobody reads the bottom, and after six months you’ll find that half of it was never used.

What if the CRM numbers and the dialer numbers don’t match?

Fix it before anything else. As long as the two sources disagree, every meeting gets spent debating the numbers instead of deciding. The cause is almost always a difference in definitions, not a bug.