> For the complete documentation index, see [llms.txt](https://readme.dhee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.dhee.ai/concepts-we-work-on/user-intent-recognition.md).

# User Intent Recognition

Detecting User's intent is very crucial in driving the conversations in a dialog system in the right direction. In simple words intent recognition engine classifies user utterance to one of the target class/intent. 

![](/files/uX6BU1Nbw0UUao7X290d)

#### **Components of Intent Recognition Engine**

1. Multilingual Transformer based Language Model

   This component converts input sentence/words to contextual embeddings, by contextual we mean the same word in different contexts would end up getting different embeddings, this contextuality also helps in dealing with homographs. The words in an utterance are tokenized using a sub-word tokenizer (more about this in the next section), these token's id's traverse through the domain fine tuned Language models to output 768-dimensional word vectors. various pooling techniques can be employed to convert these high dimensional word vectors into sentence embeddings.
2. Convolutional Neural Network (CNN) based classifier

   The embeddings extracted from a Domain Adapted Language Model is used to train a CNN classifier

![intent-recognition engine](/files/u7iXitt2MwfIfSSd1zZ9)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://readme.dhee.ai/concepts-we-work-on/user-intent-recognition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.