Bots are a collection of workers that come together to meet a set of customer use cases. These are made up of at least one worker, and at least one way of understanding utterances.
The available worker types are:
- Business Intent Worker: A type of worker that takes a user intent, aligns it to a business intent and interacts with APIs to carry out a set of steps.
- Classic Flow Worker: Uses flow based programming to configure the interaction of the bot
- Action Flow Worker: Uses flow based programming to carry out a process when triggered through a Botnet Action
- NLP Worker: An integration with non-ServisBOT NLP engines such as Lex, Dialogflow or Watson. They all have different capabilities, strengths and weaknesses.
- Filter Worker: Have the ability to respond to page events and trigger botnet actions.
Adding Workers to Bots
Workers can be added to a bot either through the
Add Resource button on a bots detail page in portal, or through the CLI manually by updating the definition of the bot.
- Action flow workers should not be added to the same bot from which they will be triggered.
- Filter workers should always be added to the top of a bot’s worker array
- When adding a worker from the CLI, the worker will have to be existing, or created through a previous step
- Re-ordering of workers in a bot can only be done through the CLI