Reply clocks & handover trail
Every Wasla chat has a reply clock: a reminder, then a move to the next Ready teammate, then the team lead is told. Every handover stays on the record.
Team performance
Wasla's reports count what the customer felt: how long they waited for a person. Per salesperson, per channel, per day and hour, with the moves and handovers that explain the numbers.
The reply-time report shows the median first reply per person and for the team, the share of chats answered within your target, how many chats Wasla moved because nobody replied, and when in the week replies are slowest. Time is counted in working minutes, and automatic messages never count as a reply.
For the team and for each person, in working minutes, over the period you pick. A trend line shows whether this week is better than last.
The share of chats whose first human reply came within your target, out of all chats that were answered or are already late. Late chats still waiting are counted, not hidden.
How many chats moved to someone else because the owner did not reply in time, and from whom. One or two on a visit day is normal; twenty is a conversation to have.
Chats and median first reply by day and hour, so you can see that Thursday evenings after a campaign are where replies slow down and adjust the shift.
Per person: leads received through rotation, how many were contacted, and how chats were closed (with the reasons your team chose).
Every Sunday a car dealership's sales manager opens the last 7 days. The team median is 6 working minutes, 84% within the 10-minute target. One person, Tamer, has a median of 4 minutes but 11 chats moved by the clock, all on Friday evening, when he was alone on shift and a campaign was running. The answer is not a warning to Tamer; it is a second person on Friday evenings. The hour view confirms it: Friday 6 to 9 p.m. is the slowest slot of the week. The manager adds a shift and checks the same view the following Sunday.
Each person can see their own numbers, and every number links to the chats behind it. A slow reply because the customer wrote at 11 p.m. is not counted against anyone, and a chat that moved shows exactly why. That makes the review a discussion about facts rather than impressions.
From the customer's first message to the first reply sent by a person on your team, counted in working minutes based on your business hours. Automatic welcome messages are shown but not counted.
Because a few very late replies distort an average. The median shows the typical customer's wait; Wasla shows the late chats separately so they are not hidden either.
Yes. Managers can see the team; each person can see their own figures and the chats behind them.
Yes. The per-person table downloads as a CSV file, so you can keep it with your own sales numbers.
The demo workspace has a week of sample chats, so you can explore the report before connecting anything.