What the ratio measures
Dials per meeting booked tells you how much outbound calling effort one qualified meeting costs, which turns call volume from an activity number into a planning input. Total dials on their own answer nothing about capacity. The ratio answers a direct question: if a rep owes a set number of meetings this month, how many hours of calling does that require.Calculate it over a full period rather than per rep per day, since call outcomes cluster. A rep can book three meetings on Tuesday and none for the rest of the week without anything being wrong.
Break the ratio into its two halves
The ratio hides two separate mechanics, and they fail for different reasons.
| Component | What it measures | What breaks it |
|---|---|---|
| Connect rate | Dials that reach a live person | Bad phone data, wrong call windows, worked-out lists |
| Meetings per connect | Conversations that convert to a booked meeting | Weak opener, wrong persona, no relevant reason to call |
Use it for capacity, not for rankings
The ratio is most useful as a planning multiplier. Multiply the meetings a rep needs by the current ratio to get required dials, then check that number against available selling hours. When the result exceeds what a person can physically do, the gap is a headcount or a list-quality problem, and no activity target will close it.
Feeding this into forecasting matters because meetings booked sit several weeks ahead of pipeline. A ratio that degrades in March shows up as a pipeline shortfall in April and a bookings miss later. Track it alongside pipeline coverage so you see creation risk before coverage drops. Coverage on its own is a lagging view of the same problem, which is why treating a coverage multiple as the answer leaves teams reacting late.
Segment before you compare
Never compare the ratio across segments or titles. Calling a director at a 200-person company and calling a CFO at a 10,000-person company produce ratios that are not comparable, and blending them creates a company average that describes no one. Report the ratio by segment, by persona, and by list source, then set targets inside each. Comparing a rep against their own trailing ratio is a cleaner read than comparing them against the team average.
Frequently Asked Questions
How do you calculate dials per meeting booked?
Divide total dials in a period by the number of meetings booked from those dials in the same period. Attribute the meeting to the channel that produced it, not to the rep's total activity, or inbound and referral meetings will make cold calling look far more efficient than it is.
Should you count voicemails and no-answers as dials?
Count every dial attempt, including no-answers, because that is what consumes rep hours. Then track connect rate separately so you can see whether the ratio is moving because of reach or because of conversation quality. Excluding no-answers makes the ratio look better and removes the signal you need.
What makes dials per meeting booked get worse over time?
List decay is the most common cause. Contact data ages, the best-fit accounts get worked first, and repeat attempts on the same names return less each pass. Persona drift is the second cause: as reps move up-market or into new titles, connect rates drop and the ratio rises even with identical call quality.
Is a lower dials per meeting ratio always better?
No. A very low ratio often means reps are booking meetings with anyone who will take one. Pair the ratio with meeting-to-opportunity conversion and with show rate. Efficient dialing that produces meetings which never become opportunities has moved the cost downstream rather than removing it.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like dials per meeting booked into prescriptive action for your team.
Schedule a Demo