Scenarios

• Let Breezaro decideThe assistant picks the moment itself and writes the message from the content of the page the visitor is on. That page has to be in the knowledge base, otherwise nothing appears. With consent waiting enabled, this mode runs only after acceptance and stays off after refusal.
• Custom rulesYou build scenarios from conditions and either write the message or let the assistant write it. Custom text needs no knowledge base. It can display locally without consent when all conditions use only the current page or a fixed delay, with a message in the visitor’s language. Adding a history or page-count condition makes the whole scenario wait when consent waiting is enabled.

• Page addressEquals, contains, or matches a pattern. The value can be a whole address or a path on its own, so /pricing works just as well as https://example.com/pricing; a path on its own ignores the domain. In a pattern an asterisk stands for any text, and the pattern is compared against both the full address and the path, so /pricing* and */pricing* both work. Tracking parameters such as utm_*, fbclid or ref are removed before matching, so a rule written on one of them never fires.ExampleMatches pattern · /pricing*
• Time on pageFor local custom text before consent, an “at least” condition acts as a fixed display delay and sends no timing data. With optional collection permitted, conditions can use measured time on the current page; only time while the tab is visible counts.ExampleAt least · 20
• Pages viewedHow many pages the visitor has seen during this visit. With consent waiting enabled, counting and the whole scenario wait for acceptance; they stay off after refusal. Pages viewed before acceptance are not added later.ExampleAt least · 4
• First view this visitTells a first view of a page from a return to it. Requires browsing history to be enabled. With consent waiting enabled, the whole scenario waits for acceptance and stays off after refusal.ExampleIs · Yes
• Distinct pages seenHow many different paths matching the pattern the visitor has viewed. For example, /product/* with a count of 3 means at least three different products. A lone * means any page. Requires browsing history to be on. With consent waiting enabled, the whole scenario waits for acceptance and stays off after refusal.ExampleAt least · /product/* · 3

1. 01
   Choose the Custom rules mode

   Switch the mode in Settings and save. Without it scenarios are not used, even when they are finished.
2. 02
   Create a scenario

   Pick a template, or start blank and add conditions. A sentence builds up under the conditions telling you when the scenario fires.
3. 03
   Try it without publishing

   Expand Try scenarios in the dialog, enter an address and a time on page, and run it. Every condition reports whether it fits. It works on an unsaved scenario too.
4. 04
   Switch it on and check in the browser

   Turn on Reach out to visitors at the top of the page. Then open your site in a new tab and test acceptance, refusal and withdrawal in the connected banner. Before acceptance, only eligible local text appears. After acceptance, AI or history-based scenarios can run and stored per-visit limits apply.

Maximum messages per visit sets how often the bubble may appear during one visit. Minimum gap keeps a pause between them. Offer again after the bubble is dismissed decides whether a closed bubble may come back later in the visit. Excluded addresses rule out pages where an approach is wrong, typically the cart or the checkout: /cart* covers /cart as well as everything under /cart/, and a pattern can carry at most 8 asterisks.

Append ?breezaroDebug=1 to the address of any page with the widget, or set localStorage.breezaro-debug to 1 in the browser, and the console prints [breezaro:proactive] lines for every ask and its outcome.

A message written by the assistant adds one credit to the conversation it starts, and only when the visitor replies. Scenarios with your own text and the welcome bubble cost nothing. Writing one is also capped per day, per bot, by your plan: the assistant composes an opener once per page and language and then reuses it, so the cap limits how much new ground a busy day can cover, not how many bubbles visitors see.