Genesys Cloud - Developer Community!

I ran into something strange and I'm hoping someone can explain it.

I built an application in Architect that uses a combination of Inbound flows, Bot flows, and Common modules. The problem is in the Bot flow, specifically when collecting a Slot value.

When it is deployed into my development Genesys environment, the recognition of the Slot value works as expected. If I say "one two three four five six seven eight nine", the slot value is set to "123456789". However, deploying it to the customer Genesys environment (in FedRAMP), when I say the same utterance, the slot value is set to "123456789." (with the unexpected period at the end). I am able to work around it by adding another RegEx pattern to the slot type and adding an Update Data node to strip out the period if it exists. 

But, I want to understand why it is doing this at all. I did some searching but could only find references to how to work around it, not why it happens.

Any assistance or explanation would be greatly appreciated.

#Architect

------------------------------
Jeff Werner
Software Engineer - Interactive Northwest, Inc.
------------------------------

Hi Jeff,

One thing I'd check is whether the Speech-to-Text engine configured under the bot flow's Supported Languages is the same in both environments.

I'm sure others will be able to add more to this as well, especially if they've worked with both commercial and FedRAMP environments.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Thanks, Phaneendra. I appreciate the quick response. I noticed that one environment is using Genesys Enhanced v2 and one using Enhanced v3. The customer's environment does not have Enhanced v2 available. So, I changed our environment to use Enhanced v3. Now, the period issue is occurring in our lab environment.

So this helped narrow it down to the cause. The next is to get an idea from someone as to why that is the case. 

Thanks again for your response. 

------------------------------
Jeff Werner
Software Engineer - Interactive Northwest, Inc.
------------------------------

Original Message:
Sent: 07-24-2026 11:35
From: Phaneendra Avatapalli
Subject: Bot Flow Slot Recognition sometimes adds unexpected period

Hi Jeff,

One thing I'd check is whether the Speech-to-Text engine configured under the bot flow's Supported Languages is the same in both environments.

I'm sure others will be able to add more to this as well, especially if they've worked with both commercial and FedRAMP environments.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Glad that helped narrow it down! That's interesting that switching from Enhanced v2 to Enhanced v3 reproduced the behaviour. It definitely points towards the STT engine's text normalization or punctuation restoration rather than anything specific to the Bot Flow itself. Hopefully someone from the Genesys team can shed some light on whether this is expected behaviour in Enhanced v3 or simply a difference in how that engine returns numeric utterances.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Original Message:
Sent: 07-24-2026 11:49
From: Jeff Werner
Subject: Bot Flow Slot Recognition sometimes adds unexpected period

Thanks, Phaneendra. I appreciate the quick response. I noticed that one environment is using Genesys Enhanced v2 and one using Enhanced v3. The customer's environment does not have Enhanced v2 available. So, I changed our environment to use Enhanced v3. Now, the period issue is occurring in our lab environment.

So this helped narrow it down to the cause. The next is to get an idea from someone as to why that is the case. 

Thanks again for your response. 

------------------------------
Jeff Werner
Software Engineer - Interactive Northwest, Inc.
------------------------------


Original Message:
Sent: 07-24-2026 11:35
From: Phaneendra Avatapalli
Subject: Bot Flow Slot Recognition sometimes adds unexpected period

Hi Jeff,

One thing I'd check is whether the Speech-to-Text engine configured under the bot flow's Supported Languages is the same in both environments.

I'm sure others will be able to add more to this as well, especially if they've worked with both commercial and FedRAMP environments.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

I figured it out. v2 uses Microsoft Azure and v3 uses AWS. AWS speech to text transcription does automatic punctuation that cannot be turned off. So, if you use v3 and don't want punctuation, you have to do what I did and remove the punctuation in an update data node. 

Thanks again, Phaneendra for putting me on the path to resolution.

------------------------------
Jeff Werner
Software Engineer - Interactive Northwest, Inc.
------------------------------

You're very welcome! Glad it helped narrow things down. Thanks for coming back and sharing the root cause too, that's really useful to know, especially the difference between Enhanced v2 and v3. Hopefully it'll save someone else a bit of troubleshooting in the future.

------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------

Original Message:
Sent: 07-24-2026 11:56
From: Jeff Werner
Subject: Bot Flow Slot Recognition sometimes adds unexpected period

I figured it out. v2 uses Microsoft Azure and v3 uses AWS. AWS speech to text transcription does automatic punctuation that cannot be turned off. So, if you use v3 and don't want punctuation, you have to do what I did and remove the punctuation in an update data node. 

Thanks again, Phaneendra for putting me on the path to resolution.

------------------------------
Jeff Werner
Software Engineer - Interactive Northwest, Inc.
------------------------------