Categorical Slot Issues

I agree that this behavior of categorical slots is a bit annoying at times. We usually want only one of the defined values or nothing.

  1. Can you share the NLU examples? The bot shouldn’t recognize “king size” as an entity if it is not tagged as the room_type entity in the intent examples.

  2. You can still tag, for example, “king size” as an entity example in your NLU but mention it as a synonym for “double”: I would like a [king size]{"entity": "room_type", "value": "double"} bed.

  3. Another thing you can do is control the users’ choice by using two buttons (Single, Double) that will force the user to choose one of these two only.

  4. You said you don’t want that, but I’m gonna write it anyway in case a future reader comes across this. You can use Custom Actions and Form Validation Actions to set the slot if its value is only either single or double.

1 Like