Behavior triggers let the Chat widget proactively open with a custom message when visitor behavior meets a configured trigger.
The deployed page explains that the bar can respond when a visitor exit-intents, idles, scrolls, abandons a cart, and performs other recognized behaviors.
Open the Agent and select Behavior triggers.
The page contains an Add a trigger form and an Existing section.
The current user-facing creation form provides:
The deployed interface includes these trigger kinds:
Use an Exit Intent trigger when you want the widget to proactively offer help as a visitor appears to be leaving the page.
An appropriate message might offer to answer a last question or help compare options before the visitor leaves.
Idle and Time triggers are intended for situations where the visitor has spent time on the page without actively starting a Conversation.
Use a concise message that offers assistance without making the widget feel intrusive.
A Scroll trigger can be used when visitor engagement with page content reaches the applicable scroll condition in the deployed trigger configuration.
This can be useful on longer pricing, product, service, or educational pages.
A Returning trigger can provide a different proactive experience to a visitor recognized as returning.
Keep the message contextually useful; do not imply knowledge about the visitor that the system does not actually possess.
UTM-related behavior can support campaign-specific engagement when visitor traffic arrives through tracked marketing links.
Use campaign-specific wording only where it remains accurate for the associated traffic.
The deployed interface includes an abandoned_cart trigger kind.
This type is relevant when an applicable commerce integration provides the visitor/cart context required for that behavior.
The form labels the message field Bar opens with message.
The interface recommends keeping the message short and conversational so the widget feels like a helpful nudge rather than a pop-up advertisement.
The Existing section shows the trigger Name, Kind, and configured message.
If no triggers exist, the page explains that triggers can proactively open the bar for behaviors such as leaving, idling, scrolling, returning, or arriving from a UTM campaign.
Use the delete action beside an Existing trigger and confirm the request.
Test changes on an appropriate staging or controlled page before relying on proactive behavior for production visitors.