You are here: Conversational user channels > Configuring the Facebook channel > Facebook chatbot configuration > Configuring Facebook chatbot text analyzer definitions

Configuring Facebook chatbot text analyzer definitions

The Facebook chatbot configuration for a Pega Intelligent Virtual Assistant includes a list of text analyzer definitions. Text analyzer definitions are used for advanced text analysis to process user input and determine the best matching response. The definitions are based on natural language processing (NLP).

In the advanced configuration you can specify several text analyzer definitions to provide a better response to users. User input is analyzed by using the first text analyzer definition in the list, and if no match is found, the second text analyzer definition in the list is used, and so on, until a response match is found.

For each text analyzer definition you can also specify whether to run it within the context of a case, outside of the context of a case, or both. For example, if you have a case that allows users to buy airline tickets, you can specify to run a text analyzer definition within the context of a case so that when the chatbot asks the user about when to book the flight, the response is automatically converted to a specific date.

Note: You must purchase a separate license before using Pega Intelligent Virtual Assistant in your application. You must also obtain and install the Facebook channel component from Pega Exchange.

You can add, delete, or modify each text analyzer definition in the list.

  1. In Designer Studio, click the name of your application and click Channels and interfaces.

  2. Click a Facebook channel interface.

  3. Click the Behavior tab.

  4. In the Text Analyzer section, click Edit intents.

    1. Click + Add intent.
    2. Fill out the following fields:

      • Intent - Required. The command for the chatbot to use as the response, the expressed intent of a user. The command is based on user input that corresponds to a value in the must match or the approximate match field.
      • Must match - Optional. User input that is an exact match as the intended command. For example, for an initial greeting response, you can specify 'hi'.
      • Approximate match - Optional. User input that is an approximate match as the intended command. For example, for an initial greeting response, you can specify: 'hello' or 'good morning'.
      • Never match - Optional. User input that must never match the intended command. For example, for an initial greeting response, you can specify 'bye'.
    3. Repeat steps a and b to define additional intents.
    4. Click Submit.
  5. Optional: Select the Use advanced configuration check box. A list of defined text analyzers is displayed.

  6. Click Save.