How to run a calling team you cannot see: attendance, a live board and daily targets

The old way of managing a calling floor was to stand at the back of the room. If you could see people on the phone, work was happening. Field sales, remote counsellors and multi-branch teams took that away, and many managers replaced it with the worst substitute: constant messages asking for updates. There is a better routine, and it is built on three things the phone can report on its own.

Attendance that means “ready to call”, not “in the building”

Check-in should be a tap on the phone at the start of the working day, with a location attached only when your policy needs it — for a site office or a branch, say. Breaks are typed: lunch, tea, meeting, prayer, personal. Check-out closes the day, and an automatic checkout after a set number of hours catches the people who forget. The point is not surveillance; it is that the live board can show “available”, “on a call”, “on break” and “idle” honestly, and that active time is measured rather than assumed.

Field agents need one more thing: a record of the visits themselves. When they reach a customer, they open the lead and tap Check in; the phone’s location is read once, at that moment, and compared with the location saved on the lead, so the visit shows as “At the location” or as a distance away. Check out adds how it went. The Field visits page then lists each person’s stops for the day in order, with the distances and a link that opens the route in Google Maps — evidence of the work without tracking anyone between stops.

Idle detection is the useful signal: an agent who is checked in, not on a break, and has made no call or CRM action for twenty minutes. Surfacing that to the team lead as a gentle indicator — not an alarm — gets more done than any message in a group.

The live board: one screen that replaces the back of the room

A team lead’s screen during the day should show every agent in a row: status and since when, calls today, connected calls, outcomes logged, overdue callbacks, due today. The data comes from the phones — calls captured from the work SIM, outcomes from the post-call prompt, presence from check-in and heartbeat — so it is true without anyone reporting.

• Sort by overdue callbacks first thing in the morning; those are the promises at risk.
• Watch connected rate, not just call count. Fifty unanswered calls is a number problem or a timing problem, not effort.
• Look at the idle column after lunch; that is when momentum dies.
• Use the board in the stand-up. Two minutes per agent on their own numbers beats twenty minutes of “how is it going”.

Daily targets that agents can actually control

Revenue targets belong to the month. Daily targets should be activities the agent controls entirely: calls attempted, conversations connected, outcomes logged, callbacks kept on time, and one outcome-based number such as visits or demos booked. Keep progress visible where the agent already looks: LumaKol’s Home shows today’s calls, connected calls, talk time and follow-ups due, and the leaderboard ranks the team — agree the day’s numbers in the stand-up and let people watch themselves get there.

Ranges vary by industry; the shape does not. Set them with the team, not for the team, and revise them monthly from the actual distribution.

Coaching from evidence

Once calls are captured, coaching stops being opinion. Pick two recordings a week per agent — one good, one where the call was lost — and review them together for ten minutes. Compare outcome mix between agents on the same lead source; if one agent’s “Not interested” rate is double the team’s, the leads are not the problem. Look at connected rate by hour and move the calling window if the team is dialing when customers do not answer — the best-time-to-call heatmap in Reports → Coaching shows the answer rate for every weekday and hour. Score a few calls a week on a simple scorecard there too, so feedback is consistent from one review to the next.

Doing this without breaking trust

Remote management fails when agents feel watched rather than supported. Tell the team exactly what is captured (calls on the work SIM, outcomes, check-in state) and what is not (personal SIM, messages, location at any time other than a check-in — the day’s attendance check-in if your policy asks for it, and the check-in and check-out of a field visit). Show them their own numbers first — the same board the manager sees — so nothing is a surprise. Use the data to remove friction, such as reassigning a stale queue or fixing a lead source that never answers, and the team will keep it honest.