Lead distribution between reps: shifts, routing, and deals left by people who quit
Omnia Lab is a lead routing system for sales teams, running on top of your CRM — Bitrix24, amoCRM or any other. Leads go by shift, not by round-robin: every lead gets an owner who is actually working today and a clock on the first reply. Manual assignments stay untouched.
· · Author: Dmitry Marenich
A new lead has to reach a specific person who is working right now. Omnia Lab reads your shift schedule from a Google Sheet, syncs it every hour, and routes leads only to reps actually on shift. First a ping with a Take button in the priority chat for new leads. If nobody takes it, the lead is assigned by the schedule. Deals owned by people who left get reassigned every day at 10:00, 25 per run, earliest pipeline stages first. All of it runs on top of the CRM you already use — nothing to migrate.
How does a lead reach a specific rep?
One lead, from the moment it lands in the CRM to the first reply.
- 01
The deal is created
The pickup timer starts here and stops at the first real contact with the customer. Only working seconds count, and the timer caps at 3 days.
- 02
A Take button appears
A ping goes to the priority chat for new leads. Whoever taps Take owns the deal — no roll call, no "should I grab this?"
- 03
Nobody takes it
After the timeout the lead is assigned by the shift schedule to a named person. It also gets its own SLA chain, so it cannot quietly rot.
- 04
The customer is waiting
Escalation ladder: 5, 15 and 17 minutes ping the shared rep chat; 10 minutes goes to the rep's direct messages; at 20 minutes it reaches the manager, both privately and in the managers' chat.
- 05
A reply closes it out
A reply, a call, the "No reply needed" button, or closing the deal clears every reminder. Each new reminder deletes the previous one, so the chat never turns into a feed.
- 06
Leads that arrive overnight
Night escalation steps are cancelled, not postponed. Overnight leads arrive as one digest at 10:05 instead of a dozen separate pings.
Where does the shift schedule come from?
You keep the schedule you already keep. Nothing new to maintain.
- Source
- Your team's Google Sheet.
- Layout
- A matrix: people down the rows, days across the columns, a shift code in each cell.
- Shift codes
- A separate code reference, so the system learns your notation instead of forcing its own.
- Sync
- Every hour. Change a cell and within the hour it governs routing.
- Who gets leads
- Only people on shift, minus anyone temporarily paused.
- Temporary pause
- A rep can be taken off new leads for 2 working hours after a call scored 50 or below. Night does not burn the clock: taken off at 20:00 means back on at 11:00 the next morning. Off by default.
- Last one standing
- If a rep is alone on shift, leads keep coming to them. The customer outranks the penalty.
What happens to deals when a rep quits?
The classic hole: someone leaves, and their cards keep aging under their name.
- 01
Remove them from the directory
Marking a rep as no longer working is the only step you take. The rest happens on its own.
- 02
Every day at 10:00
A reassignment run. Not a one-off on the day they leave — cards surface later too.
- 03
25 deals per run
Nobody inherits an entire pipeline at once. The handover spreads over a few days and stays workable.
- 04
Earliest stages first
Deals where the customer can still be saved move before the ones parked near the finish line.
- 05
Two sources, not one
Deals with message history, and deals created by a phone call with no messages at all. The second kind is what usually disappears.
- 06
Manual assignments stay put
If a manager handed deals out personally, the system leaves those alone.
Why is the rep directory the source of truth?
One list of working people drives routing, reminders, and paid analysis alike.
- A deal with an unknown owner triggers no pings and never goes into paid analysis. No reminders into the void, no spend on people who are not there.
- Every minute the system checks for new deals stuck on the service account and routes them, instead of leaving them until a customer complains.
- Fail-open by design: any failure is resolved in the customer's favor. The lead still gets assigned, the conversation never vanishes, filters switch off rather than hide data.
- Scheduled time off is taken into account in the weekly review, so days a rep was away do not distort their numbers.
- An ignore list covers pipelines and stages where SLA and summaries do not apply.
What goes wrong with lead routing most often?
What we usually find in a sales team before rollout.
- Round-robin that ignores the schedule. The lead lands on someone who is off today and sits there until evening.
- "Whoever sees it first" with no fallback. It works until everyone is busy, which is exactly when it matters.
- A departed rep still holding the pipeline. Cards sit under their name for months while customers wait for a reply.
- Call-created deals nobody watches. With no message thread, they never surface in any chat.
- The service account as a black hole. An integration creates the deal, leaves the owner blank, and that is the end of it.
- Overnight leads landing as a morning avalanche. A pile of pings reads as noise, so it gets read as nothing.
What changed for customers after rollout?
Measured before and after rollout at current customers, including a premium car dealership.
- Median first response
- From 32 minutes to 6.5 minutes.
- Deals with a prepayment
- From 4—7% to 13%.
- Revenue
- +33% in 4 months with no extra headcount.
- Why speed pays
- Responding within an hour produces 7 times more qualified leads than an hour later, and 60 times more than a day later (Harvard Business Review, "The Short Life of Online Sales Leads", 2011, 2,241 companies).
- A second data point
- Cutting the wait from 30 minutes to 5 raises lead qualification roughly 21 times (James Oldroyd, MIT Sloan).
Rollout takes 3—5 days. The free audit takes 3—5 days as well.
What does the system deliberately not do?
The limits matter as much as the features.
- It does not replace your CRM. It runs on top of Bitrix24, and every deal and task stays where it is.
- It does not keep a second schedule. Your sheet is the source, and your manager owns it.
- It does not override deals a manager assigned by hand.
- It does not leave a lead ownerless when something breaks — routing still happens even if some checks fail.
- It does not pull leads away from a rep working a shift alone.
- It does not ping on deals with an unknown owner, and it does not spend money analyzing them.
Частые вопросы
- How do we route leads when reps work in shifts?
- The system reads your shift schedule from a Google Sheet and syncs it every hour. A new lead first goes out as a ping with a Take button in the priority chat. If nobody takes it, it is assigned by the schedule to someone working today. From there it gets its own reminder chain so it does not go unanswered.
- What happens to deals owned by a rep who quit?
- You remove the person from the rep directory, and that is your whole job. Every day at 10:00 the system reassigns their deals — up to 25 per run, earliest stages first. Both sources are covered: deals with message history and deals created by a call with no messages. Manual assignments made by a manager are untouched.
- We assign leads by hand. Does that have to change?
- No. Manual assignment always wins: if a manager handed the deal to someone, the system leaves it alone. Automation picks up what nobody owns — leads with no assignee, cards stuck on the service account, deals from people who left.
- Are call-created deals routed too?
- Yes, and they are a separate source in the reassignment run. They have no message thread, so they never surface in normal chats and are the ones that get lost. On top of that, a check runs every minute for deals stuck on the service account.
- Do we need to switch CRMs?
- No. Omnia Lab runs on top of the CRM you already use. Bitrix24 is the primary integration — deal events, stage robots, tasks, timeline comments, custom fields, pipeline and stage moves — and every scenario on this page describes Bitrix24. amoCRM is among the CRMs we roll out and configure; ask us separately about the scope and timing of that integration. Deals, tasks, comments and custom fields stay exactly where they are.
- How long does setup take?
- Getting a new customer up and running takes 3—4 hours, and full rollout takes 3—5 days. The admin panel holds 85 settings that apply in under 60 seconds with no restart. Each of the 33 modules has its own toggle, so you can run shift-based routing and nothing else.
Read next
- Lead routing by shift: every request gets an ownerHow to stop losing leads at night and on weekends: shift-based routing, first-response tracking, reassigning deals when a rep quits. Free 3-5 day audit.
- How to Manage a Remote Sales TeamHow to manage a remote sales team without spyware: what to track, how to run reviews online, and the risks that only appear when people work from home.
- Sales response SLA: a 5–20 minute ladderReps not answering customers? A response SLA that runs itself: escalation at 5, 10, 15, 17 and 20 minutes plus an hourly unanswered digest.
- Telegram Alerts for Sales TeamsHow to set up Telegram notifications for a sales team: in-chat buttons with permissions, one live alert per thread, separate chats, 20:05 cleanup.
Let's look at how your leads get routed today
A free audit in 3—5 days: we show how many leads go to people who are off shift, how many cards sit under departed reps and the service account, and where the time before the first reply disappears. No strings — if you decide to change nothing, the report is still yours.