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.

Configuring follow-up settings for inactive chats

Updated on September 10, 2021

Configure the Chat Follow-up settings to track and wrap up inactive chat sessions. If a customer stops sending chat messages to a customer service representative (CSR) in a chat session for a configurable amount of time, you can send customizable reminder messages to both the customer and the CSR. You can configure automatic termination of the chat if it remains inactive for more time after sending the reminder message.

To configure the settings, complete the following steps:

  1. In the navigation panel of App Studio, click Settings > Chat and messaging.
  2. Click the Configuration tab.
  3. Select the Chat follow-up check box.
  4. To define the time in seconds that the application should wait before sending a reminder message to the customer, enter the number of seconds in the Reminder after NN seconds of no response from customer field.
  5. In the CSR reminder message field, enter a reminder message for the CSR.
  6. To define the inactive time in seconds after which the application must terminate the chat, enter a value in the Wrap up after NN seconds of no response from customer field.
  7. In the CSR wrap up message field, enter a wrap up message for the CSR.
  8. Click Save.
  • Previous topic Step 6: Configuring and deploying the web chatbot
  • Next topic Upgrading chat functionality to Pega Customer Service 8.2 and later

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