Home / Smartbar / How proactive messages work

How proactive messages work

Updated Sep 28, 20262 min read

Proactive messages help visitors at an appropriate moment instead of waiting for them to open Smartbar. Adealo supports contextual Smartbar prompts and explicit automation rules.

Contextual Smartbar prompts

When Visitor AI is live and proactive engagement is enabled, Smartbar can offer help after a visitor spends meaningful time on a relevant page. The prompt may use the page type, campaign context, browsing progression, or scroll depth to choose useful wording and up to two next steps.

Common contexts include pricing, demo, integration, security, and product pages. A prompt can offer a relevant question together with an available next step such as booking a demo, requesting a callback, or talking to support.

Safeguards

  • No prompt is shown when a conversation is already active.
  • Sensitive pages such as checkout, sign-in, account, admin, and billing-portal pages are excluded.
  • A minimum dwell time applies before a prompt can appear.
  • Session frequency limits and a dismissal cooldown prevent repeated interruptions.
  • Mobile prompts follow the Smartbar's proactive engagement setting.

Automation-based proactive messages

Workspace admins can also open Settings → Automation → Workflows and create a rule. Choose a visitor trigger, optional page or business-hours conditions, and an action such as Send message, Show quick replies, or Show article. Templates include help on a pricing page and re-engagement for an idle visitor.

When a visitor engages

Showing or dismissing a prompt does not by itself create a verified AI outcome. When the visitor accepts the prompt or selects an action, Adealo starts or continues the conversation and records the entry context. Any booking, callback, message, or handoff is reported as complete only after its connected workflow confirms success.

Test before enabling broadly

Use a narrow page condition first. Test the delay, wording, quick replies, mobile presentation, dismissal behavior, Inbox context, and conversion workflow before expanding the rule to more pages.