Genesys Cloud - Main

@Anand Gangappa - Out of curiosity, why aren't you using the built-in date slot type?

 Otherwise, I completely agree with Jason/Srikanth from a customer experience perspective.

@Brian Jones Business wants this requirement only

@Anand Gangappa - Out of curiosity, why aren't you using the built-in date slot type?

 Otherwise, I completely agree with Jason/Srikanth from a customer experience perspective.

Interesting. So have you tried the built-in date slot type and it didn't work or does the business refuse to let you try to use the built-in date slot type? The built-in any slot type seems a bit broad to use for dates.

(NOTE: If you're feeling fancy, you could also try an AI-powered slot given that can handle dates spoken just about any way. Only downside is that would require you upgrade the bot to a Virtual Agent and use tokens accordingly.)

@Brian Jones Business wants this requirement only

@Anand Gangappa - Out of curiosity, why aren't you using the built-in date slot type?

 Otherwise, I completely agree with Jason/Srikanth from a customer experience perspective.

Perfect example of virtual agent slots.  I suggest this all the time that you need to look at virtual agents not as bots, but as a piece of the orchestration that you do in your IVR call flow.  In this case, your virtual agent is nothing more than a single Ask for Slot and a prompt in the slot like "caller will provide their date of birth that has to be in the past and output the result as YYYY-MM-DD".  That works EVERY time flawlessly no matter how they say it.  Yes, by doing this, it will convert your IVR to a virtual agent at .5 tokens per call, but the savings in frustration for the caller is well-worth the costs.  You would not have to use this for all flows, bot only when you need type of input.  

Interesting. So have you tried the built-in date slot type and it didn't work or does the business refuse to let you try to use the built-in date slot type? The built-in any slot type seems a bit broad to use for dates.

(NOTE: If you're feeling fancy, you could also try an AI-powered slot given that can handle dates spoken just about any way. Only downside is that would require you upgrade the bot to a Virtual Agent and use tokens accordingly.)

@Brian Jones Business wants this requirement only

@Anand Gangappa - Out of curiosity, why aren't you using the built-in date slot type?

 Otherwise, I completely agree with Jason/Srikanth from a customer experience perspective.