Chatlayer Documentation
Get in touchAbout Chatlayer
  • Welcome
  • What's new
  • Send feedback
  • start quickly
    • Leadzy tutorial
      • 0. Introduction
      • 1. New bot, new block
      • 2. Understand your users
      • 3. Collect and display user input
      • 4. Steer the conversation with Conditions
      • 5. Empower your bot with Actions
      • 6. Set up a channel and publish your bot
    • Templates
      • Banking
      • E-Commerce Returns
      • E-Bike Shop
      • E-Scooter Support
      • Feedback
      • Find Nearest Location
      • GPT
      • 🆕Gym
      • Job applications
      • Knowledge base AI template
      • Lead generation
      • 🆕NPS
      • Restaurant
      • Retail
  • navigation
    • Analytics
      • Dashboard
      • Customers
      • Conversations
      • User flow
      • Intents
      • 🆕Funnels [Beta]
    • Bot builder
      • Flows
        • Canvas functionalities
        • Collaborate with team members
        • Manage your flows
        • 🆕[Beta] Export and import flows
      • Bot dialogs view
      • Translations
      • Events
    • NLP
      • Dashboard
      • Intents
      • Expressions
      • Entities
      • Train
      • NLP settings
      • Improve
    • Knowledge base AI
      • Add content to your KBAI
      • Build your KBAI flow
      • Use your KBAI source URL in a button
      • Use tags to limit your KBAI content
      • 🆕Use Tables to store your KBAI questions
      • 🆕Manage handover where KBAI is unsatisfactory
    • History
      • Conversations
      • Execution logs
      • Versions
    • Channels
    • Tables
      • Create a table with records
      • Column types
      • Operate on your records
        • Insert record
        • Update record
        • Retrieve record
        • Delete record
      • API
    • Settings
      • Bot settings
      • Offloading
      • Variables
      • Voice
      • Import/Export
  • build your bot
    • Conversation design
      • Plan your bot
      • Conversation design workflow
    • Flow logic
      • Blocks
        • Message
        • Condition
        • Collect input
        • Action
      • Go-to connections
    • 🆕Emulator
    • Tips & best practices
      • Route your flow depending on the time
      • Improve the Not understood block
        • How to create better not understood messages
        • Not understood counter
        • Not understood Google search
      • Go to previous block
      • Recognizing a returning user
      • Skip introduction message
      • Route your flow depending on the channel
      • Reuse flows
      • Connect two bots to each other
  • understand users
    • Natural language processing (NLP)
      • Basic NLP concepts
      • Detect information with entities
        • Match entities
        • Contextual entities
        • System entities
        • Composite entities
      • NLP best practices
        • Word order and diversity of expressions
      • AI intent booster
      • Train your NLP
      • Context
      • NLP import & export
      • Sentiment analysis
    • Languages
      • Supported languages
      • Make your bot multilingual
      • Change language within the conversation
  • set up channels
    • Add a channel to your bot
    • All channels
      • 🚨Facebook Messenger [Deprecated soon]
        • Facebook Admin Removal
        • Facebook Webview Whitelisting
        • Facebook Messenger API updates for Europe
      • 🚨Google Assistant [Deprecated soon]
      • Webhook
      • Web
        • 🚨Web V1 [Deprecated]
          • Customize web widget
          • Live example web widget
        • 🆕Web V2
          • 🆕From Web V1 to V2
          • 🆕Web V2 methods and options
    • Sinch Conversation API
      • Configure your Sinch Conversation API
      • 🆕 Make the most of RCS with Carousels
      • WhatsApp Business API
  • integrate & code
    • API calls
      • Configure your API integration
      • Advanced API features
      • V1 API Reference
      • Custom integrations 101
    • Code editor
      • [Example] Sending data to Airtable (POST)
      • [Example] Retrieving data from Airtable (GET)
      • [Example] Making SOAP requests
    • App integrations
      • Airtable
      • Freshdesk
      • Freshdesk Messaging
      • 🆕Gmail
      • Intercom
      • Mailgun
      • OpenAI: GPT-3, ChatGPT and GPT-4
      • Salesforce
      • 🆕Slack
      • Topdesk
      • Zendesk Support
      • Zendesk Sunshine (beta)
    • 🆕Expression syntax
    • Human handover & live chat
      • Sinch Contact Pro
      • #Interact
      • Genesys Cloud
      • Offloading Webhook
      • Salesforce Service Cloud
      • Sparkcentral by Hootsuite
      • Zendesk Chat
    • Chatlayer messages specifications
  • Publish
    • Publish your bot
      • Publish a flow
  • Analyze & maintain
    • Analytics definitions
    • Data retention
    • Maintenance
    • Session
    • Track events for analytics
  • VOICE
    • 🆕Send bot response as audio
    • Voicebots
      • Create a voicebot
      • Voicebot-specific actions
      • Test your voicebot
      • From chat to voice
  • access & support
    • Identity & Access
      • Single Sign-On (SAML SSO)
    • Billing & subscription
    • Get in touch
    • Chatlayer glossary
    • SaaS Regions & IP Ranges
    • Status
    • Debug your bot
      • No correct response
      • Collect input not working
      • Video isn't working
