Nomatch and Noinput Elements
Use
The noinput and nomatch elements provide means to handle situations when there is no appropriate answer from the customer. Typical example is to have them in menu element where noinput defines what happens when the user gives no choice, and nomatch defines what happens when the user chooses an option that is none of the choices defined for the menu.
Both elements can work simply as containers for their child elements that are always carried out in no-input and no-match situations, or they can have conditions and counts that make the performance conditional.
noinput
The noinput element has child elements assign, audio, clear, exit, goto, if, and it can be nested in the field, form, menu, transfer, record, vxml element.
* = Specific to Sinch Contact Pro
Attributes of noinput Element |
Description |
---|---|
Condition |
Define the condition for executing the child elements in this element. Use one of the following options:
|
Count |
Enter the appropriate number to define how many times a user is given a chance to enter a DTMF but no answer is received, before the child elements in this element are executed. |
Description* |
Enter a description about what this element is planned for, its requirements and limitations. This helps you to track possible errors later on. |
Reporting Condition* |
Define the condition for including this answer option in reporting. For
example, you may not want to include all |
Answer Option in Reporting* |
Enter a free form text to be displayed in Dashboard, Reporting, and Online Monitoring, especially as an Answer Option for a survey IVR script report. |
nomatch
The nomatch element has child elements assign, audio, clear, disconnect, exit, goto, if, log, var, and can be nested in the field, form, menu, transfer, vxml elements.
Attributes of nomatch Element |
Description |
---|---|
Condition |
Define the condition for executing the child elements in this element. Use one of the following options:
|
Count |
Enter a number for how many times a no-matching DTMF can be entered before the child elements in this element are executed. |
Description* |
Enter a description about what this element is planned for, its requirements and limitations. This helps you to track possible errors later on. |
Reporting Condition* |
Define the condition for including this answer option in reporting. For example, you may not want to include all no-matching answers in reporting when the customer after a few trials enters a proper choice. Make definitions in the same way as any condition, see above. |
Expression for Answer Option in Reporting* |
Enter an expression that defines the text to be displayed in Dashboard, Reporting, and Online Monitoring, especially as an Answer Option for a survey IVR script report. |
Example
See the menu example Example_QueueTransfer_IVR_import.xml that you can get from Sinch.