Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  Set

    Posted 08-26-2020 11:21
    No replies, thread closed.
    If I have a Call Flow that Play Audio that is a Prompt like this with audio for two languages, English (us) and Swedish...
    LanguagePrompt

    And I have ticked Swedish as the "Default" in Supported Languages...
    SetDefaultLanguage

    Shouldn't Architect play back the Swedish variant on the audio? For me, it always default to the English prompt. I have to use a "Set Language" -> Swedish action to get the Swedish track to play. 

    To me, its seems intuitive that the prompts should use the "Default" as set in the Supported Languages area?
    #ArchitectureandDesign

    ------------------------------
    Joel Hellman
    Hi3G
    ------------------------------


  • 2.  RE: Set

    Posted 08-26-2020 11:22
    No replies, thread closed.
    Sorry for the bad subject line, seems you can't edit the subject once you posted 😓

    ------------------------------
    Joel Hellman
    Hi3G
    ------------------------------



  • 3.  RE: Set

    Posted 08-26-2020 11:30
    No replies, thread closed.
    The flow will select which language to choose based on the following in order of priority:
    1) If the dialstring includes a language that the flow supports, it will be used.
    2) If the trunk has a language specified that the flow supports, it will be used.
    3) The default language in the flow is used.

    You're probably running into 1 or 2.

    ------------------------------
    Melissa Bailey
    Genesys - Employees
    ------------------------------



  • 4.  RE: Set

    Posted 08-27-2020 01:16
    Edited by Joel Hellman 08-27-2020 01:26
    No replies, thread closed.
    I checked and found our Admin > External Trunk Configuration > General > Language is set to English (us-eng). Swedish is not an option there however, its not in the list though its otherwise supported in Architect etc. That seems like it might be scenarion 2?  

    This seems counter-intuitive. Typically, you expect that "local configuration" wins out, eg. locally scoped variables, CSS, etc. If I change the default language to Swedish in the Supported Languages settings for a particular Architect Flow, but that setting is ignored because of an upstream setting, that feels weird.

    Since the set Language action doesn't take effect until the next Architect Task for Call flows, and defaults to our non-default language, it makes for some akward Flow designs in each flow (as we need to first initialize Swedish, then offer an opt-in for English, and then possible switch back to English in the case the caller opted in for English).


    ------------------------------
    Joel Hellman
    Hi3G
    ------------------------------

    Original Message


Related Content