Pro-active triggers

We currently have 3 types of pro-active triggers defined:

• The classic exit intent, which shows a pop-up when people show intention to leave your webshop. As we maintain browsing behavior during one session, we’re able to show similar products and/or featured products that you defined in your webshop, in the same exit pop-up window. Compared to showing a ‘please don’t leave our website’ and/or ‘why don’t you subscribe to our newsletter’, showing related or featured products in the exit intent pop-up creates more user engagement.
• A ‘product page dwell time‘ pop-up of the Corelex chat window: When active, you may configure the timing of this pop-up. Like in the exit pop-up, we show contextual information to user so that there’s better engagement
• A ‘cart abandonment‘ pop-up of the Corelex chat window: In this scenario, the visitor has added products to the shopping cart, but he/she didn’t finish the sale, for instance after 20 or 30 seconds (configurable)

Exit intent #

Overview #

Exit intent automatically opens the Corelex chat when a desktop visitor moves their cursor toward the top of the browser – the gesture that typically precedes closing a tab or navigating away. The popup fires once per session and respects your page exclusion rules: it will not trigger on pages where the widget is hidden.

Heads up: If your site already uses another exit intent tool – a newsletter popup, a discount offer, or a cookie banner – both will trigger at the same time. Only enable this feature if Corelex is your only exit intent interaction on the page.

How it works #

Exit intent fires in two phases:

Phase 1 — Instant (always). The moment the cursor crosses the top-edge threshold, the exit intent popup appears immediately. No API call is made at this point. The featured product shown is drawn from data already loaded on the page, so there is zero latency.

Phase 2 — Contextual (optional). If Have the assistant personalise the message based on browsing behaviour is enabled and the visitor has session signals (viewed products, search queries, cart contents), the agent generates a personalised opening message based on what they were actually browsing. This message follows the instant Phase 1 display.

Settings #

Controls how the content is arranged inside the modal. Available options:

Layout	Best for
Message + product card (default)	Stores that want the agent to open a chat conversation immediately, with a featured product shown alongside
Split — image right, message left	Stores that want a visually branded moment — hero image on the right, eyebrow label, headline, and chat input on the left
Lead capture form	Stores that want to capture an email address before (or instead of) opening a chat

Each layout exposes different configuration fields, described below.

Fields: Message + product card (default) #

This is the simplest layout. When the exit intent fires, a featured product card appears alongside the agent’s opening message. No additional configuration fields are required beyond the behaviour options below.

Fields: Split — image right, message left #

Hero image URL #

The image displayed in the modal. Paste the full URL of any image already uploaded to your WordPress media library or hosted externally. Recommended dimensions: 600 × 800 px (portrait), minimum 400 px wide. Leave blank to show the modal without an image.

Eyebrow label #

A short line of text displayed above the headline – typically used for a soft, attention-grabbing phrase. Shown in smaller text above the main headline.

Example: Please don’t leave our shop!

Keep this under 40 characters. It is not the place for a discount offer – use the headline for that.

Headline #

The primary message shown in the modal. This is the first thing the visitor reads, so make it specific and useful.

Examples:

• Get 10% off your first order
• Still looking for the right size?
• Free shipping on orders over €50

Leave blank if you want the agent’s proactive message (Phase 2) to serve as the opening line without a static headline.

Fields: Lead capture form #

This layout replaces the chat interface with a lead capture form. Use it when your goal is email list growth rather than an immediate conversation. The same hero image, eyebrow label, and headline fields apply, plus the following form-specific options.

Form fields #

Select which fields appear in the form. Email address is always included and cannot be removed.

Field	Notes
First name	Optional. Adds a first name input above the email field.
Last name	Optional. Adds a last name input.
Email address	Always shown. Required for submission.
Show privacy consent checkbox	Adds an explicit consent checkbox below the form fields. Recommended for EU stores to support GDPR compliance.

Submit button label #

The text shown on the form’s submit button. Defaults to Subscribe. Customise to match your offer — for example: Claim my discount, Send me the code, or Get access.

Send lead to #

Where Corelex sends the captured lead data after a successful form submission. Currently available option:

Option	Behaviour
Email notification	Sends an email to the address specified in the Notification email field below

Additional integrations (CRM connectors, FluentCRM, etc.) may be added in future releases.

Notification email #

The email address that receives a notification when a visitor submits the lead capture form. Enter a single address. Leave blank if you have not yet configured a destination — form submissions will not be delivered until this is set.

Behaviour options #

Pre-fill the chat input when the visitor clicks “Chat with us” #

When enabled, the chat input field is pre-filled with a message when the visitor opens the chat from the exit intent popup. The pre-fill text is configured in Language Settings → Exit intent. This reduces friction — the visitor can send with a single tap rather than typing from scratch.

Have the assistant personalise the message based on browsing behaviour #

When enabled, the agent generates a contextual opening message based on the visitor’s session – products viewed, categories browsed, cart contents, and dwell time. This is Phase 2 of the exit intent flow.

The message is generated by the Corelex backend and is specific to the session. The agent does not explicitly reference the data it has collected – it asks a natural follow-up question that makes sense given the context.

If the visitor has no meaningful session signals (e.g. they landed directly on the page they’re leaving), no personalised message is generated and the static headline is shown instead.

Language settings #

The message text shown in the exit intent popup – including the pre-fill text and any language-specific variations – is configured separately under Language Settings → Exit intent. Changes to wording, translations, and per-language overrides are all managed there.

Limitations and known behaviour #

• Exit intent detection is desktop only. On mobile and tablet, cursor-based detection is not available. The feature does not fire on touch devices.
• The popup fires once per session. A returning visitor in a new session will see it again.
• Exit intent respects page exclusions. If you have excluded certain pages from showing the Corelex widget, exit intent will not fire on those pages either.
• If another exit intent tool is active on the same page, both will fire simultaneously. There is no coordination between third-party tools and Corelex exit intent.
• The hero image is loaded at the time the popup fires. Using a very large image file may introduce a brief visual delay on slow connections. Keep hero images under 200 KB.

Dwell time #

Cart abandonment #

Here as well, there are 3 options:

• Off
• All devices
• Desktop only

Enabling this functionality will pop-up the Corelex chat window, after x seconds that someone added a product in the shopping basket but then never navigated to the check-out page. The timing trigger may get updated as what fits best your shopping behavior.