Powered by GitBook
On this page
  • 1. Change the block type
  • 2. Set the first condition in the Condition block
  • 3. Set the final condition in the Condition block
  • 4. Write the bot messages

Was this helpful?

  1. build your bot
  2. Tips & best practices
  3. Improve the Not understood block

Not understood counter

A good 'not understood' handling is key to a good bot experience. Learn how to set up this counter in the article below.

PreviousHow to create better not understood messagesNextNot understood Google search

Last updated 1 year ago

Was this helpful?

Instead of always showing the same not understood message, you can create a counter to show different messages, depending on how often the not understood block is triggered. For example, when the bot doesn't understand the user for the first time, it will display the first not understood message:

"Sorry, I didn't get that. Can you please rephrase?"

After the user has sent another message and the bot didn't understand a second time, it will display the second not understood message, offering an external way out:

"Sorry, I still don't understand. Perhaps you'd like to talk to my colleague instead?"

Or "Sorry, I still don't understand. Perhaps you'd like to email us instead?"

This counter set-up creates a better user experience and makes the bot appear much smarter. Ready to get started? Let's go! 👏

1. Change the block type

Step 1: Click on the 'not understood' Message block and in the list under 'Type', select 'Go To'

2. Set the first condition in the Condition block

For the next step, we are going to set the counter conditions so the bot knows how often this block was triggered already.

For the first condition, we want to check if the 'not understood message' block was triggered already once. To do so, copy and paste the variable not_understood_counter in the left field. Click on 'create' to create the variable.

Then in the middle field, select equals in the drop down menu.

In the field on the right, we'll put 1 – This tells the bot that the first not understood block was displayed already and that it's time to display the second not understood block.

3. Set the final condition in the Condition block

For the second and final condition, we're creating the actual counter.

Under Else, type Not understood x 1 and click 'create' to create the variable.

Save your set-up by clicking the Save button on the bottom right.

The entire Condition block should look like this:

4. Write the bot messages

After saving your Condition block and closing it, the flow should look like this:

Now it's time to write the copy for both blocks. Here's some inspiration for the first message that will be displayed – the 'Not understood x 1' block:

  • Sorry, I didn't get that. Can you please rephrase?

  • Hmm, I can't understand. Can you use different words? Perhaps I'll get it then!

  • I didn't understand, please try once more

For the second and final message, the 'Not understood x 2' block, you can write something like this:

  • Sorry, I still can't understand. Perhaps you'd like to talk to my human colleague instead?

  • Sorry, I can't seem to understand. Would you like to call us instead?

  • Sorry, I can't seem to understand. Perhaps it's better if you email us your question

That's it, all done! You just created a user-friendly way of telling the user the bot didn't understand 👏

Next, click + Add Variable to add a variable and value. In the middle field, add the variable not_understood_counter. In the field on the right, add the {not_understood_counter|increment}

increment value