Ask for Intent action
Intents describe a goal or task that a user wants to do, such as tracking their package or booking a cab. In a bot flow, this action prompts the user to provide an intent. Configure your bot intents from the Natural Language Understanding menu. For more information, see Intents overview.
Access the Ask for Intent action from the bot flow’s Ask menu in the Architect toolbox.
Name | Description | |
---|---|---|
Name | Type a meaningful name for the action. The label you enter here becomes the action’s name displayed in the flow structure. | |
Question | Here, ask callers or chat recipients what they want to do. In call flows, the question you enter hear plays verbally to the caller. In chat flows, this question appears in text. | |
Voice End of Input Timeout |
The maximum length of time to pause after the system detects that the caller has finished speaking. If you use a value that is too low, the system can truncate caller input mid-sentence. A value that is too high can require callers to repeat themselves, which can lead to recognition problems. If the duration value is less than the minimum value, then the flow uses the minimum value. If the value is greater than the maximum value, then the flow uses the maximum value. If the value is NOT_SET, then the system uses the default value at runtime.
|
|
Invalid Response | No Input |
Enter the communication that the bot produces when it does not receive user input. For example, “Do you want to find a branch nearby?” Note: No Input reprompts are not enabled for Digital Bot Flows. The bot returns the configuration that you define in Settings > User Input > No Input Detected > No Input Apology combined with the Question communication. |
Customize No Input |
Click to enable the No Input Reprompts field and create a list of prompts that the bot incrementally returns after it does not receive user input. |
|
No Match |
The communication that the bot returns when the user’s input is not a valid match. For example, “Tell me again what you would like to do.” Note: The bot returns the configuration that you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication. |
|
Customize No Match |
Click to enable the No Match Reprompts field and create a list of no match prompts. The bot returns these prompts incrementally after it receives No Match input events. |
|
No Match Reprompts |
When the bot receives a No Match input, it returns the communication at the position in the No Match Reprompts collection that corresponds to the current number of No Match inputs received for that action. For example, the first No Match input triggers the bot to use the first No Match reprompt in the defined collection. The length of the No Match Reprompt collection also overrides the maximum number of No Match retries that you define in Settings > User Input > No Match Detected > Maximum Number of No Match Retries for that particular action. For example, if you define two reprompts in the collection, the bot retries twice. An empty collection turns off No Match retries. Note: The bot returns the configuration that you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication. |
|
Knowledge Search Results |
The variable that stores the collection of KnowledgeBaseDocument matching results from the search that Architect performs in the action. If you select standard knowledge handling, then search results collection only contains the article that appears to the user. If you choose custom knowledge handling, then the results collection can contain multiple articles that strongly match the search. To configure standard or custom knowledge handling, follow these steps:
|
|
Paths | Intents | Enable or disable the intents this action can match. For each intent, an output path is enabled on the action. If the intent matches the user input, then the flow takes the relevant output path. If you disable a path, the flows configured for that output path are hidden, not deleted. |
Knowledge | Enable or disable the Knowledge output path. When you enable the path, if a knowledge article matches the user input, then the flow takes this output path. If you disable a path, the flows configured for that output path are hidden, not deleted. | |
Max No Inputs |
Enable or disable the Max No Inputs path. When you enable this path, if the bot exceeds the maximum number of no input retries that you set for the action, then the flow takes this output path. If you enable both No Intent and Max No Inputs paths and the bot exceeds the maximum number of no input retries, then the Max No Input path takes precedence. If you disable a path, the flows configured for that output path are hidden, not deleted. |