{ "componentChunkName": "component---src-templates-doc-page-js", "path": "/docs/en/NLU_core/intent_detection/", "result": {"data":{"site":{"siteMetadata":{"title":"Gatsby-doc-engine"}},"markdownRemark":{"id":"60c4a1ca-4c02-546f-b58b-48d9919ba879","excerpt":"Activation rules?> You can detect the client’s intent using patterns, phrase examples and the CAILA classifier. Activation rules for patterns, intents and…","html":"

Activation rules

\n
\n

You can detect the client’s intent using patterns, phrase examples and the CAILA classifier.

\n

Activation rules for patterns, intents and groups of examples in a script are processed for the following objects in descending priority:

\n
    \n
  1. Patterns.
    2. \n
  2. A group of STS classifier samples.
    3. \n
  3. Intents.
    4. \n
\n
\n

Rule activation mechanism

\n
    \n
  1. If the user request has been triggered in a state with a pattern, a group of e! examples and an intent, then the pattern will have the highest priority. The state with the pattern will be triggered.
    2. \n
  2. If the user request has been triggered in a state with a group of e! examples and an intent, then the group of samples will have the highest priority. The state with a group of samples will be triggered.
    3. \n
  3. If the user request has been triggered in a state with an intent only, then only the intent will be handled.
    4. \n
  4. In all other cases the user request will be handled by the CatchAll state.
    5. \n
\n
\n

CatchAll

\n

Note that if the NLU service is used together with patterns and classifier phrase examples, such a CatchAll is not used:

\n
    state: CatchAll\n        q!: *\n        a: I did not get it
\n

Use the event: noMatch for user requests not defined in the script:

\n
    state: CatchAll\n        event: noMatch\n        a: You said: {{ $request.query }}
\n
\n

A sample script:

\n

Consider the following script:

\n
theme: /\n\n    state: Pattern\n        q!: * pattern *\n        a: A pattern has been triggered\n\n    state: Example\n        e!: pattern\n        a: This example is not triggered because a pattern is processed\n\n    state: Second example\n        e!: example\n        a: The example has been triggered\n\n    state:\n        intent!: /pattern\n        a: This example is not triggered because a pattern is processed\n\n    state:\n        intent!: /example\n        a: This example is not triggered because a group of examples is processed\n\n    state: Intent\n        intent!: /intent\n        a: An intent has been triggered\n\n    state: CatchAll\n        event: noMatch\n        a: You said: {{ $request.query }}
\n

The training phrases for the intent are as follows:

\n\n

We launch the test widget and check the script:

\n
    \n
  1. In response to the request Pattern the Pattern state is processed.
    2. \n
  2. In response to example the Second example state is processed.
    3. \n
  3. In response to Intent the IntentI state is processed.
    4. \n
  4. All requests not handled by the script are handled by the CatchAll state.
    5. \n
\n

When patterns, intents and example groups are used in the same script, the developer can define the priorities of rule activation.

","frontmatter":{"title":"","description":null},"headings":[{"value":"Activation rules"}]}},"pageContext":{"slug":"/docs/en/NLU_core/intent_detection/","previous":{"fields":{"slug":"/docs/en/NLU_core/nlu_core/"},"frontmatter":{"title":"","description":null}},"next":{"fields":{"slug":"/docs/en/NLU_core/intent/"},"frontmatter":{"title":"","description":null}}}}, "staticQueryHashes": ["1209419333"]}