
Lead Reassignment Rules: Two Timers, Not One
Most teams reassign a lead after "no response in an hour". That one timer counts through the night, measures the wrong event, and quietly recycles leads.
Lead reassignment rules need two timers, not one. The first timer runs in minutes and asks one question: has the rep accepted the lead? The second runs in hours or days and asks a different question: has the lead been updated since? Most small sales teams set a single rule, usually "reassign if no response within an hour", and that single rule measures an event the CRM cannot see, keeps counting through the night, and pushes leads into the recycling loop that kills them.
A single reassignment timer fails in both directions. Set too short, it bounces a lead from rep to rep until nobody owns it. Set too long, it lets an accepted lead sit untouched with no consequence. The fix is an accept timer in minutes that only counts during working hours, an update timer in hours that catches the lead that was accepted and then ignored, and a cap of two reassignments before the lead goes to a manager instead of the next rep.
Why does a single reassignment timer fail?
Because leads die in two different ways, and one timer can only guard against one of them. Across the agency-model sales operations we have worked with, dead leads split into two groups. Roughly eight in ten had been contacted by many different agents, passed around until the buyer was burnt and nobody worked the lead properly. The other three in ten were assigned once, the agent never acted, and nothing happened to the agent. Those are first-hand observations, not a survey, and the second group is the one a short timer is meant to fix. The problem is that a short timer makes the first group bigger.
Think about what "reassign after one hour with no response" actually does. A lead arrives at 11.40am. The rep is on a site visit, sees it at 12.50pm, and the system has already moved it to a second rep, who was in the same meeting. By 2pm the lead has had three owners and zero messages. Each rep assumes someone else has it. The lead is now in the eight-in-ten group, and the timer put it there.
Now loosen the timer to a full day to avoid that. A lead arrives at 11.40am, the rep taps nothing, and at 11.40am the next day it moves on. The buyer has already bought from whoever replied first. That is the three-in-ten group, and the long timer created it.
The HBR study of 2,241 US companies found firms that reached a lead within an hour were nearly seven times as likely to qualify it as firms that waited even one more hour (Harvard Business Review, 2011). That number is why teams reach for a short timer in the first place. The mistake is not the urgency. The mistake is measuring the wrong event with it.
What should the accept timer measure?
The accept timer should measure whether the rep has tapped Accept, not whether the customer has received a reply. Acceptance is the one event the system can see with certainty. A reply to the customer might happen by phone, in a personal WhatsApp, or at a viewing, and the CRM has no idea. A rule written as "no response in an hour" therefore fires on reps who did respond and spares reps who accepted and went quiet.
Vendor documentation across the lead-routing space has quietly converged on this. One real estate CRM describes a time-out window in minutes, ten in its example, inside which the assigned agent must accept before the lead goes to the next person in line (Inside Real Estate help centre). A routing design guide goes further and says assignment and acceptance must be treated as two separate events with two separate timeouts, so a lead never has two current owners (GetEasy routing template). None of them say how long the window should be for a six-person firm in Malaysia, so here is our view.
For a lead from a paid ad, ten minutes during working hours. An ad lead is holding the phone right now and is comparing three suppliers at once. For a referral or a website form lead, thirty minutes. The buyer has already chosen you and is less likely to be shopping in parallel. The exact number matters less than the unit: minutes, not hours.
The second half of the rule is the one teams forget. The accept timer only counts while the rep is on shift. Microsoft's own documentation gives the clearest example of what happens without that. A lead arriving late on Friday under a 48-hour limit expires unassigned over the weekend, while a 60-hour limit would have handed it to the first seller available on Monday morning (Microsoft Learn, Dynamics 365 assignment rules). A timer that counts through Saturday is not measuring the rep. It is measuring the calendar.
What should the update timer measure?
The update timer catches the lead that was accepted and then ignored, and it measures whether anything on the lead record has changed. A stage move, a field filled, a remark added, a message logged. If a rep accepted a lead on Tuesday morning and the record looks identical on Wednesday morning, the lead is not being worked. That is the three-in-ten failure, and the accept timer cannot see it because acceptance already happened.
Set this one in working hours, not calendar hours, for the same reason as above. A 24-working-hour update timer means a lead accepted at 4pm on Friday is checked at 4pm on Monday, not at 4pm on Saturday. A rep who takes a lead at 9am and does nothing all day will hit it the next morning. That is the right amount of pressure. It is not a punishment. It is a promise to the buyer that someone is actually on it.
What happens when the update timer fires is the part that separates a healthy rule from a recycling machine, and that is the next section.
| Rule | Single "no response" timer | Accept + update timers |
|---|---|---|
| Event measured | A reply nobody can verify | Accept tap, then any record update |
| Unit | Usually 1 hour, flat | 10-30 minutes, then 24 working hours |
| Counts overnight? | Yes, by default | No, paused outside shift |
| Rep on a site visit | Loses the lead | Keeps it if accepted from the car |
| Accepted then ignored | Never caught | Caught next working day |
| Reassignment cap | None | Two, then manager |
How many times should a lead be reassigned?
Twice. On the third timeout the lead goes to the owner or sales manager, not to the next rep in the queue. A lead that has timed out with two different people is telling you something about the lead or the team, and a third rep will not fix either. One helpdesk vendor's routing allows up to seven reassignments before the lead finally stays with the last agent (Freshdesk custom routing). Seven owners is not a routing rule. It is the recycling loop with a number on it.
This is where the two-timer rule and why recycled leads never convert meet. Every automatic reassignment is a small withdrawal from the lead's patience. The accept timer should rarely fire if reps are on shift and notifications work. The update timer should fire occasionally, and the cap keeps either from spinning.
There is one more honest shortcut: let reps reject. A rep who taps Reject on a lead they cannot serve gives it back in thirty seconds. A rep who cannot reject sits on it until the timer takes it, and that costs the buyer the full window. Rejection is not a failure signal. Silence is.
Frequently Asked Questions
How do you set lead reassignment rules up in practice?
Start from the two events, pick the units, then decide where a timed-out lead goes. Here is the sequence we walk new teams through.
How to Set Up Lead Reassignment Rules in 5 Steps
Take a six-person renovation firm in Puchong running Facebook lead ads. Two reps are on site visits most of the day, two work from the showroom, and the owner closes the big jobs. Under a flat one-hour rule, the site-visit reps lose almost every lead that lands before lunch, so they stop trusting the system and start asking the showroom reps to "hold" leads for them in a group chat. Under the two-timer rule, a site-visit rep accepts from the car in a minute, the update timer gives her until the next morning to log the call, and the showroom reps only receive her leads when she genuinely does not respond. The group chat workaround disappears, which is the real sign the rule is working.
What does this look like in Raion HUB?
In Raion HUB, reassignment is a setting on each lead source, not a workflow you have to build. You choose round-robin or shotgun per source, narrow it by up to three dropdown fields such as branch or product, and then set two conditions: reassign when the lead is not accepted in time, and reassign when the lead is not updated in time. Each member has their own working hours and holidays, so a lead only routes to people who are on shift, and the clock does not run against someone who is off.
Reps see an Accept and a Reject button on every assigned lead, which is what makes the accept timer honest. The dashboard shows accepted, rejected and timed out per person, which is the Monday review in the Steps above without a spreadsheet. And the activity log records every stage, field and owner change with who made it, whether a person, the AI or an automation, so when a lead has had three owners you can see exactly when and why.
Lead Assignment is included from the Core plan. Working hours and the Duty Scheduler sit on Max, so if the on-shift pausing is the part you need, that is the plan to compare on the pricing page. If your team is small enough that the owner is still the dispatcher, the stale leads Monday check is the manual version of the update timer and a good place to start before you automate it. And if you are not yet sure whether round-robin or shotgun is right for your rotation, round-robin vs shotgun covers that choice on its own.
For the wider picture of capture, assignment, follow-up and reporting, the lead management system guide is the parent to this post.
The bottom line
One reassignment timer cannot guard against both ways a lead dies. Put an accept timer in minutes on the event the system can see, put an update timer in working hours on the lead that was accepted and ignored, pause both outside each rep's shift, and cap reassignments at two before a manager steps in. The lead stays with one person long enough to be worked, and never with a person who is not working it.


