When the user confirms to close the conversation in a language and switch to another language |
You are now conversing with the bot in the <language-name> language. |
When only field prompt is present in the oob |
This is a field prompt message for action and alert tasks. This is only for the Kore platform to use. Enterprises should not be changing this. As part of the next deployment, this will be hidden from the bot developer. |
When language preference is set |
Shown when the user switches language using cheat lang or picks a language from the options shown. |
When task is not accessible to user |
Shown when the developer tries to access a bot task for which they do not have access |
User confirms alert setup |
Applicable to Alert Task Only
This response is displayed when an alert is set up successfully and the bot will trigger the task at the given frequency or specified time. |
User discards/abandons the current activity |
Shown in the following cases:
1. When a user ends the task by saying discard
2. When a task ends on exceeding max tries at an entity or choices not available in an LoV, or a cURL problem in an HTTP request, etc. |
User implies to end the conversation (For example, good night, bye, ttyl) |
This condition occurs only for Dialog tasks for which the following Follow-up Tasks Setting is configured: Yes, at the end of this dialog ask the user to select and perform a task from the Follow-up task list in the Dialog settings. The bot shows this message when it presents the Follow-Up Intents array to the user at the end of the Dialog. |
Location provided by user is invalid for a field in an action |
This message is displayed when the Bot is not able to validate the user input for a Location type of entity. |
Amending an Alert field |
Applicable to Alert Task Only
When setting up an alert, the end-user needs to provide values for the parameters that the alert needs along with the frequency at which the alert will be triggered. If the developer specifies that the alert should confirm all values from the user before setting up the alert, the bot will display an option to the user if he wants to amend the values.
This bot response is displayed if the user says Yes to amend |
Amending a task which has no fields |
Applicable to Alert, Action and Information Task
The standard confirmation message in case of Action, Alert and Information task ends with an option to amend entities. In case the task does not have any entities (Fields) then this message will be shown. |
Ask at least one optional field |
Applicable to Action Task Only
Under the Advanced settings when defining the action task, the developer can set an option to enforce the user to provide at least one of the optional fields (parameters/entity) of all the configured optional parameters. This is to handle the use case of Modify.
This Bot response is displayed if the user does not provide value to any of the optional parameters |
Topic retry limit exceeded |
This is only for the developer (Developer mode on).
The platform has set up a check on loop limit and if the dialog conditions result in looping through the same nodes multiple times (Defined limit) then the task is discarded and this message is shown to the developer. |
Universal fallback response |
Shown in the following cases:
1. Universal catchall: For any reason, be it technical or others, when the bot is not able to generate further responses
2. When the bot exceeds the maximum number of nodes that can be executed in a volley, and the user is not a bot developer. For a bot developer Topic retry limit exceeded message displays in this case. |
Server returned authorisation failure and the user needs to re-authorize |
This message is displayed for a Server Authorization failure during the execution of the script node or making API call. |
User selects a valid option from the list of options |
The message is displayed when the bot displays a list of all the tasks and the user selects an action/alert/information task. |
User selects an action |
The message is displayed when the user selects an action task to be executed. The bot confirms that the task has been selected and asks the user to provide values for the parameter required to complete the task. |
Alert is identified, ask the user to enter alert time |
Applicable to Alert Task Only
During the setup of the Alert, the bot will ask the user the frequency at which the alert will be triggered. The end-user will need to specify at what interval the alert task will be triggered.
This bot message is displayed to request the user to specify the Alert time if the Trigger interval option is set to At a specific time in the day. |
Alert is identified, ask the user to enter alert time interval |
Applicable to Alert Task Only
During the setup of the Alert, the bot will ask the user the frequency at which the alert will be triggered. The end-user will need to specify at what interval the alert task will be triggered.
This bot message is displayed to request the user to specify the Alert time interval if the Trigger interval option is set to Every X mins. |
User selects an alert |
The message is displayed when the user selects an alert task to be executed. The bot confirms that the task has been selected and asks the user to provide values for the parameter required to complete the task. |
Task discarded |
Shown when the user types discard in the middle of task flow. The bot discards the task. |
Bot choosing the default account |
Used in alerts. Shown when the user is asked if they want to amend anything before setting up the alert, and what the user replies with is not understood by the bot. |
Confirmation Dialog for Task consolidated |
Used in Action and Information tasks.
Before executing the task, the bot confirms with the user with the parameters captured if it can go ahead and execute the task |
Confirmation Dialog for Alert consolidated |
Applicable to Alert task Only
During a task set up by the end-user, the bot will confirm all the details entered with the user before setting up the alert. It also gives the user an option to amend the values, proceed or discard.
This message is displayed only if the developer has enabled confirmation of all parameters before the execution of the task. |
Confirmation Dialog for Alert consolidated without fields |
Applicable to Alert Task Only
If the alert is not expecting any parameters from the end-user, the bot will display this message before the final execution of the alert.
This message will be displayed only if the developer has enabled confirmation with the user before the execution of the task. |
The alerts will be muted |
This message is displayed when the developer has muted the alert notifications |
Confirmation Dialog when alerts are muted |
Applicable to Alert Task Only
This response is displayed when the developer has enabled Mute alert notifications for the RSS feed. Developers can enable or disable Mute alerts notifications if they do not want desktop or mobile phone notifications to display on the desktop or your mobile phone each time an alert for the RSS is received. By default, notifications are enabled. |
Alert Frequency description |
Applicable to Alert Task Only
Alert tasks when configured using web service, make requests based on the frequency selected by the bot user.
This message is displayed as an alert task setup confirmation about the frequency of query. |
Not understanding the input at confirmation |
In the process of setting up the alerts, the user is asked to confirm the frequency settings and the user response does not relate to the frequency query. |
No results found for the search string |
Applicable to Alert, Action and Information Task
When a typeahead field does not return any results |
Successful task setup |
This message is displayed when an alert task is set up successfully |
I am not sure what you mean |
Shown when the bot finds one or more not-so-confident intents against a user utterance. Usually shown for FAQ suggestions. |
Ambiguity in intent recognition |
This response is displayed when the bot fails to identify the intent from the end user utterance. The bot then prompts the user to re-phrase the statement. |
User has selected to setup an alert per day and bot needs to know if the choice is based on frequency or specific time |
Applicable to Alert Task Only
This message is displayed when the bot asks the user to provide the frequency at which the alert task will be auto-triggered. This can be specified in terms of af a particular time as 10 am or frequency like every 10 minutes. This is a message when both the options are set up. |
Bot needs to present the filter options |
Applicable to Alert Task Only
This message displayed when more than one filters are available during the setup of an alert. In this situation, bot will display this message followed by the list of available filters from where the user can select the filter to apply. |
Bot needs to present the filter options with exit option |
Applicable to Alert Task Only
This message displayed when more than one filters are available during the setup of an alert. In that situation, bot will display this message followed by the list of available filters from where the user can select the filter to apply and an option to skip. |
User finished configuring filters |
Applicable to Alert Task Only
This message is displayed after a user completes configuring a filter while setting up an alert task. |
User asks Who am I |
Shown when a user types who am I |
User asks for help |
This message is displayed when the user types Help. The bot lists all the dialog tasks, alert/action/information task it can perform.
Part of the Help message. |
Skipped values |
Applicable to Action and Information Task
This is part of the confirmation message for an action/Information task, we mention the skipped parameters in the confirmation message. |
While filling fields, ask user to change the field that this fields depends on |
Applicable to Actions dropdowns
This message is displayed to the user when a drop-down field at actions is dependent on another field and platform is not able to fetch the data from the dependent field |
When there is no data |
Applicable to Action Tasks
This message is displayed when the user chooses to change the account and upon bot confirmation, the user provides no as input |
When date given in Invalid format |
Shown when the user enters an invalid entry for a date entity. The platform recognizes the following date formats: YYYY-MM-DD, DD-MM-YYYY
DD-MM-YY, 1 Jan 1982 or 1st Jan, or the following type of date descriptions This day last year, Next Friday |
This message is displayed by the bot when the end user discard the current task in execution. The user can use the discard/discard all command to discard the current task in execution. Other similar commands like exit, cancel etc also results in discard. |
Follow up sentence post User discards/abandons the current activity |
Confirmation Dialog for task with skipped fields |
Applicable to Action and Information Task
This message is displayed to confirm the setup of Action/Information before the final execution of the task when a few fields are not mandatory to provide by the user. |
Listing all tasks |
This message is displayed when the end user types Help and the bot lists all tasks. This is part of the message shown when user utterance does not match any task/faq |
Listing all alerts |
This message is displayed when the end user types Help and the bot lists all alert tasks. This is part of the message shown when user utterance does not match any task/faq |
Listing all FAQs |
Shown when responding to the user when requested for Help. This response is part of a bigger response and deals with the knowledge graph collections. |
Listing all alerts after tasks |
If a bot just has alert tasks, the bot shows this message along with showing the list of all alert tasks when the bot fails to understand the user intent |
Listing all alerts after tasks and FAQs |
When user provides the input Help and all types of tasks Actions, Dialogs, FAQs and Alerts are configured at the bot |
Lists all actions and FAQs for a bot |
This message is displayed when the bot is unable to find a matching task for the end-user utterance and lists all actions and FAQs. |
Lists all alerts and FAQs for a bot |
This message is displayed when the bot is unable to find a matching task for the end-user utterance and lists all alerts and FAQs. |
When bot has no tasks |
Shown when the developer tries to run a bot that doesn’t have any tasks created. |
When a server call fails and the task has to be discarded |
Shown when a kore API call couldn’t be made (webhook node or service node) and the task had to be discarded. |
User prompt when a task is discarded due to a server call failure |
This message is displayed when there is a server call failure due to which the API call was not completed successfully. |
Specific bot is not available for conversation |
This message is displayed when a bot is not published yet and the end user tries to communicate with it. |
Field title and value in confirmation |
Applicable to Alert, Action and Information Task
This is part of the confirmation step before executing the alert, action or information task. The format of showing the captured parameters is described here. |
Recursive dialog found |
Shown when the bot calls a dialog recursively and exceeds the maximum limit (100). |
Loop limit reached for a node |
Shown when the bot repeatedly invokes the same node in a loop for more than an allowed number of times. |
Message component doesn’t have a message |
When the message from a message node or service node is empty or cannot be resolved, we show this default message. |
User says thanks |
Shown when user thanks the bot. |
User says OK, fine, yes, etc. when there is no task in context |
Shown when the user says OK, fine, got it, etc (probably after finishing a task) |
User says no, nope etc. when there is no task in context |
This is small talk in the response to user utterance is – No, Nopes, etc. |
User says great, awesome etc. when there is no task in context |
Shown when the user says great, awesome, etc. (probably after finishing a task) |
User says that helped, that was useful, etc. |
Shown when the user says good, great, awesome, cool, “fair enough”, “that helped”, “it helps”, “that was useful”, “that was handy” etc. (probably after finishing a task) |
User says I am done. That’s it for now! etc. |
Shown when the user says I am done, that’s it for now, that’s all, done, etc. (probably after finishing a task) |
Successfully added filter |
This message is displayed when a filter is added successfully to an alert |
After successfully adding a filter, showing the filter options again |
Applicable to Alert Tasks only
Developers can define filters for end-users to limit the results of an alert task as per the end-user needs. When the alert is set up by the end-user, and the filter applied, only alert messages that meet the filter specifications are displayed to the end-user.
This message is displayed when a filter is enabled for an alert. |
User gave invalid input for filter, showing the filter options again |
Applicable to Alert Task Only
The message is displayed when the user specifies a filter name that does not match with the ones that have been configured. |
Resume paused task. |
This message is displayed when the user chooses to resume the On-hold task. The message is displayed only when the Resume option is set to Notify the user with a message that the on-hold task is being resumed. |
Notify the user that we have canceled the paused task. |
This message is displayed when the user chooses to cancel the on-hold task. This option of canceling the on-hold task is available only when the Resume option is set to Get confirmation with the user before resuming on hold task. When the user is asked to confirm resumption and selects to cancel the on-hold task this message is shown. |
Notify the user that we have canceled the current task to switch to another |
This message is displayed when the Hold and Resume – Hold option is set to Discard the current task and switch to new. Before discarding the current task, the bot will display the given message. This message can be customized from the Manage response option. |
When an interruption is identified but hold is not allowed |
This message is displayed when the user input matches with another task when one task is in execution but the current task cannot be interrupted. In this situation, the bot will add the new task to the follow-up task list and continue the execution of the current task. For this behavior, the developer needs to select Continue the current task and add a new task to the follow-up task list in the Hold and Resume settings. |
Service call timedout |
Shown when a third party API call timed out (webhook node or service node-third party async API timeout) |
Dialog has no transitions |
Applicable to Dialog Task Only
This response is displayed when the bot identifies a dialog task for which no conversation flow has been defined. The task is defined only with an Intent node. |
manage account |
User says manage bot accounts, add a new phone number, manage my profile, I want to delete my bot account, I want to reactivate my account, etc. |