While most of users' input is clearly assignable to a specific user intent, there are some expressions that are so generic that it is not possible to link this input to one intent and one intent only. These expressions are e.g. okay, I don't care, don't know, not yet, yes or no. These expressions are so general that they are called global intents. They can be found in the intent signature under the game title Hooks.
Since hooks are so context-sensitive, they must be configured in the respective context. The context for hooks is the bot message to which the respective user reaction refers. If the bot asks "Do we want to start?" and a user writes "yes" as the answer, then it is the bot intent where it must be set up to specify which intent is implied as the reaction at this point.
At this point, we are not dealing with the standard procedure of always having a specific question related to a specific answer, but with the fact that certain utterances are already defined in the hooks intent. So all we have to do is placing hooks intents in the right context. This should become clear when we discuss it based on an example:
In the way the bot message ends, the reply spectrum to it is already implied. Answers such as "yes" or "no" are more likely to be given. However, as mentioned above, we should not add "yes" as a possible user utterance in the user intent that is meant here. The reason for this is that you might expect the same answer elsewhere in the bot. Adding "yes" as uterance to multiple user intents would prevent the bot from making an informed decision as to which intent would trigger the correct answer in this context.
Therefore there is the possibility to add a global intent at the end of the bot intent. There you define two things. First of all, which hook it is that you are configuring and secondly which User Intent the hook is supposed to trigger.
As the first step it is important that you select the correct hook because the hook determines which user reply is anticipated. You set it up by clicking on add callback and filling in the fields that open. First, you select the type of response you want to recognize - for example, for affirmative responses, select hooks/Ack (short for acknowledgement).
The next step is to set the User Intent for which this answer should stand. The reason for this is that the hook simulates the User Intent at this point. In other words, you configure that the hook evokes the same behavior as when this intent is triggered through the recognition of a User Utterance. What you determine here are two things. First, the game in which the intent lies. Secondly, the intent that the respective reply of users should trigger.
A respective configuration for acknowledging and disapproving reactions to the above mentioned bot intent will look like this:
The configuration is to be interpreted as follows: When users enter something that responds to the Bot Intent with an approval, the intent
Guide/FirstSteps is activated. If the reply to the Bot Intent is a negative response, the main menu intent is taken from the same game (
Since the abbreviations used are not always self-explanatory, here is a short list of abbreviations and the utterances that are already covered by these intents.
By the way, we are always open for further suggestions. So if you have another suggestion for an expression we should add to our hooks, you can always contact us at email@example.com.
|Ack (acknowledgement)||yes, yeah, indeed, okay, sure, you bet, fine, exactly, great, awesome, I like, perfect|
|NotAck (Not acknowledge)||no, no thanks, never, I don’t think so, boring, stupid, not this, I do not like|
|Maybe||maybe, not sure, possibly, could be|
|DontKnow||do not know, don’t know, dunno, no idea, how should I know|
|Thanks||thank you, thanks, thx, merci, grazie, gracias|
|Reset||start again, restart, reset|
|Sorry||I am sorry, sorry, I’m sorry, no offense, did not mean it|
|Aha||aha, mhm, well|
|Egal (doesn’t matter)||I don’t care, whatever, somewhere, everywhere, nothing in particular|
|LOL||lol, rofl, haha, hihi, heh, hehehe|
|Schade (too bad)||what a pity, too bad|