When a company receives many calls at the same time, it is important for the manager to understand whether they have enough employees on the line to process the entire flow of incoming calls. For this purpose, in Queue Monitoring, you can track all current calls (active, in queue, on hold, in IVR), as well as the employees’ preoccupation and call processing quality.
Queue Monitoring helps to detect problems with call processing both at the company level and at the level of individual employees and, if necessary, to make adjustments to the call route or assign additional employees to overloaded departments.
The For today section displays summary data on all calls for the current day (from 00:00 to 23:59). Each metrics answers the key questions of the manager:
If you are not satisfied with the results of the calls for today, figure out what exactly is wrong — one glance at the Now section is enough to understand:
There is no need to reload the page to get the call data — the metrics on the monitoring page are automatically updated every second.
Using the Calls by departments and employees section, you can understand where the problem with call processing came from and how to solve it best.
In the Employees table, you can see for each employee whether they are talking on the phone at that moment or not. If they do, then with whom and for how long.
To learn more about how to access online listening and call whispering and how to use this feature, read the Online Listening and Call Whispering article.
You can compare employees in the For today tab. Here you can see for each manager:
The load of incoming calls to each department changes not only every day, but also every hour, and is not always predictable. But with constant call queue monitoring you can equally redistribute workload between departments and efficiently process incoming calls during peak periods, even with a small team of employees.
For detailed instructions on enabling and setting up monitoring, as well as on how call efficiency metrics are calculated, see the article.