Team performance

Know who answers fast, measured from the customer's side

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.

  • WhatsApp
  • Instagram
  • Messenger
  • Facebook lead ads
  • Website form
  • 14-day trial
  • No card needed
  • Arabic and English

The short version

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.

Why the usual numbers mislead

  • Averages hide the problem. Nine replies in two minutes and one in nine hours "average" to about an hour, which describes nobody. Wasla shows the median and the late ones separately.
  • Bots make everyone look fast. If a welcome message counts as the first reply, every team has a perfect score.
  • Night messages punish the morning shift. Counting clock hours makes the first person in the office look slow for messages sent at 2 a.m.
  • Activity is not outcome. Number of messages sent says little; replies within target and close reasons say more.

What the report shows

  1. Median first 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.

  2. Answered within target

    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.

  3. Chats moved by the clock

    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.

  4. Weekday and hour view

    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.

  5. Received, contacted, closed

    Per person: leads received through rotation, how many were contacted, and how chats were closed (with the reasons your team chose).

Workflow example: the Sunday review

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.

Fair to the salesperson too

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.

Questions people ask

How is first reply time measured?

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.

Why median and not average?

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.

Can salespeople see their own numbers?

Yes. Managers can see the team; each person can see their own figures and the chats behind them.

Can I export the report?

Yes. The per-person table downloads as a CSV file, so you can keep it with your own sales numbers.

See the report on sample data

The demo workspace has a week of sample chats, so you can explore the report before connecting anything.