The other day I’m talking to an owner. Team of 26 in Kommo, sales down for the second month. I ask: what’s going on with the people? He answers, confident: “They work, on the phone from morning till night, I can see it.” And I’m looking at his own pipeline — and I see something else. Deals frozen. Conversations cut off mid-sentence. Week-old leads nobody has even opened.
Here’s the catch. He doesn’t see. He believes. And those are not the same thing.
In an office a manager at least reads the room: who is at their desk, who stepped out, whose phone never cools down. On a remote or CRM-based team there is none of that. There is the result at month’s end — and your faith in whatever happened underneath it. The gap between “my rep works” and “I think my rep works” is the hole sales departments fall into.
Why the result never tells you what happened
A result is a lagging signal. It lights up when it’s already too late. And it never explains itself.
A deal has been stuck in “Negotiation” for three weeks. What does that tell you? Nothing specific. Maybe the rep is lazy and isn’t calling. Maybe they call every day but can’t close. Or maybe they call, and they can close — the lead was never yours, the person was never going to buy. Three different causes. And the fix for each is the opposite: fire one, coach the second, and for the third do nothing to the rep at all, because what’s broken is marketing, not the person.
From the result alone you can’t tell them apart. You’ll guess. And usually you’ll punish the wrong one.
And one more uncomfortable number. Across sales research, a rep spends roughly 30% of the workday actually selling — the rest is eaten by messaging, filling in cards, internal calls, “oh, got distracted.” So “on the phone all day” and “selling all day” are not the same thing at all. And from the result you will never separate that 30% from the other 70%.
What it means to see the real work
“Seeing the work” is not counting calls. Calls are easy to count, which is exactly why they get gamed. Seeing the work means having in front of you everything the rep actually did in the system that day.
And here is what they did: called, ran chat conversations, wrote notes on deals, moved them across stages, filled in fields. Those are active actions — at least somewhat visible. But there is also an invisible half: the rep simply opened a deal and is studying it. Reading the conversation history. Pulling up old notes before a call. Preparing.
And here is the important part. A call counter doesn’t catch that half at all. To it, the person who spent half a day carefully working through a million-dollar deal is “a slacker, zero calls.” When they may be the only one doing real work today. Quiet work is still work. Any monitoring system that doesn’t understand this punishes your sharpest people and rewards your loudest.
Activity Panel — a widget for Kommo — is exactly that “person sitting next to you.” It takes a daily snapshot: for each rep, an activity track from 00:00 to 24:00, where you can see which minutes they actually did something and which minutes the system was dead. Green — working. Red — silence. And the total: how many hours of real activity added up that day.
Look at this through a manager’s eyes. You don’t need to count anything — you see at once whose day is dense and whose entire “busyness” is ninety minutes of activity smeared across the screen.
What actually matters here is three things, and not one of them is “how many calls”:
- Density of the day. How many hours of real activity added up, and how they’re spread. A steady green band is a working day. Three green bursts against red is “checked email three times.”
- Did the customer reply. Activity met with silence on the other side is a monologue. Ten outbound messages into a dead thread aren’t worth one exchange where the customer answers.
- Is the deal moving. You can log forty touches on a deal cemented in one stage for three weeks. Touches are not movement.
And now, with the real activity in front of you, you can finally ask the right question.
The three reasons there is no result
The right question is not “did they work?” but “why, given this work, is there no result?” And there are exactly three answers. They fold into a simple matrix — activity against result.
| What the snapshot shows | Diagnosis | What to do |
|---|---|---|
| Almost no activity. One real hour out of ten. Half the screen red. | Not working. A discipline problem, not a skill one. | A conversation. If that fails, part ways. There is nothing to coach here. |
| High activity, no result. Twelve green hours and the deals stand still. | Working in vain — a sales-skill problem. Talking, not selling. | Coach the close. Review calls, work the scripts. (A separate widget for this is shipping soon.) |
| High activity, the effort is right, and the deals still die. | Not the rep. The leads are wrong — a sourcing problem. | Fix marketing and the lead sources, not the rep. |
See the point? On the surface all three look identical — “no sales.” But the causes are opposite, and so are the actions. Without the activity layer you can’t tell them apart and you swing blind: you fire the one you should have coached, coach the one with bad leads, and fix marketing where the person is simply lazy.
The activity snapshot turns “no sales” from a verdict into a diagnosis. And a diagnosis you can treat.
A case from practice
A client’s team, 14 people, sales down two months straight. The owner had already decided who to cut: the quiet one, Maria — “sits there, says nothing, barely any calls, clearly not pulling her weight.” We open the snapshot. And Maria’s day is dense green: every morning she spends an hour working through the big deals, pulling up history, prepping targeted messages. Few calls — because she isn’t hammering everyone in sight, she’s working the large accounts. Two of her deals were sitting in the final stage at serious sums.
And the two “loud” ones the owner praised — their screens were half red. Activity flaring up right before he checks the reports. Theater. The exact kind.
If they’d cut by gut feeling, they’d have fired the one person actually working and kept two actors. The snapshot flipped the decision 180 degrees. Maria stayed; three weeks later she closed both deals. The “loud” ones got a different conversation. The moral is simple: quiet doesn’t mean lazy, and loud doesn’t mean useful. You can’t tell by eye. You can tell by the numbers, in a minute.
This isn’t spying on people — it’s transparency of the work
This is usually where the objection comes: isn’t this surveillance, gross. Let’s sort it out, because the difference is fundamental.
Surveillance is screenshots of the screen every five minutes, keyloggers, a webcam, a “time-at-the-monitor” counter. That really is toxic. And, more importantly, it doesn’t work. Per Visier, 43% of employees spend more than 10 hours a week on performative work — on looking busy. And the harder you watch, the more of that theater you get. Around 74% of employers have already switched on some kind of digital tracking (2025 data), and more than half of employees are willing to quit over excessive monitoring. You push — they perform. It’s a dead end.
Activity Panel looks the other way. Not at the person — at the work product inside Kommo. Not “how long you sat at the screen,” but “what showed up in the system”: called, wrote, moved a deal, worked a lead. This isn’t peeking through a keyhole. It’s the work that’s happening anyway, made visible — it’s just that on a remote team you can’t see it at all without a tool.
And the key move here is honesty. Tell the team plainly that activity in the CRM is visible, and why it’s needed. Oversight that people know about and that’s tied to a clear purpose is accepted calmly. Covert surveillance is not. An employee who feels trusted, by the same research, works about twice as productively. So this isn’t about clamping down — it’s about stopping the guessing and starting to see.
And one more thing: you’re paying for ghosts
There’s a side effect that pays for the widget before any management even starts. Money.
Every seat in Kommo costs money. And on any team of 20-plus there are seats with zero activity for weeks. Someone left and was never deactivated. On the roster but never logs in. Added “just in case.” You see those seats only on the invoice — and you pay for them every month without a second thought.
The same transparency that diagnoses the people also finds money on the floor. One follows from the other: if you can’t see the activity, you can’t see that you’re paying for emptiness either.
What it looks like day to day
No “sit down and analyze for half a day.” Monday morning, the manager opens the dashboard and reads the picture in a minute.
- The workload traffic-light. The widget sorts the team itself: who is in range (green), who has spare capacity (amber), who is overloaded (red). No counting by hand — the first-level diagnosis is already done.
- The activity tracks. Run your eye down — whose day is dense, whose ninety minutes are smeared across ten hours. A red screen is obvious at a glance.
- The three-reason matrix. For the ones with no result, sort each into their cause and act on it — not on your mood.
One honest detail to close on. If the traffic-light shows “zero in range,” that’s an alarm too, not a victory. It means the team is working unevenly: someone idle, someone overloaded, someone simply not logging anything in the system. An empty green is not the same as a healthy green. The snapshot shows that too.
From there it’s Activity Panel inside Kommo, a daily snapshot of real actions, and the habit of looking instead of believing. A team that works outside one office can’t be held together any other way — more on that in the piece on the remote sales department. And first-response speed, where “why the lead went cold” so often begins, is caught by SLA First Touch Control.
So the question isn’t whether you trust your reps or not. It’s simpler. Do you actually know what they did today?