• Skip to primary navigation
  • Skip to main content
  • Skip to footer
Cyara

Cyara

Cyara Customer Experience Assurance Platform

  • Login
  • Contact Us
  • Request a demo
  • Login
  • Contact us
  • Request a demo
  • Why Cyara
    • AI-Led CX Assurance Platform
    • AI vision for CX
    • Cyara partner network
    • Cyara Academy
  • Solutions
    • Transform
          • TRANSFORM – Drive CX Change

          • Functional, regression, & objective testing | Cyara Velocity
          • Performance testing | Cyara Cruncher
          • See all use cases >
          • Cyara platform - Transform - Drive CX change
    • Monitor
          • MONITOR – Assure CX Journeys

          • Telecom assurance | Cyara Voice Assure
          • CX & telecom monitoring | Cyara Pulse 360
          • Call ID line assurance | Cyara Number Trust
          • Agent environment assurance | Cyara ResolveAX
          • CX monitoring | Cyara Pulse
          • See all use cases >
          • Cyara platform - Monitor - Assure CX journeys
    • Optimize
          • OPTIMIZE — Leverage AI for CX

          • Conversational AI optimization | Cyara Botium
            • Functional & regression testing for AI agents
            • LLM-driven AI agent testing
            • Load testing for AI agents
            • NLP analytics for conversational AI in CX
          • Generative AI assurance | Cyara AI Trust
          • See all use cases >
          • Cyara platform - Optimize - Leverage AI for CX
    • Connect
          • CONNECT — Assure WebRTC CX

          • WebRTC optimization | Cyara testRTC
          • WebRTC monitoring | Cyara watchRTC
          • WebRTC quality assurance | Cyara qualityRTC
          • See all use cases >
          • Cyara platform - Connect - Assure WebRTC CX
  • Resources
    • CX Assurance blog
    • Customer success showcase
    • CX use cases
    • Events & upcoming webinars
    • On-demand webinars
    • Resource library
    • Customer community
  • About Us
        • About Cyara

        • About Cyara
        • Leadership
        • Careers
        • Legal statements, policies, & agreements
        • Services

        • Cyara Academy
        • Consulting services
        • Customer success services
        • Technical support
        • News

        • CEO’s desk
        • Press releases
        • Media coverage
        • Cyara awards
        • Partners

        • Partners

Blog / CX Assurance

October 8, 2021

The Six Common Challenges of Underperforming Chatbot Intents

Alison Houston

Alison Houston, Data model analyst

This article was originally published on QBox’s blog, prior to Cyara’s acquisition of QBox. Learn more about Cyara + QBox.


Improving underperforming chatbot intents can be a challenge for anyone looking to improve their conversational AI. In this blog, our Data Model Analyst Alison Houston shares the six most common challenges she comes across and how they can be fixed.

Cyara empowers businesses to accelerate chatbot development, reduce costs, and improve chatbot performance with our conversational AI optimization solution.

People examining message with @mention symbol

If you’re working on chatbots, you’re probably wondering how to improve your chatbot intents and where to start with underperforming intents. I’ve built numerous chatbots myself and analysed many client chatbots to provide them with helpful tips to improve the performance of their failing bots.  Over the years, I’ve come to understand the underperformance is usually down to some problematic intents within the bot falling into one (or more) of six common challenges: 

  • Weak concepts
  • Intent too wide
  • Overlapping intents
  • Lack of training data
  • Imbalance of training data
  • Human error

Weak Concepts

A weak concept is where the most important phrase or set of words within an utterance are not represented very strongly within the intent’s training data, and therefore the bot’s learning value is weak.    

This is probably the most common issue I see and can easily be rectified.  The general rule I find works well is that for every concept within your intent, aim to have three utterances.  So, if I have an intent covering ways to get in contact with a company, a few example utterances may be: 

  • I want your email address.
  • Give me your telephone number.
  • What are your contact details? 

We have three concepts here: email address, telephone number, and mailing address, so each concept needs to have another two utterances added. Each concept will then be reinforced, and the bot’s learning value is increased. This means that whichever way a user asks for the company email address for instance, the likelihood of returning the correct intent, and with high confidence is greater. 

Intent too Wide

When an intent covers many different subject areas, it is at risk of being too wide. It probably has many more training phrases compared to the rest of the model and could possibly be compromising other intents. This may happen if you have an intent that has a lot of traffic going to it, and so it is tempting for the chatbot builder to pick many training phrases from the customer logs to keep adding to that intent in the training and improvement process.   

An intent should have a clear purpose and be focused. You should be able to describe the purpose of the intent in one sentence. If you’re finding that your intent is getting a little too unwieldy, don’t be afraid to split the intent into smaller, more manageable intents. Each of these smaller intents will then be highly focused and it is more likely your bot will understand them better. 

Overlapping Intents

This is when two or more intents have similar meaning or cover similar subject areas, and therefore will probably have related training data, causing confusion in the model. You may see this problem in your bot if it’s consistently returning the same incorrect intent or it’s consistently returning the correct intent, but with low confidence, (or it could be a combination of both symptoms).   

If it’s vital to have two separate intents because they provide different answers, then you will need to carefully train each intent to ensure the set of utterances for each is very clearly defined and separated from each other to prevent overlaps.   

In some cases, it might be impossible to separate the two intents clearly enough and the best course of action would be to merge them into one intent and just provide the user with one answer which covers all aspects of the utterances. You could also consider using entities within the merged intent which could trigger different answers within the same intent. 

Lack of Training Data

This occurs where you have less than five utterances for an intent. Most NLP providers recommend a minimum of five utterances; however, I find aiming for fifteen to twenty good utterances works well for most NLP providers. Although with some intents you might find having five utterances works well, especially for basic intents like greetings ones and pleasantries: hello, goodbye, thanks etc. After all, there’s only so many ways you can say hello. 

