Lead rotation
Wasla rotates new leads and chats between the salespeople who are Ready, in turn, and skips anyone busy, away or full. Every assignment and handover is recorded.
Reply clocks & handover trail
Speed is the one thing a salesperson fully controls. Wasla times the wait from the customer's side, reminds the owner, moves the chat on when time runs out, and keeps a plain record of who had it and why it moved.
A lead writes in. Here is what Wasla does if nobody answers. The demo runs one minute per second.
Hana Adel
Hi, is the 2-bedroom in New Cairo still available?
A reply clock is a timer that starts when a customer writes and stops when a person from your team answers. In Wasla, the default target is 10 working minutes for the first reply and 30 for later replies. If the owner misses it, the chat moves to the next Ready person, who gets their own full time. After two moves, the team lead is told. You can change every number.
The clock starts from the customer's message, counted in working minutes. A message at 11 p.m. starts counting when your working hours begin.
Before the deadline, the owner gets a reminder in Wasla. The chat shows how long is left, in plain numbers.
If the owner has not replied, Wasla moves the chat (and its lead) to the next Ready teammate. The new owner gets the full target time on their own clock, not the leftovers.
After the maximum number of moves (two by default), the team lead is notified so a person decides what happens next.
When you are waiting for the customer, or the chat is closed, the clock stops. Automatic welcome messages do not stop it: only a reply from a person counts.
Every chat and lead keeps a timeline in plain sentences: "Arrived on WhatsApp at 14:02 and went to Mona (rotation)", "Moved from Mona to Omar at 14:12: no reply within 10 min", "Taken over by Heba (team lead)", "First reply at 14:15 by Omar". Anyone allowed to see the lead sees the same story. There are no hidden reassignments and no arguing over whose lead it was.
Saturday is visit day, and three of five salespeople are walking clients through units. Reply targets are 10 minutes. A WhatsApp lead about a 3-bedroom flat arrives at 12:20 and goes to Ahmed, who is with a client and does not see it. At 12:27 he gets a reminder; at 12:30 the chat moves to Nour, who is at her desk and answers at 12:32. The trail shows the move and the reason. Ahmed is not punished by a manager's memory; the report simply shows one missed clock on a visit day, and the customer got an answer in 12 minutes instead of waiting until Ahmed finished his tour.
A timer per chat that counts how long the customer has waited for a person from your team. Wasla uses it to remind the owner and, if needed, move the chat to someone available.
No. Wasla measures the first reply from a person. Automatic messages are shown in the chat but do not count as a reply.
No. Clocks count working minutes based on your business hours, so a message sent at night does not turn red before the office opens.
The clock is visible to the salesperson first, with a reminder before anything moves. Most teams find it fairer than the alternative: a manager's impression of who is slow.
You can set how many moves are allowed. Setting it to zero keeps the clock and reminders, and tells the team lead when time is up.
Start a 14-day trial or open the demo workspace to see clocks counting on sample chats.