Difference between revisions of "Messages"
(9 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | Messages are components used to configure the agent's | + | Messages are components used to configure the virtual agent's replies. |
[[File:message.png|600px]] | [[File:message.png|600px]] | ||
− | Messages | + | Messages contain a text that will be used as the main response. If the channel is callcenter the text will be vocalized. |
− | Each message can also have a media url that will be sent together with the text. | + | Each message can also have a media url that will be sent together with the text. Configure the media url in the bottom right corner of each text variant. |
You can create multiple text variants from which the agent will select a random one by pressing the "Add new" button. | You can create multiple text variants from which the agent will select a random one by pressing the "Add new" button. | ||
+ | |||
+ | To insert user session data like extracted entities in a message use the syntax {{<entity name>}}. E.g. "Salut {{nume}}!" | ||
For text based channels the agent will also send a list of suggestion that will be displayed above the keyboard. | For text based channels the agent will also send a list of suggestion that will be displayed above the keyboard. | ||
Line 15: | Line 17: | ||
The action list is useful for the call center client and other custom clients. By example when implementing a native app custom client using the API integration you can send custom actions to the client that can trigger certain business logic, like turning on the flash. | The action list is useful for the call center client and other custom clients. By example when implementing a native app custom client using the API integration you can send custom actions to the client that can trigger certain business logic, like turning on the flash. | ||
− | + | ||
− | *Stop | + | System actions: |
− | *Redirect:<phone_number> | + | *Stop - close phone call |
− | *Hold | + | *Redirect:<phone_number> - redirect phone call |
+ | *Hold - hold phone call | ||
+ | *keyboard-input:<number of characters> - enable keyboard input for phone call | ||
+ | *only-keyboard-input:<number of characters> - enable keyboard input for phone call | ||
+ | *assign_to_wisevoice_crm / assign_to_wisevoice_crm:[department] / assign_to_zendesk_crm / assign_to_facebook | ||
+ | *hide-chat-input-console - hide text input for chat | ||
+ | |||
+ | Other special syntax: | ||
+ | *[pause:<float seconds>] | ||
Other channel specific settings are available in the tab dedicated to that channel. | Other channel specific settings are available in the tab dedicated to that channel. | ||
+ | |||
For example the Callcenter channel have extra settings for handling silences with no user input. | For example the Callcenter channel have extra settings for handling silences with no user input. | ||
Checking the Template list checkbox will cause the suggestions to display vertically on facebook. | Checking the Template list checkbox will cause the suggestions to display vertically on facebook. | ||
''Other message templates are coming soon.'' | ''Other message templates are coming soon.'' |
Latest revision as of 07:46, 23 May 2022
Messages are components used to configure the virtual agent's replies.
Messages contain a text that will be used as the main response. If the channel is callcenter the text will be vocalized.
Each message can also have a media url that will be sent together with the text. Configure the media url in the bottom right corner of each text variant.
You can create multiple text variants from which the agent will select a random one by pressing the "Add new" button.
To insert user session data like extracted entities in a message use the syntax {{<entity name>}}. E.g. "Salut Template:Nume!"
For text based channels the agent will also send a list of suggestion that will be displayed above the keyboard.
The action list is useful for the call center client and other custom clients. By example when implementing a native app custom client using the API integration you can send custom actions to the client that can trigger certain business logic, like turning on the flash.
System actions:
- Stop - close phone call
- Redirect:<phone_number> - redirect phone call
- Hold - hold phone call
- keyboard-input:<number of characters> - enable keyboard input for phone call
- only-keyboard-input:<number of characters> - enable keyboard input for phone call
- assign_to_wisevoice_crm / assign_to_wisevoice_crm:[department] / assign_to_zendesk_crm / assign_to_facebook
- hide-chat-input-console - hide text input for chat
Other special syntax:
- [pause:<float seconds>]
Other channel specific settings are available in the tab dedicated to that channel.
For example the Callcenter channel have extra settings for handling silences with no user input.
Checking the Template list checkbox will cause the suggestions to display vertically on facebook. Other message templates are coming soon.