Friday, 9:40 PM. A new inquiry drops into Kommo from your website. Hot — the person is comparing you against two competitors right this minute. And formally it even has an owner. Except that owner is the account admin, who does not work deals.
Or it is Sergey, who already has three hundred deals dumped on him. Hundreds of notifications a day — he stopped looking at them long ago. Meanwhile the other reps sit with an empty bell. Same result: nobody picked the inquiry up. Monday morning the sales lead digs it out from twenty others, calls — and gets a polite "thanks, we went with another company."
Sound familiar? Here is the thing. It is almost never about a lazy rep. And almost never about the deal having "no owner" — it almost always has one. The trouble is it is the wrong one. The inquiry sits with someone who will not get to it, while the people who could answer never even know it exists. I am going to show you why this is the most expensive hole in your sales team, and how to close it in Kommo or amoCRM in a single evening.
The short version, if you are pressed for time:
- A deal almost always has an owner — the problem is it is the wrong one: the admin or one buried rep. The one exception is the Unsorted/Incoming stage.
- Notifications go to the owner. Wrong owner → the signal lands on someone who won't react, while free reps never see the deal.
- You distribute leads for speed of reply, not for "fairness" of workload.
- According to Lead Response Management (Harvard Business Review), replying within the first 5 minutes makes you roughly 21 times more likely to qualify the lead than replying at 30.
- Two ways to hand them out: by schedule and by "online" status. The first is the plan, the second is the reality.
- For remote teams, floating shifts and evening inquiries, you need an online-routing widget, Peresmenka.
Why distribute leads in a CRM at all
In any CRM, whether Kommo or amoCRM, every deal has one field that matters most. The owner. One rep the inquiry is glued to. And here is the core myth. People assume inquiries get lost because they have "no owner." They almost always have one. The question is who it is.
Here is how it works. Notifications in a CRM do not go "to the department." They go to the owner. New lead comes in, the owner pings. Customer writes in chat, the owner again. A task falls due, the owner once more.
Now — where it breaks. When you connect your website, chats or telephony, the default owner is often the admin or the account holder — whoever set up the integration. They do not work deals. And a pile of inquiries quietly stacks up on them, untouched. Or the whole flow dumps onto one "duty rep" — buried so deep that hundreds of notifications become background noise and he stops noticing them. Meanwhile the other reps sit with an empty bell.
The result is the same: the deal is formally parked, but the actual sellers do not see it. The signal went to the wrong place. The one spot where there really is no owner is the Unsorted/Incoming stage — inquiries the system has not tied to anyone yet. That is exactly where distribution should start.
Lead distribution is the process that immediately puts the right owner on the inquiry. Not the admin, not the forever-busy Sergey, but whoever is on the line right now and will pick it up. It takes the deal from Unsorted (or pulls it off the dumping-ground default owner) and hands it to a live rep. Without that, your CRM turns into a pretty pile of contacts nobody touches.
Remember one thing: in a CRM it is not the "sales department" that reacts, it is a specific owner. If that owner is the admin or one buried rep by default, the notification goes nowhere and the free reps never know about the deal. Lead distribution exists for exactly one reason — to give every inquiry the right owner within a second, someone who is on the line and will pick it up.
Why this is about speed, not fairness
Plenty of people think distribution is "to keep it even." So Masha is not working for three while Pete coasts. That is useful, but it is a side effect. The real reason is speed. According to Lead Response Management (Harvard Business Review), replying within the first 5 minutes versus 30 makes you roughly 21 times more likely to qualify the lead.
21 times. Not 21 percent. Twenty-one times over.
Sit with what that means. The window in which a customer is hot and willing to talk is measured in minutes. Not hours. An inquiry that sat with the wrong person even until morning is already close to a corpse. You already paid the ad platform for it, and you will get nothing back.
And here comes the second trap, the question of when people actually leave inquiries. According to Blazeo (2026), more than four in ten inquiries arrive in the evening and on weekends. Which is precisely when the office is shut and the shift roster is drawn up as "nine to six."
Now the most important turn. According to LeanData, a slow reply is more often a routing problem, not a lazy-rep problem. The inquiry simply never reached someone who could answer. There was no mechanism to deliver it to a living human right now.
This changes everything. When a sales lead sees a speed failure, they reflexively start prodding people. Stand-up lectures, threats of fines. But the problem is not in the people. It is in the pipes the lead flows through. Fix the pipes, not the driver.
Two ways to hand out leads
There are essentially two ways. And the difference between them is like a train timetable versus the arrivals board reading "arrived / delayed." One shows how it should be. The other, how it actually is. According to LeanData, it is exactly the gap between plan and reality that eats most of your reply speed. Let us take both apart.
Method one: by shift schedule
Simple and clear. You write out in advance who is on shift and during which hours. Nine to one, Masha. One to six, Pete. Leads in those windows fly to whoever "should" be in their seat. Often you bolt round-robin onto this too: inquiries go around in a circle, in turn.
The upside is obvious: predictability. You plan coverage ahead, you see your grid, you know who answers for what. For a steady office it runs like clockwork.
But there is a catch. A schedule is the plan, not the reality. Masha went to lunch. Got sick. Got stuck on a call with a big client. And leads keep raining down on her by the roster. And they pile up. The system thinks she is in her seat when she is not. Inquiries accumulate on a person who is physically off the line.
Method two: by "online" status
Here the logic flips. The inquiry goes not to whoever "should" be on shift on paper. It goes to whoever is actually on the line right now. Open the CRM, hit "I'm working," and you get leads. Close the laptop, walk away, and the flow shifts to your colleagues in an instant.
This is our widget, Peresmenka. It holds a live mirror of who is connected right now. It hands incoming inquiries to those people only, and does it evenly. And the key part: the second a rep goes offline, their fresh leads get reassigned to whoever stayed.
No inquiries left dangling on someone who walked out. The lead always lands in hands that can pick it up. This is distribution by reality, not by roster.
Schedule vs online: side by side
To keep it straight, let us put both methods in one table. The difference is fundamental: the schedule answers "who should be working," online answers "who is working in fact." According to Blazeo (2026), more than 40% of inquiries arrive outside standard hours, so real coverage is not a small thing, it is half the result.
| Criterion | By shift schedule | By "online" status |
|---|---|---|
| Logic | The lead goes to whoever should be on shift per the roster | The lead goes to whoever is actually on the line now |
| Response to "out of action" (lunch, sickness, day off) | None. Leads pile up on the absent rep and sit as dead weight | Instant. The flow moves to online colleagues, leads get reassigned |
| Coverage in the evening, on weekends, across time zones | Weak. Gaps wherever the schedule is not drawn | Strong. Whoever logs on at any hour catches the inquiries |
| What it needs from the team | Schedule discipline, someone to maintain the roster | Honest "online / offline" status marking |
| Who it is for | A small office with firm working hours | Remote teams, floating shifts, part-timers, mixed zones |
| Main risk | Plan diverged from reality, the inquiry died on an absent rep | A rep forgot to mark their status (cured by a reminder in the widget) |
Which method fits whom
There is no universal answer, the choice depends on how your team is built. According to LeanData, the rise in reply-speed failures almost always tracks with a more complex department structure: remote work, mixed zones, part-time. The more complex the team, the worse the schedule loses to online. Let us go type by type.
A small office with firm hours. Everyone sits in one room from nine to six. A schedule or a simple round-robin is enough here. Inquiries go around in turn, the load stays even, and everyone is in plain sight, if someone steps out, the neighbor picks it up by hand.
Remote work, mixed time zones, floating shifts, part-timers. This is where the schedule falls apart. One person in Lisbon, a second in Almaty, a third logging on for a couple of hours in the evening. You cannot draw that as a roster. You need online, which means Peresmenka, handing leads out by actual presence.
High volume and night inquiries. Here a hybrid works best: online plus explicit shifts. Shifts set who should be covering the night today. And online is the safety net, handing leads to whoever actually logged on and never letting them fall into a void.
And this is the part to grasp. Often the choice is not "either/or." Shifts and online answer different questions. The schedule says who should be on the line. Online says who is on the line in fact. Peresmenka joins the two: you plan the shifts and immediately see which of the planned people are really working, and only they get the leads.
What if nobody is on shift at all
This is the moment almost nobody closes. And it is critical: according to Blazeo (2026), more than 40% of inquiries arrive in the evening and on weekends, exactly when the roster might not have a single living soul "on shift." Two scenarios here.
How it goes badly. An inquiry lands at 11 PM. The system dutifully assigns it by the schedule to the "duty rep," who has long been asleep. The notification flies into the void. The lead sits as dead weight until morning. And by morning the customer has already placed the order with a competitor who answered automatically in thirty seconds.
How it should go. The lead is not assigned into the void. It joins a queue and goes to the first person who logs on. Or an auto-reply catches it right away: "Thanks, we're back from the morning, here are answers to common questions in the meantime." The customer feels heard. And does not run.
And here is the strongest move. Nights and weekends are exactly where it pays to bring in AI. At minimum for first-touch: a bot replies instantly, asks a couple of qualifying questions, and writes the answers straight into the deal card. The customer is happy — answered in seconds, not in two days. And in the morning the rep opens the deal, instantly sees what it is about, and picks it up at full speed. The lead is neither cold nor lost. Which AI actually fits this (and where it is overkill) — we break it down in Kommo Salesbot vs an AI agent.
The rule is simple: never assign a lead to someone who is not there. If the shift is empty, the inquiry should wait in a queue and go to the first person who logs on, not hang on someone asleep. Peresmenka does exactly that: it queues incoming inquiries and hands them out the second someone appears online.
This is the difference between "we slept through the customer" and "we caught them first." And it costs you one correctly configured widget.
You distributed — now measure the speed
Say leads now land on the right people. How do you know they actually reply fast? You don't — until you measure it. "We feel responsive" is not a number. And remember: 5 minutes versus 30 is 21 times.
So the second layer after distribution is measuring first-touch speed: how long from the inquiry arriving to the rep's first reply. Per lead, per rep, with overdue flagged. Then distribution stops being blind — you see whether the inquiry reaches a human and whether they react in those exact minutes.
That is what SLA first-touch control does — it counts response time against working hours, sends preventive alerts, and creates tasks when a deal is about to go stale. Distribution delivers the lead; SLA makes sure nobody sleeps through it.
So which widget do you need
If you have read this far, you already know more than half the sales leads out there. A default owner is a silent hole. Speed wins by 21 times. The schedule is the plan, online is the reality.
For online distribution in Kommo and amoCRM you need Peresmenka. It holds a live mirror of the team, hands inquiries only to those actually on the line, and never lets leads stall on people who left. Want to push reply speed down to minutes? Look at first-touch speed control (SLA) as well. And if your team is distributed, here is the breakdown on building a remote sales department on Kommo.
One last question for you. Right now, as you read this line, are your new deals piling onto one person while the rest of the team sits with no notification at all?