Genesys Cloud - Developer Community!

Hi all,

Have any voice bot customers had issues recently with the sensitivity of the bot to background noise? Right now, we're having huge issues with the way that the bot is processing any kind of sound, even when there's a prominent voice in the foreground. We're testing across three different orgs and if a chair squeaks just before someone speaks, the bot is processing that sound as the utterance and immediately hits a No Match.

We're getting so many problems with this right now. There's a setting under User Input for Speech Detection Sensitivity, but this is specific to Nuance Recognizer as a Service., not the Genesys bot.

I largely use the V3 engine for Speech to Text, my colleague is using V2 and seeing the same. So I don't think the issue is specific to an engine 

If anyone has this too, I'd be interested to hear about it. I'm about to raise a ticket with Support anyway so if there's a resolution to this, I'll make sure this thread is updated.

Would I be able to get some input from Genesys on this please? Our support ticket has come back and simply said "nothing you can do, raise an idea". But there's a clear issue we're seeing in the voice bots where the bot is processing ANY sound which is creating a big problem with slot matching. 

If any of the product managers would have some time to help, we'd really appreciate it! @Mitchell Mason not sure if this is still your area or not

Thanks

Hi all,

Have any voice bot customers had issues recently with the sensitivity of the bot to background noise? Right now, we're having huge issues with the way that the bot is processing any kind of sound, even when there's a prominent voice in the foreground. We're testing across three different orgs and if a chair squeaks just before someone speaks, the bot is processing that sound as the utterance and immediately hits a No Match.

We're getting so many problems with this right now. There's a setting under User Input for Speech Detection Sensitivity, but this is specific to Nuance Recognizer as a Service., not the Genesys bot.

I largely use the V3 engine for Speech to Text, my colleague is using V2 and seeing the same. So I don't think the issue is specific to an engine 

If anyone has this too, I'd be interested to hear about it. I'm about to raise a ticket with Support anyway so if there's a resolution to this, I'll make sure this thread is updated.

Hi all,

Have any voice bot customers had issues recently with the sensitivity of the bot to background noise? Right now, we're having huge issues with the way that the bot is processing any kind of sound, even when there's a prominent voice in the foreground. We're testing across three different orgs and if a chair squeaks just before someone speaks, the bot is processing that sound as the utterance and immediately hits a No Match.

We're getting so many problems with this right now. There's a setting under User Input for Speech Detection Sensitivity, but this is specific to Nuance Recognizer as a Service., not the Genesys bot.

I largely use the V3 engine for Speech to Text, my colleague is using V2 and seeing the same. So I don't think the issue is specific to an engine 

If anyone has this too, I'd be interested to hear about it. I'm about to raise a ticket with Support anyway so if there's a resolution to this, I'll make sure this thread is updated.

Hi all,

Have any voice bot customers had issues recently with the sensitivity of the bot to background noise? Right now, we're having huge issues with the way that the bot is processing any kind of sound, even when there's a prominent voice in the foreground. We're testing across three different orgs and if a chair squeaks just before someone speaks, the bot is processing that sound as the utterance and immediately hits a No Match.

We're getting so many problems with this right now. There's a setting under User Input for Speech Detection Sensitivity, but this is specific to Nuance Recognizer as a Service., not the Genesys bot.

I largely use the V3 engine for Speech to Text, my colleague is using V2 and seeing the same. So I don't think the issue is specific to an engine 

If anyone has this too, I'd be interested to hear about it. I'm about to raise a ticket with Support anyway so if there's a resolution to this, I'll make sure this thread is updated.