extended-salmon•2y ago
{Names} entity is completely unusable now?
Hey team,
I've had no issues whatsoever capturing user names just using the system {user_name} entity as is in previous projects. The current project rejects every name. I have added over 1000 names as examples, I've limited intent scoping to this single step, I've deleted similar variables like first_name & last name. I am at my wits end. I don't see anything different from any other project. Any ideas whats wrong with the NLU on this one?? #
3 Replies
It sounds like you're experiencing issues with the system-defined {user_name} entity not recognizing names in your current project, despite having worked in previous ones. This could be due to several factors, but let's try to troubleshoot:
- Ensure that the entity type is correctly set to NAME, as this is designed to capture first names, last names, or full names.
- Review the NLU model training. If you've made recent changes, such as adding over a thousand names, make sure to retrain your NLU model to incorporate these updates.
- Check for any unintentional restrictions or configurations that might have been applied to the entity or the step where it's being used.
- Consider extending the system-defined entities if you're looking for a specific pattern in names that isn't being captured by the default settings.
If these steps don't resolve the issue, it might be helpful to look into creating a custom entity tailored to your specific needs, although the NAME entity should generally handle common use cases effectively.
For more detailed guidance on working with entities and capture steps, you might find these resources helpful:
- Capture Step and Entity Creation & Editing
- Entities in Voiceflow
extended-salmonOP•2y ago
Thanks Tico. Yes, model is trained and there are no restrictions or anything like that. It doesn't recognize "John Smith".
I would recommend using an LLM for entity detection.