Collecting data for Avaya Experience Platform™ Public Cloud

Last Updated : Mar 17, 2023 |
Prolog information
Google Dialogflow agents use parameters to collect queue data, attributes, and customer identifiers and pass them to Automation. Google Dialogflow CX parameters are session parameters and can use entity types to identify possible parameter values. When a Google Dialogflow agent ends a conversation, Avaya Experience Platform™ Public Cloud processes the received parameters. The contact center uses the virtual agent configuration on the Store Context tab in Automation to match the collected parameters to queues, attributes, and customer identifiers. For more information about parameters and entities, see Google Dialogflow CX documentation.
If a Google Dialogflow agent is multilingual, the contact center can map the data collected in different languages to the same parameter. You can add synonyms for existing entities in different languages in entity types. For example, an agent that supports English and Spanish receives a queue parameter from a Spanish-speaking caller. The agent defines the "queue" entity type that corresponds to the "queue" parameter. The "queue" entity type has an entity "sales" and its synonym "ventas." When the caller says "ventas", the agent associates it with the "queue" parameter and fills the parameter in with "sales." The agent returns the "sales" parameter to the contact center.
A Google Dialogflow agent can set the parameter value to null with a fulfillment parameter preset to clear a collected parameter and not pass it to the contact center. For more information about setting string parameter values to null and fulfillment parameter presets, see Google Dialogflow CX documentation.