I have an utterance set up for 'Bonding Leave,' but in some cases, we found that the bot not able to distinguish between the pronunciation of 'Leave' and 'Leaf,' as both sound pretty much the same. Take a look at the Utterance History attached, how the bot handles between these two pronunciations. Can we adjust the bot to be more lenient and accept both sounds/pronunciations?
Hi Hannchiad,
3 lines above where you have underlined in Red the customer is prompted confirmation for the "Absence and Attendance" Intent, and the customer says No to the confirmation question, in my experience if the customer says no to the confirmation question, that Intent (in this case Absence and Attendance) is removed from the possible Intents that may be hit in follow up ask for intent actions.
you might find that if the customer says "Bonding Leaf" to the original ask for Intent question it might select that intent, or it may prompt for confirmation.
In saying that you could make it more likely to select that intent by adding more utterances to the intent that include the term Leaf in place of Leave e.g if you have the below utterances
"Apply for leave"
"bonding leave"
"i want leave"
you could add in
"Apply for leaf"
"bonding leaf"
"i want leaf"
and that would make it more likely to select that intent for phrases including the word Leaf
hopefully this helps
Hi @Cam_Stone,
Thank you for your reply and recommendation. However, my concern is that 'Leaf' is just one example. It could also be 'Lift,' 'Live,' or many other possibilities. Continuously adding more utterances doesn’t seem like an ideal solution. I’m hoping if there's a more systemic/AI-driven approach to address this issue.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.