Reply speed for property leads
For property sales teams in Egypt and the Gulf: reply to new leads within minutes during working hours, set a clear rule for nights, and measure it weekly.
Use round robin when your salespeople have similar workloads and you want everyone to get the same number of new leads. Use least busy when workloads differ a lot, so nobody drowns while someone else is idle. In both cases, the rules around the method (only people who are ready, a cap per person, and moving a lead on when nobody replies) decide whether it feels fair.
Round robin hands out new leads in a fixed order: Ahmed, then Mona, then Karim, then back to Ahmed. Each person gets the same number of new leads over a day, whatever happened to the previous ones.
Least busy (sometimes called load-based routing) looks at how many open leads or chats each person has right now and gives the new one to whoever has the fewest. Over a day, people who close or hand off quickly receive more new leads.
Round robin does not look at workload. If Karim spent the morning on three long site visits and still has twelve open conversations, he gets the next lead anyway. The lead waits, the customer waits, and Karim looks slow even though the system put him in that position.
It also ignores people who are not there. A plain round robin will happily give a lead to someone on leave unless you exclude them by hand.
Least busy rewards people who empty their list, and a list can be emptied the wrong way: by closing leads too early or passing them on. If someone closes conversations without a real outcome, they will be sent more new leads. That is why closing should ask for a reason, and why managers should look at outcomes and not only at counts.
It is also harder to explain. A salesperson who gets fewer leads than a colleague needs to see why: their open count was higher at the moment each lead arrived.
Some teams send a new lead to everyone who is ready and give it to the first person who replies. It can be very fast during busy campaigns. The risks are that the same quick people take most leads, and that customers sometimes receive two openings at once if the tool does not lock the chat on the first reply. Use it when speed is everything and the team agrees to it openly.
Teams often argue about round robin versus least busy when the real problem is one of these rules:
Start with round robin, Ready status and a cap. Run it for two weeks and look at two numbers per person: open leads at the end of each day, and reply time. If open lists stay roughly equal, keep round robin. If some people are always far above the others and their reply times suffer, switch to least busy.
Whatever you choose, show the rule to the team. In Wasla the Distribution settings show who is next in line right now and who is being skipped and why (not ready, at their cap, outside shift). When people can see the rule working, they stop suspecting it.
It is a rule that gives each new lead to the next salesperson in a fixed order, so everyone receives the same number of new leads over time.
It gives each new lead to the salesperson with the fewest open leads or conversations at that moment, so workload stays balanced.
Round robin is fairer on the number of leads; least busy is fairer on workload. Most teams find either method fair once leads skip people who are not ready, each person has a cap, and late leads move on.
Yes, if your tool supports pools. In Wasla you can send leads from specific channels or campaigns to a team and rotate inside it.
Usually not. Keep managers out of the rotation and let them take over a chat when needed; the takeover is recorded.
The live demo has a sample team; switch the distribution rule and see who would get the next lead.