What is intent recognition?

Intent recognition is the classification of a customer message into one of a predefined set of purposes, so a system can decide how to respond.

Older chatbots were built entirely on this. Someone enumerated the intents — check_order_status, request_refund, ask_shipping_cost — wrote training phrases for each, and mapped every intent to a scripted reply. It worked exactly as well as the list was complete.

Why it matters

The failure mode is the interesting part. A question that matches no intent falls into a catch-all, which is why so many bots answer 'I didn't quite get that' — the phrase is not a bug, it is the architecture becoming visible. Keeping the list complete means constant maintenance, and the list is never complete, because customers keep inventing phrasings. Retrieval-based systems sidestep the problem: instead of classifying the question, they search the content for whatever is closest to it, so a phrasing nobody anticipated still finds the right page. Intent recognition remains useful for routing — deciding which team gets a message — rather than for answering.

Examples

  • A bot trained on twelve intents meeting the thirteenth and apologising.
  • Routing a message to billing versus technical support, where classification is genuinely the job.
  • A retrieval system answering a phrasing nobody wrote a training example for.

Not the same as

Semantic search

Intent recognition sorts a question into a fixed bucket. Semantic search finds the closest content without needing buckets to exist.

Related

RubyRep is this, applied to your website.

Give it your URL and it reads your pages, then answers your customers from them.

Train My RubyRep