Imbalance of Training Data

This is where a particular intent contains too many repeated common phrases like CAN I HAVE or TELL ME ABOUT or HOW DO I within its training data. For instance, if you have one intent with a large amount of training data having the phrase CAN I HAVE in them; you are likely to influence the prediction of user questions to this intent, rather than the correct intent. This is because the phrase CAN I HAVE has been reinforced so much, the bot has incorrectly learned the most important part of the training data is CAN I HAVE.   

We can easily get into bad habits of creating patterns within an intent, but always bear this in mind and always try to make the utterances as varied as possible.  Similarly, try to vary the personal pronoun by including some utterances with “we” instead of “I,” or “us” instead of “me.”  

Human Error

This is where training data has been added to the wrong intent in error, or the exact same training data has been added to more than one intent (although it’s impossible to do this in some NLP Providers as you’ll get an error message alerting you of this). It happens, humans are not infallible! And quite often it’s because more than one person is working on the bot.   

There is no simple solution to this, but usually doing a thorough testing of your bot, and continuous monitoring once the bot is live, will alert you to any of these types of anomalies within your training data.   

Summary

Chatbots are being used everywhere now, there is enormous potential in more intelligent bots, and we’re all trying harder to improve our bot’s performance. Hopefully you’ll be able to identify that some of your own struggling intents probably fall into one of the above types of problems and this may make it easier to rectify them.    

QBox correctness distribution diagram

This diagram is a screenshot of our solution in action.  This is the correctness distribution diagram and shows a typical example of how an intent would look that is possibly too wide, ie. trying to cover too many topics.  The circle in the middle represents the focused intent, the circles on the outside represent intents that are getting confused with the focused intent.  The data points represent the utterances, green dots represent correct predictions and red dots represent incorrect predictions. 

QBox diagram showing possible overlapping intent

This diagram is another screenshot from our platform and shows a typical example of how an intent would look that is possibly overlapping with another intent.  There are a cluster of data points, representing the utterances for the focused intent, all being confused with another intent. 

Contact us to schedule a demonstration.

Read more about: Chatbot Testing, Chatbots, Conversational AI, Conversational AI Testing, QBox

Ready for seamless CX assurance?

Learn how Cyara’s AI-led CX productivity, growth, and assurance engine can help you eradicate bad CX.

Speak to an expert
Office view with Cyara dashboard

Related Posts

conversational AI governance

November 13, 2025

Conversational AI Governance for CX: Ensuring Compliance, Bias Mitigation & Reliability

AI-powered CX channels handle millions of interactions every day. Deliver accurate and reliable CX with conversational AI governance.

Topics: Artificial Intelligence (AI), Conversational AI, Conversational AI Testing, Customer Experience (CX)

AI CX dealbreakers

November 12, 2025

New Survey Data: The AI Dealbreakers Making Consumers Ghost

As customer expectations and Agentic AI technology evolves, you must avoid dealbreakers and deliver quality interactions for best results.

Topics: Agentic AI, Artificial Intelligence (AI), Conversational AI, Conversational AI Testing, Customer Experience (CX)

conversational AI testing

August 28, 2025

Automated Testing for Conversational AI: A Game-Changer in Customer Support

The rise of AI-powered CX offer many key benefits... and risks. Learn how to ensure CX quality with a conversational AI testing solution.

Topics: AI Chatbot Testing, Artificial Intelligence (AI), Automated Testing, Chatbots, Conversational AI, Conversational AI Testing, Customer Experience (CX)

Footer

  • AI-Led CX Assurance Platform
    • Cyara AI Trust
    • Cyara Botium
      • Functional & regression testing for AI agents
      • LLM-driven AI agent testing
      • Load testing for AI agents
      • NLP analytics for conversational AI in CX
    • Cyara CentraCX
    • Cyara Cloud Migration Assurance
    • Cyara Cruncher
    • Cyara Number Trust
    • Cyara probeRTC
    • Cyara Pulse 360
    • Cyara Pulse
    • Cyara qualityRTC
    • Cyara ResolveAX
    • Cyara testingRTC
    • Cyara testRTC
    • Cyara upRTC
    • Cyara Velocity
    • Cyara Voice Assure
    • Cyara watchRTC
  • Use cases
    • Agent desktop testing
    • Cloud contact center monitoring
    • Contact center number test types
    • Contact center testing
    • Continuous testing
    • Conversational AI testing
    • CX monitoring
    • DevOps for CX
    • Email & SMS testing
    • Functional testing
    • Incident management
    • IVR discovery
    • IVR testing
    • Load & performance testing
    • Omnichannel testing
    • Outbound call testing
    • Regression testing
    • Voice biometrics testing
    • Voice of the customer
    • Voice quality testing
    • Web interaction testing
  • Resources
    • CX Assurance blog
    • Customer success showcase
    • Events & upcoming webinars
    • Resource library
    • On-demand webinars
    • Cyara portal & support site access
    • Customer community
  • About us
    • About Cyara
      • About us
      • Leadership
      • Careers
      • Cyara awards
      • Legal statements, policies, & agreements
    • Services
      • Cyara Academy
      • Consulting services
      • Customer success services
      • Technical support
    • News
      • CEO’s desk
      • Press releases
      • Media coverage
    • Partners
      • Partners
      • Integration & technology partners
      • Platform Integrations
  • LinkedIn
  • Twitter
  • YouTube

Copyright © 2006–2025 Cyara® Inc. The Cyara logo, names and marks associated with Cyara’s products and services are trademarks of Cyara. All rights reserved. Privacy Statement