Hello, @Jeff Werner.
I have not found a clear Genesys document that lists every supported DTMF format for builtin:date in a bot flow.
The built-in date slot is documented mainly with spoken/natural language examples, like "June 15" or "next Tuesday," and the resolved value is returned in ISO format, such as 2021-06-15.
For DTMF, I would be careful relying on multiple possible formats. If you need a predictable customer experience, I would use a fixed numeric format, such as YYYYMMDD, and validate it yourself before converting it to a date.
For example, collect 8 digits, validate that the value is a real date, then convert it to the format Architect needs, such as YYYY-MM-DD.
So instead of depending on builtin:date to interpret different DTMF date formats, I would probably handle DTMF dates as numeric input and normalize the value in the flow or with a Data Action/Function.
That gives you more control over validation, retries, and customer prompts.
------------------------------
Arthur Pereira Reinoldes
------------------------------