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.

Creating a Unified Messaging channel

Updated on June 1, 2023

Expose your essential business services to users through a chatbot on multiple messaging platforms by defining a single Pega Intelligent Virtual Assistant™ (IVA) for Unified Messaging. As a result, you provide users with additional ways to communicate with your application, which improves the overall user experience.

For example, you can create an IVA for a travel agency application. As a result, customers can instantly book their flight by interacting with your chatbot on Apple Messages for Business, Facebook Messenger, and other messaging platforms.
Note: Due to changes by Twitter in the API and the licensing model, direct integration with Twitter is no longer supported in the Unified Messaging channel interface.
Before you begin: Configure Unified Messaging channel security settings. For more information, see Configuring Unified Messaging channel security.

You can define custom IVA responses to fit the business needs of your organization and to extract the intent of users with natural language processing (NLP), decisioning, and text analytic capabilities. In the preview console, you can test whether the configured Unified Messaging channel works correctly before moving the channel to a production environment.

  • A chatbot works in one language because the conversational channel uses a template operator that is defined for a single locale. For more information, see Template operator for IVA channel.
  • After you update Pega Platform or Pega Customer Service, to use the latest Digital Messaging Manager features, save your existing Unified Messaging channel.
  1. Create a new channel interface in Pega Platform:
    1. In the header of Dev Studio, click the name of the application, and then click Channels and interfaces.
    2. In the Create new channel interface section, click Unified Messaging.
    3. In the Details section, in the Channel interface name field, enter a name for your channel.
    4. Optional: To describe the purpose of the channel, in the Description field, enter a short description of your IVA.
    5. In the channel, click the Connection tab.
    6. In the Template operator ID list, click the name of an existing Pega Platform operator to use as a template.
      The system uses this operator as a template to create all further accounts. Each account has a unique channel identifier set as its ID. The selected operator must at the minimum have the PegaRULES:User4 access role, taking into consideration the application settings, for example, providing access to the application's cases. For more information, see Template operator for IVA channel.
    7. Click Save.
  2. Configure a Unified Messaging channel for a social messaging platform:
    You configure specific settings for a social messaging platform on the Connection tab using Digital Messaging Manager that is displayed on a separate page.
For example:

The following figure shows the settings for a Unified Messaging channel:

Settings for a Unified Messaging channel.
The configuration settings for a Unified Messaging channel on the Configuration tab.
What to do next: Define conversational channel behavior for the IVA, for Unified Messaging. For more information, see Defining conversational channel behavior.
  • Previous topic Implementing an Intelligent Virtual Assistant for a conversational channel
  • Next topic Setting up the IVA for Apple Messages for Business

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