Proactive Triggers

Proactive triggers let your chatbot reach out first instead of waiting for a click. When a visitor lingers on your pricing page, scrolls to the bottom, or moves to close the tab, the bot can pop up with a relevant message. Used well, this lifts engagement; used badly, it annoys people — so the feature ships with several anti-annoyance limits (covered below).

Getting Started

1. Navigate to Dashboard → Chatbot → Widget Customization → Triggers tab
2. Enable "Proactive Triggers"
3. Add a trigger type and configure the message
4. Save and rebuild the widget

Trigger Types

Nine trigger types are available. Each type fires under different visitor behavior conditions.

Global Settings

These settings apply to all proactive triggers globally.

Response Modes

Each trigger can use one of three response modes to control how the proactive message is generated and delivered.

Conditions & Scheduling

Each trigger supports optional conditions and scheduling to fine-tune when and where it fires.

Conditions

Conditions are AND-combined with the trigger.

Schedule

Trigger Combinations (AND Logic)

You can require that other triggers have also been satisfied before this trigger fires. For example, combine "Scroll Depth 70%" AND "Time on Page 45s" so the message only appears when both conditions are met.

Anti-Annoyance Protection

Proactive triggers include multiple layers of protection to avoid annoying visitors:

1. Session limit — Max triggers per browser tab session (default: 10; lower it to 1–2 to be less intrusive)
2. Daily limit — Max triggers per 24 hours across sessions (default: 20, stored in localStorage)
3. Cooldown — Wait time between triggers (session or persistent)
4. Permanent dismiss — Visitor who closes a message is never messaged again
5. No re-trigger — Each specific trigger fires only once per session
6. Chat open guard — No trigger fires when the chat is already open
7. User message guard — No trigger fires after the visitor has already sent a message
8. Bubble auto-hide — Speech bubble disappears automatically after configured time

Templates

Three pre-built template bundles are available to get started quickly. Loading a template replaces existing triggers (with confirmation).

Analytics

The Triggers tab shows a performance overview table when data is available.

Use this data to optimize your trigger messages and settings. Low response rates may indicate the message is not relevant or the trigger fires too early.

Privacy / GDPR

Proactive triggers store the following data in the visitor's browser:

Important:

• No cookies are set by proactive triggers
• No personal data is collected or transmitted
• Page context (for AI context on reply / AI-generated modes) is extracted from visible text only — no form data, no data-* attributes
• Context text is used for the current API call only and is not stored in the database
• Mention localStorage usage in your privacy policy

Best Practices

• Start simple — Begin with 1-2 triggers and measure performance before adding more
• Keep messages short — 1-2 sentences maximum; be helpful, not pushy
• Set appropriate delays — Time on Page: at least 15-30 seconds. Don't trigger immediately
• Use conditions — Target specific pages rather than firing everywhere
• Monitor analytics — Check response and dismiss rates regularly; adjust or disable low-performing triggers
• Respect visitors — Keep session limits low (1-2), enable permanent dismiss
• Test on mobile — Verify exit intent via tab switch works as expected
• Use templates — Start with a bundle and customize from there
• Combine triggers — Use AND logic for precise targeting (e.g., scroll + time)
• Add a privacy notice — Update your privacy policy to mention localStorage usage