Start the right conversation before they ask.

The four triggers

• First message — greet visitors the moment they open the widget. Your baseline welcome, per locale.
• Page visit — fire when a visitor lands on matching URLs. "Working on pricing? Ask us about volume discounts" beats a generic hello every time.
• API trigger — fire from your product. Track usage_limit_reached or trial_started via the event API and map events to messages in the dashboard.
• Email capture — ask anonymous visitors for their email at the right moment; captured emails create contacts and enroll lifecycle campaigns.

Display modes

• Bubble — a teaser next to the launcher. Low-key, dismissible.
• Open — the widget opens with the message. Use sparingly; high intent pages only.

Guardrails

• Frequency caps — limit how often a visitor sees any automation, per automation and globally. The difference between helpful and spammy.
• Conditions — target by page, locale, or visitor properties. Paying customers shouldn't see trial-upgrade nudges.
• Locale-aware copy — write each message per language; the widget serves the visitor's locale automatically.

Recipes

• Pricing page — page visit trigger: "Happy to help you compare plans — what are you solving for?"
• Churn watch — API trigger on usage_dropped: open with a check-in offer.
• Cart hesitation — page visit on checkout: bubble with shipping/returns answer links.

API surface

GET  /api/widget/automations/config      # client-side trigger config
POST /api/widget/automations/evaluate    # evaluate triggers for a visitor

Client-side evaluation keeps targeting logic in your control; server-side rules (caps, conditions) are enforced for you.