Quick reminder: chatbot conversations built with Activechat consist of multiple skills, and these skills are triggered by events. There are custom events that you can trigger with the SEND or TRIGGER blocks, and system events, that are triggered automatically upon certain conditions.
Please note that system events can also be triggered with “/” commands (type “/start” in the conversation to trigger the “start” event, for example).
Here is the complete list of system events
|start||Triggered when user stasrts communicating with the chatbot. On Facebook Messenger – when user clicks “Get started” button, on Telegram – when user clicks “Start” button, on website chat widget – when new user is opening a web-page with chat widget installed for the very first time. By default, is handled in the “start” system skill.|
|default||Triggered on every new message from the user to the chatbot, except situations when there is an active LISTEN block waiting for user input. By default, is handled in the “default” system skill.|
|_mute||Triggered when chatbot administrator clicks the “Pause” button in the Conversations list. By default, is handled in the “_mute” system skill.|
|_page_visit||Triggered on every new message from the user to the chatbot, except situations when there is an active LISTEN block waiting for user input.|
|_error||Triggered when there’s a run-time error in one of the chatbot blocks and there are no blocks connected to the ERROR exit in that block. By default, is handled in the “_error” system skill that sends e-mail notification to the admin’s email address.|
|customer_updated||Triggered when customer info is updated in Shopify or WooCommerce back-end.|
|order_updated||Triggered when order info is updated in the Shopify or WooCommerce back-end.|