Conversation block
The foundational building block of any conversation skill. Each block is a contextual unit that you can think of as a "topic" of a conversation, or, if you come from a web development background, imagine it as a page in your sitemap.
When to use?
Basically, all the time. This is your bread and butter block for the vast majority of use case scenarios.
How to use?
After you add a conversation block, fill out the Elements and Processors that will be used to handle a section of a given conversation.
Special role conversation blocks
There are several special types of conversation blocks that differ from the standard one.
- Session started: A block with this role, if present, is always executed first when a new session starts.
- Session ended: Like the above, if this block is present, it is called right before a session ends.
- Service processors: This block only has a processors slot which is active throughout the entire service. Useful for things like users asking for help.
- Media block: Handles media (audio) requests, such as starting playback, shuffling, rewinding, etc. Refer to the Media block specific help file for more details.
- Loop block: Given a collection of items, runs once for each item in the collection. Refer to the Loop block specific help file for more details.