The four numbers worth measuring on a telecalling team

Every calling floor watches call count, and it is the one number that can be raised without doing more work. Four measures describe a day properly, and reading them in the right order tells you whether a slow week was a lead problem, an effort problem or a conversation problem.

1. Talk time, first

Talk time is the total minutes spent in connected conversations. It matters most because it resists gaming: you cannot manufacture minutes without somebody on the other end talking to you.

Read it per caller and per day. Two to three hours of connected conversation in a full day is a strong figure for outbound work, though the number that matters is your own team over time rather than any benchmark. A caller whose talk time drops for a week is either getting worse lists or having worse conversations, and the next two numbers say which.

2. Connect rate, to judge the list

Connect rate is answered calls divided by attempted calls. It is a diagnostic, not a performance measure, because the things that move it mostly sit outside the caller control: how old the list is, which source it came from, the hour of day, and what number appears on the customer screen.

Track it per source. A source whose connect rate declines month on month is going stale, and no amount of effort on the calling floor will fix numbers that no longer answer. Track it per hour as well: most teams find a clear pattern and can reorganise the day around it for free.

The largest single lever on connect rate in India is the number being dialed from. Ordinary mobile numbers are answered materially more often than virtual ones, and that gap has widened as caller-ID apps have spread.

3. Outcome mix, to see whether anything happened

A day of long conversations that moved nothing is a different problem from a day of short ones. The outcome mix is the count of calls by lead status change: how many moved forward, how many were told no, how many need a callback.

This is the number that turns a management conversation from an accusation into a question. Instead of asking why only ninety calls were made, which invites a defensive answer, the useful question is why eleven interested leads from yesterday have no follow-up date, which invites a specific one.

4. Call count, last

Call count is context. Read after the other three it is useful: high volume with low talk time means the list is not connecting or the calls are being ended quickly; low volume with high talk time means long conversations, which may be excellent or may be an inability to close.

Read first, or worse read alone, it drives exactly the behaviour you do not want. A team managed on dials will produce dials.

A target set that does not backfire

If you need targets, set them as a pair rather than a single number:

• A talk-time floor, for example two hours of connected conversation.
• An outcome expectation, for example every interested lead leaves the day with a follow-up date.

Then publish call count and connect rate as information rather than as targets. Teams managed this way tend to make slightly fewer calls and considerably more money, because nobody is rewarded for hanging up.

Speed to first call, the fifth number

One more is worth watching even though it is not a caller measure: the minutes between a lead arriving and its first call. For most businesses it predicts conversion better than anything on the list above, and it is fixed structurally rather than by effort, by making lead sources live and assignment automatic.

Telodial reports all of these as a by-product of the calling: talk time, connects, outcome mix, call count and assigned-to-first-call delay, per person and per source, with the caller own remarks attached to the numbers. Nobody writes a report, which also returns the reporting hour at the end of the day. The detail is on the call analytics page.