Each flow starts with a trigger. Triggers can be used to reply with content or trigger actions.
We support a number of different triggers and are adding more exotic types along the way.
|Text||Respond to a text or speech message. Add training examples to enable advanced text classification and entity extraction.|
|Event||System triggers like optin events|
|Unknown||The AI cannot match anyhting|
|Location||User shares a location|
|Image||User has sent an image|
|Video||User has sent a video|
|Audio||User has sent an audio file|
|File||User has sent a file or document|
Determine based on what a user says or types what his or her intention is. Next to determining the user intent, the system can extract data from a sentence in the form of entities. Text triggers work with advanced contextual language classification (NLP) and contextual matching algorithms.
Events are system triggers that are usually send using our API. An event is a sort of trigger a user does not visibly notice. You can use events to specifically trigger flows. This is useful for example to automatically show a welcome message or send static content from cloud code.
Note: you can only use events as the starting trigger of a flow.
Whenever the system receives a trigger it cannot match it will be triggered. You can use this for fallback scenarios.
Our AI system learns based on the examples you train for each step. It also works the other way around. You can teach the AI what it should not match. This is especially useful in delicate situations like customer support.
Unknown triggers can be placed within context of a flow. That way you can easily differentiate the reply actions based on the context of a flow.
Note that the unknown is also triggered when a user for example shares an image and you do not have a flow handling this specific situation.
If a user decides to share his or her location you can respond to that. The system automatically adds the latitude and longitude values to the params of the query. Location triggers can also be placed within the context of flows so it also allows.
Image, audio, video, audio and file triggers allow to create responses whenever a user shares one of these types. Just like the location trigger the shared resource is available inside the params of a query and can be used within the context of a Flow.