Smart Matching (ASR/LLM Bridge) - Not Working Properly

Agent ID: agent_676c44a96e38f971e9c40accc7 (version 29)
Call ID: call_6003c3b917b023536ca45dec9ca

Config:

  • BOOSTED KEYWORD: AMOEBA
  • Smart Matching (ASR/LLM Bridge): Turned **ON
    **
    Issue 1:
  • Though guest interrupted Introduction, agent ignored and continued finishing the statement.
  • I have already covered this in my Global Prompt (please check the Global Prompt)
  • I also highlighted the same issue in other Topic Thread, agent fails to follow instructions

Issue 2:

  • User mentioned Amoeba, Agent understood अमीबा → perhaps converted it to english Ameba, sent the same to TOOL Calling and found zero results; told the guest venue is not available with us, guest ended the call.
  • result: LOSS in sales.

What is the point of having so many configuration (boosted KW, Smart Matching, global prompt) options but none works when needed.?

Hey @info29 Sorry for the inconvenience. I’ll forward this to our team for further investigation.

We’ll keep you updated as soon as we have more information.

Best regards

Hey @info29

Team checked the call and for

Agent restarting welcome despite interruptions:
The agent IS detecting your caller’s interruptions. However, in conversation flow mode, when the agent is interrupted during a node’s response, it re-generates a new response for that same node, which restarts the greeting. Your global prompt instruction to “not restart unfinished sentences” applies to the conversational LLM, but the conversation flow node restart behavior takes precedence. You can adjust interruption behavior in the settings.

“Amoeba” not matching :
The ASR correctly transcribed “अमीबा,” but our extraction step (which doesn’t yet use boosted keywords) transliterated it as “Ameba,” as it translates the word into English (based on your prompt). To improve accuracy, consider using an enum if you have a limited set of options to choose from.

Thank You