Just a thought...possible workaround for now (though obviously imperfect).
When transferring to voicemail, send the call to another flow which just uses the two supported languages. Have logic in a task which uses a Switch action to choose one of four options based on Participant Data set in the previous flow, let's say.
For the Supported languages, use a Set Language for the non-default, then do the voicemail transfer using a prompt in that language, and all the TTS stuff should be fine for that language (and the one using the Default language)
For the non-Supported languages, use the default (English, or whatever) and just have a User prompt that is designated as English, but actually recorded in Thai or whatever, and use that for the Pre-Transfer Audio (same for Failed Transfer Audio). The later prompts for further options will be in English, but most folks just hang up after leaving a message...so it will usually be ok.
Might that work as an interim measure?
------------------------------
George Ganahl
Principal Program Manager
Genesys
------------------------------
Original Message:
Sent: 10-09-2018 13:22
From: Sven Schiller
Subject: Transfer to Voicemail for "other" languages
Thanks Melissa for clarifying. All I could see was the voicemail prompt in the system prompts.
It would be nice to have the ability to offer basic voicemail, i.e. "Leave a message after the tone" instead of having no support for languages not supported for extended voicemail. I'll open a change request.
Best,
------------------------------
Sven Schiller
Kognitiv
------------------------------
Original Message:
Sent: 10-08-2018 09:29
From: Melissa Bailey
Subject: Transfer to Voicemail for "other" languages
Sorry there isn't a workaround. Yes voicemail is limited to languages with TTS support b/c the app uses more than just the initial voicemail prompt you can select in architect, i.e. the options if you press the pound key after leaving the message.
------------------------------
Melissa Bailey
Genesys - Employees