Intent Recognition

Intent recognition is the AI task of identifying the purpose behind a customer's message, such as reporting a fault, checking a bill or moving house, so the contact can be answered, routed or prioritised correctly.

What is intent recognition?

Intent recognition (also called intent detection or intent classification) answers one question: why has this customer made contact? A caller might say “I’ve had no hot water since this morning and I think the power’s off”. The intent is something like report a fault or check for an outage, and everything else the system does depends on getting that right.

It is a core task within natural language understanding, and it works across voice, chatbots, email and messaging. In voice channels it runs on the text produced by automatic speech recognition.

What intent recognition is used for

Routing

Recognising intent lets a contact go straight to the right place: an AI flow that can resolve it, or a queue of agents with the right skills. It is a natural partner to skills-based routing, and a more natural replacement for long IVR menus, because customers say what they want instead of guessing which option fits.

Self-service

An AI voice assistant or chatbot uses intent to decide which flow to follow: look up an outage, take a meter reading, explain a process.

Prioritisation

Some intents are more urgent than others. A hazard call about a fallen power line, or an email that signals a customer is at risk, should jump the queue. Intent recognition makes that possible automatically.

Reporting and insight

Counting intents across all contacts shows what customers are actually ringing about. Speech analytics tools use the same idea to track reasons for contact over time and spot new ones early.

How intents are designed

Intent recognition only works as well as the list of intents behind it. Good intent design follows a few principles:

  1. Start from real data. Look at a large sample of real calls, chats and emails to find the reasons that drive most volume.
  2. One intent, one outcome. Each intent should lead to a distinct response or route. If two lead to the same place, consider merging them.
  3. Plan for “other”. Some contacts won’t fit any intent. Those should go to a person, not be forced into the nearest category.
  4. Allow for several intents. Customers often raise more than one issue in a single contact.
  5. Review regularly. New products, policies and events create new reasons for contact.

Measuring accuracy

Intent recognition is usually measured by how often the predicted intent matches what a human reviewer would choose. It is worth looking beyond the average, because mistakes are not equally costly. Misrouting a billing question is a nuisance. Missing the intent behind a safety call or a vulnerable customer is serious. For high-risk intents, it is better to err on the side of a person.

Accurate intent recognition also supports first contact resolution, because customers who reach the right place first time are more likely to be sorted in one go.

How Telnet Helps

Where Telnet comes in

Telnet’s AI uses intent recognition at three points in a customer interaction:

  • On the call. Tulip identifies what the customer is calling about and takes the routine calls itself, such as outage updates and fault reports, while recognising urgency so the right calls go to a person.
  • On arrival. Iris routes emails by what they are about, not simply the address they were sent to, so a message sent to sales that is really a support request lands with support. You define the work that belongs in each queue and how it is prioritised.
  • Across everything. Fern assigns every call and email a theme describing the reason for contact, discovered from the data rather than chosen from a pre-set list, so new issues surface without anyone having to look for them.
FAQ

Intent Recognition FAQs

What's the difference between an intent and a theme?

An intent is usually a predefined category the system is designed to act on in real time, such as report a fault or update payment details. A theme is a broader label used in analysis to describe why customers made contact, and can be discovered from the data. Intents drive what happens next; themes show patterns across many interactions.

How many intents should a contact centre have?

As few as will reliably drive different actions. If two intents lead to exactly the same routing or response, they can often be merged. Many organisations start with the relatively small number of reasons for contact that make up most of their volume, and add more only when there’s a clear reason to treat a request differently.

What happens when a customer has more than one intent?

It’s common, for example a customer calling about an outage who also wants to query their bill. Modern systems can detect several intents in one message and deal with them in turn. Older systems often lock onto the first one they hear. Either way, the system should check whether there’s anything else before ending the conversation.

Ready to scale?

Outsourced contact centre
for New Zealand & Australia.

30+ years. 100% onshore. The leading provider to the energy & utilities industry.

Get in Touch