I am obliged to you for your time and patience.
I have little if any experience of coding. Essentially, Hello World in Basic and C years ago and that from passing and rushed curiosity.
Could you bear with my ignorance a little while longer.
My understanding of a slot is that it will categorise a var iable so that Alexa may be “primed” to expect a particular type of content within that variable.
The slots available to me are: custom, airport, artist,colour,country
Using any or none of these resulted in the “fallback intent” issue.
I can see that the ambiguity that is introduced by a “spoken alphanumeruic” or utterance, as it were, necessitates a slot type categorisation at least to aid the Alexa AI in narrowing down from the infinite possible range of utterances.
Also, if I test the Prototype on laptop then it works. A spoken entry to the Capture variable is recognised and read back correctly in the following linked Speak block!
So, it is clear then that when uploaded to the Alexa device there is a problem. The Alexa AI needs more.
There must be some way that Alexa can deal with un-delimited spoken alphanumeric or utterance. The Alexa Reminder skill has “What do you want to be reminded of” prompting an un-delimited utterance.
My understanding of Choice and Intent and Slots and Utterances is that collectively they are ways of segmenting the possible range of utterances (infinite). Creating Intents delimits the subsection of the possible (very narrowly). Each Intent given typical Utterances and the particular intent further helped in identification by creating additional typically relevant Slot variables.
These, nevertheless, could go nowhere near to accomodating the possible range of utterances, no matter how many of them might be created.
Any idea how the unlimited range of utterances are accomodated in the Reminder skill?
I notice Fallback as an existing Intent in the Choice block. Perhaps if I discover what Fallback delimits then I might be on the right track!
Again, I appreciate you patience.