Hello,
For some reason Dialog Flow CX consistently doesn't parameterize queries, even when there is a word for word match to the intent training sentence.
For example, consider the following intent:
And the following query: "What's the availability of Kevin"
Much to my surprise, DialogFlow CX offers the filled in parameter missing response of:
"Who are you looking for?"
I can then respond with the name, and it's parameterized. But... Honestly why is that? I mean it's a pretty basic prompt, and the intent was matched. So any ideas was the field not parameterized?
intent_detection_confidence: 0.832419693
Also when trying the shortest phrast, "Is Kevin Online" I get the default no match intent and the confidence is 0.3, as seen here: intent_detection_confidence: 0.3
Pretty poor experience for me to be honest...
So nearly a week on without any support.
Is there a way to file a bug report? This is 100% reproducible and cannot be the expected behavior.
Hi @KP-372,
Great to hear from you again.
It sounds like you're encountering some difficulties with parameterization. One way to potentially enhance parameterization accuracy is by adding more variations to your entity annotations.
When defining annotated training phrases, you should use a variety of entity value examples in the phrases. You should not consistently use the same entity example for the annotations.
Do not define entities that match virtually anything. This degrades the performance and quality of ML. Nearly everything in every training phrase will be evaluated as a possible match.
You can learn more about these best practices here, Handling end-user input.
Listing here some useful references:
I hope I was able to provide you with useful insights.
User | Count |
---|---|
2 | |
2 | |
1 | |
1 | |
1 |