V3 Queue scalability
For the above reasons, we recommend you to follow the important best practices here below:
1. Do not to associate more then 50 queues to each agent. If you really need to overcome it, please consider very high processing consumption.
2. Remove the old queues you do not use anymore. This is very important: we often see customers adding new queues and associating it to the agents, without considering to remove the queues no more in use. Remember that any kind of not used queues associated to an agent will also mean waste of processing resources!Â
3. Carefully add new queues to the agents only when you really need it. Having an agent managing calls for 200 queues does not make a lot of sense, even in terms of contact center design management and monitoring.
IMPORTANT: if you only need the agents to be able to differentiate the incoming calls for each different services or DID, please consider not to add one queue for each service, but use instead the XCALLY variables to send such information inside the Agent phonebar pop-up.
If you use XCALLY MOTION, please just follow the simple Trigger guide to customize your Motion phonebar pop-up with the values you need.
Furthermore use the Templates to customize the pop-up content. In the following screenshot, you can see a very simple template example in order to show the Caller, queue and the DID inside the agent pop-up!