Triggers 101: manual, event and screen-based
Learn how to trigger Kletso from user input, real-world events or whatever screen the user is on.
A chatbot that only waits for a tap on a launcher misses most of its moments. Kletso has three kinds of triggers, all configured in the dashboard and fired by the SDK.
Manual
The classic launcher. Call Kletso.open() from any button, menu or gesture, optionally with context such as the current order id.
Event-based
Send events from your app with Kletso.track("cart_abandoned"). Rules in the dashboard decide who sees a proactive message, with what copy, and how often. Frequency caps stop the bot from becoming noise.
Screen and time-based
On web the trigger can watch routes; on mobile it can watch named screens. Combine with a delay, for example open on /checkout after twenty seconds of inactivity, and add audience rules such as plan or country.
Testing triggers
Every trigger has a preview mode. Fire it against a test user, watch the conversation, tweak the copy, publish. No redeploys, ever.