Skip to main content


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

Configuring common phrases for Augmented agent

Updated on March 16, 2021

To decrease the time needed for a customer service representative (CSR) to respond to common customer questions, and to ensure consistent responses, you can configure a set of common phrases that CSRs can select from and send in their replies.

Pega Customer Service Implementation Guide
Before you begin:
  • Enable common phrases in SettingsChat and messaging Augmented Agent in App Studio.
  • Set the required analytics repository in SettingsPrediction Studio settings in Prediction Studio.
    Note: The repository defaultstore is the default analytics repository. Choosing defaultstore as the analytics repository can result in data loss because it points to a temporary directory. To avoid data loss, choose a dedicated repository.

To help CSRs to more quickly select the most appropriate common phrase, the application groups the phrases into user-defined categories. During an interaction, the CSR clicks the Phrases button, selects from the list of categories, and then selects a common phrase from within that category.

When a CSR is engaged in a live chat or messaging session with a customer, the Augmented Agent suggested replies feature suggests common phrases to the CSR, based on the customer's chat input. For example, if the customer asks for information about their account, the Augmented Agent can suggest a common phrase that includes the requested account information. In addition, the Augmented Agent can be configured to send the common phrase automatically if the confidence level of the response is high.

To set up common phrases more quickly, you can import and export individual common phrases or all of the common phrases that you define.

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.

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

Close Deprecation Notice
Contact us