You should be able to do this. Either create one slot to capture any value, and if string contains an @ assume it is an email if not assume it is an account number. Issue there of course is validating customer input, which is doable but requires some extra thinking.
Or create two slots, both as regular expressions - finding a regular expression for email addresses - a google or LLM can find you one of those easily.
Creating one for an account number format should be fairly straight forward too.
As two slots:


The key is here under utterances, I need to show it examples of what those slots will look like

Then we just do a wait for input:

Then in my task for the intents I'm just going to read back which slot is filled and the value

end result


Does that give you what you are after?
------------------------------
Anton Vroon
------------------------------