Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Optimizing queue traffic by adding customer service representatives

Updated on September 10, 2021

In Pega Customer Service, the Contact Center Managers can add customer service representatives (CSRs) to busy queues to balance the workload in the queues. For example, if the Technical queue in the contact center is experiencing high traffic with a limited number of CSRs handling the incoming conversations, the manager can address this situation by adding more qualified CSRs to the queue.

The application provides monitoring tables, such as the Queue monitor and CSR monitor, for the managers to use to monitor the occupancy of each queue and the availability of each CSR. Managers can use these tables to determine when to add a CSR to a queue based on the level of activity in each queue and the availability of qualified CSRs.

  1. Log in to the Customer Service application as a manager.
  2. In the header of Dev Studio, click Launch web interface > Interaction portal.
  3. In the left navigation panel, click Manager Tools.
  4. In the Queue monitor section, identify the highly occupied queue that needs extra CSRs to manage the work, and then click the Manage CSRs button for that queue.
  5. To add a CSR, in the CSRs who can join the queue section, click Add.
  6. To add more CSRs to the queue to balance the workload among the CSRs, repeat step 4.

The customer service representatives are added successfully to the queue.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us