Thanks for the suggestion on using regex - we are already applying regex to enforce the 10‑digit requirement for phone number. What we're trying to understand is why the same built‑in numeric slot behaves differently depending on the tag.
This difference in behavior is what we'd like to clarify. Is the formatting and partial confirmation logic hard‑coded specifically for numeric slots named as phone number? If so, it would be helpful to know whether similar formatting rules exist for other built‑in numeric slot types, so we can be confident that account numbers or other identifiers won't be affected in the future.
Original Message:
Sent: 05-05-2026 13:42
From: Rodrigo Soares
Subject: Genesys Bot
Hello Vinaya,
The builtin Numeric Slot will accept any numeric input, so depending on how your user is entering this information, the system may accept fewer digits as valid inputs. To prevent that, I would recommend you using regex, if possible, like /b/d{10}/b or /b/d{3} /d{3} /d{4}/b. This would guarantee the 10 digits are captured.
https://help.genesys.cloud/articles/use-custom-regular-expression-slot-types-in-a-bot-flow/
Regards,
------------------------------
Rodrigo Soares
NALA Team Lead
Original Message:
Sent: 05-05-2026 11:42
From: Vinaya Mente
Subject: Genesys Bot
Unexpected Behavior with Phone Number Slot Formatting in Genesys Dialogue Engine Bots
We've run into an unusual behavior with the Genesys Dialogue Engine bots and wanted to check if others have seen the same.
We created a numeric slot (builtin) and tagged it in an intent designed to collect phone numbers. For example, the utterance: "My phone number is 1234567890."
When the bot uses Ask for Intent to collect the phone number, the response is automatically formatted as 123-456-7890. During confirmation, the bot only asks about the last four digits, which isn't ideal.
Interestingly, this doesn't happen with other numeric slots. For instance, when we use a 10‑digit numeric slot for account numbers, the formatting issue doesn't occur. It seems to be specific to slots tagged as phone numbers.
As a workaround, we're currently using the Ask Slot block for phone numbers, which avoids the formatting problem. But we'd like to know:
- Is this a known issue with phone number numeric built-in slots?
- Should we expect similar behavior with other 10‑digit numeric slots in the future?
Any insights or confirmation from the community would be really helpful
#Architect
------------------------------
Vinaya Mente
------------------------------