Skip to main content

Enabling voice and data transfer for Pega Call

Suggest edit Updated on March 16, 2021

Customer Service Representatives (CSRs) can transfer a call to another CSR along with the associated interaction and call data using voice and data transfer. When you transfer a call with the associated interaction, the associated service cases are also transferred.

Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide
Before you begin:

Ensure that Pega Call is installed, configured, and connected to a Customer Telephony Integration (CTI) platform that supports adding call data elements to a call.

Voice and data transfer supports both warm and blind transfers.

To transfer a call, ensure that the target CSR is logged into the same portal and use the same navigation method. Do not use integrated voice data transfer for transferring a call to parties who do not use Pega Customer Service. If the CSR to whom the call is transferred does not use Pega Customer Service, the interaction and service cases will remain open in the transfer work basket.

Save all changes before initiating a transfer. During the transfer, if unsaved changes are present in the interaction, a pop-up message is displayed with OK and Cancel buttons. Clicking the OK button transfers the interaction without the unsaved changes.

  1. In the navigation pane of App Studio, click SettingsPega CallDevice capabilities.
  2. Select the Enable integrated voice data transfer check box.
What to do next: You can set a time limit for voice and data transfers. If no CSR accepts the transfer within the time limit, the transferred call and interaction are returned to the CSR initiating the transfer. For more information, see setting a time limit for voice and data transfers.Note: If you are using a custom review harness, you need to include the PegaCA-Work.CPMWarmTransferAcceptButton rule in the harness to enable the Open button. The Open button lets recipient CSRs open transferred interactions in the perform harness.

Transfer reasons

When transferring a call with its associated interaction, a Customer Service Representative (CSR) selects a reason for the transfer.

By default, a CSR can choose from the following transfer reasons:

  • Escalate to supervisor
  • Customer needs additional services
  • Customer routed to wrong queue
  • Other

You can configure additional transfer reasons and set transfer reason availability for interaction channels. For instructions, see Configuring transfer reasons.

Setting a time limit for voice and data transfers

You can configure a time limit beyond which calls and interactions awaiting transfer are moved back to the Customer Service Representative (CSR) initiating the transfer.

When a CSR initiates a voice and data transfer for a call and its attached interaction, the transfer waits to be accepted by a different CSR. To shorten the time customers wait for assistance, you can configure a time limit after which the call and its interaction return to the CSR who initiated the transfer.

Pega Call provides a job scheduler, called ReassignToTransferor, which sets the default time limit for voice and data transfers to 15 minutes. You can enable that job scheduler and modify the time limit.

  1. In the navigation pane of Dev Studio click RecordsSysAdminJob Scheduler.
  2. Click the ReassignToTransferor job scheduler.
  3. Click the Enable Job Scheduler toggle to switch on the job scheduler.
  4. Modify the time limit for voice and data transfers in minutes in the After every field.
  5. Set the Long running job scheduler threshold to the value of your time limit in milliseconds.
  6. Click Save.
Result: If a transferred call is not accepted by another CSR within the set time limit, it returns to the CSR who initiated the transfer.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us