Genesys Cloud - Developer Community!

 View Only

Sign Up

Expand all | Collapse all

Architect DetectLanguage Function: Need for Lower Confidence Threshold - Share Your Experience

  • 1.  Architect DetectLanguage Function: Need for Lower Confidence Threshold - Share Your Experience

    Posted 09-23-2026 09:44
    Edited by Minhaj Mubashir 09-23-2026 09:45

    Problem Statement

    The Architect language detection function DetectLanguage currently has a very high confidence threshold (99%) that frequently returns NOT_SET, making it difficult to route customers effectively in multilingual environments.

    Proposed Solution

    Extend the DetectLanguage function (or create a new variant) that accepts a confidence threshold as an input parameter, allowing developers to set lower thresholds (e.g., 80%, 70%) based on their use case.

    An alternative enhancement could return multiple possible languages when confidence is uncertain (e.g., "Swedish or Norwegian"), enabling flows to ask clarifying questions.

    Use Case Examples

    Example 1: Short Chat Messages

    1. Customer enters: "Hello, I need your help with placing an order"

    2. DetectLanguage applied with default 99% threshold

    3. Returns: "NOT_SET" (too uncertain)

    4. NEW function with 80% threshold

    5. Returns: "English"

    6. Route to English queue + set attribute "Language detection 80%"

       to inform agent of confidence level

    Example 2: Ambiguous Short Phrases

    1. Customer enters: "Hej"

    2. Function returns: "Swedish or Norwegian"

    3. Flow asks: "Do you want to chat in Swedish or Norwegian?"

    4. Customer clarifies preference

    Business Impact

    • Improved routing accuracy for multilingual contact centers
    • Reduced customer frustration from being routed to wrong language queues
    • Better agent efficiency with confidence indicators
    • Flexibility to balance confidence vs. functionality based on use case

    Related Idea in Ideas Lab

    This enhancement has been submitted to the Product Ideas Lab (SSAAOB-I-442): https://genesyscloud.ideas.aha.io/ideas/SSAAOB-I-442

    Current Status: No Plan to Implement (as of July 2026)
    Current Votes: 3

    The product team has indicated they revisit ideas if demand increases, so customer votes and feedback matter!

    Discussion Questions

    • Are you experiencing similar challenges with DetectLanguage?
    • What confidence threshold would work for your use cases?
    • How are you currently working around this limitation?
    • Would multi-language return values be helpful for your flows?

    Please share your experience and consider voting on the idea if this impacts your implementation!

    Thank you,



    ------------------------------
    Minhaj
    Technical Account Manager
    ------------------------------



  • 2.  RE: Architect DetectLanguage Function: Need for Lower Confidence Threshold - Share Your Experience

    Posted 09-23-2026 10:00
    Edited by Guilherme Hernandez Hubner 09-23-2026 10:04

    Hi Minhaj,

    I think this would be particularly useful in real-world flows where customers often start with very short messages. In those cases, having more flexibility around how the language result is handled could make the flow more practical, rather than treating an uncertain result as simply NOT_SET.

    Another useful option could be allowing the flow to handle uncertain results differently depending on the languages involved. For example, if two languages are very close and the message is too short to distinguish them, the flow could ask the customer to confirm their language instead of immediately falling back.

    Also, just a quick note: the link attached to the post seems to be unavailable. When I try to access it, I get a “Record not found” message, saying that the record may have been deleted or that I may not have permission to access it. You may want to check whether the link is still accessible.