Proactive Engagement Templates for Shopify Chat: A Library of Pre-Built Rules

Conditional rules give merchants precise control over chat widget behavior. They also give merchants a blank canvas — and a blank canvas is a usability problem when the merchant doesn't know what kinds of rules other stores find useful, what condition combinations make sense, or what greetings actually convert. The first time a merchant opens the rules editor, they often write nothing because they don't know where to start.

v1.5.0 added a template library for this. Categorized, pre-built rules that the merchant can apply with one click and then customize on top — Welcome Back greetings for returning visitors, mobile-format overrides, exit-intent offers on cart pages, business-hours messaging, and more. The library replaces the blank canvas with a starting position.

The categories

Templates are grouped into six categories, each addressing a different shape of merchant intent:

• Engagement — Welcome Back, First-Time Visitor, Mobile Shopper. Adjusts greeting and tone based on who the visitor is.
• Proactive — Browsing Nudge, Engaged Scroller, Exit Intent Offer, PDP Engagement. Uses the time-on-page / scroll-depth / exit-intent triggers from v2.0.4 to surface chat at high-intent moments.
• Presentation — Search on Collections, Chat on Product Pages, Chat on Mobile. Format overrides scoped to specific page types or device classes.
• Campaigns — Campaign Landing. Adjusts messaging for visitors arriving via campaign URLs (UTM parameters or specific landing-page paths).
• Navigation — Collection Browser. Surfaces search-bar format on collection pages so customers can narrow down through AI without leaving the listing.
• Scheduling — After Hours. Time-of-day rules that adjust messaging when the store team is offline.

The categories grow over time as merchant patterns surface. The shape of the library — opinionated starting points organized by intent type — is what stays consistent.

One-click apply with sensible defaults

Each template applies a complete rule: condition set + action + presentation overrides. Click Apply on the "Exit Intent Offer" template and the rule lands in the merchant's rule list with:

• The exit_intent trigger condition
• A URL constraint scoped to /cart
• Smart-banner format override
• A pre-written greeting tuned for the cart-abandonment moment

The merchant can publish as-is or edit any piece. Most merchants edit at least the greeting copy to match their brand voice; many also tighten or loosen the URL scope ("just /cart" vs "/cart and /checkout"). Templates aren't locked — they're a fully populated starting form.

The library doubles as documentation

Beyond providing starting points, the categorized library is also the implicit documentation for what conditional rules can do. A merchant browsing the templates sees concrete examples of:

• Which condition types are available (URL, device, time-of-day, behavior triggers)
• How conditions compose with AND logic
• What kinds of overrides a rule can apply (visibility, format, greeting, quick questions)
• What greeting copy works for which moment

A merchant who never applies a template still benefits from skimming the library — it answers "what should my rules do?" without forcing the merchant to read a docs page. That's a quieter form of onboarding than a tutorial modal but often a more effective one.

Composing with the rest of the rules system

Templates share the same data shape as merchant-authored rules. A template-applied rule is a regular rule — it shows up in the rule list, sorts by priority alongside everything else, evaluates against visitors with the same matching logic, and can be edited or deleted like any other.

That means a merchant can stack multiple templates: apply Welcome Back, then First-Time Visitor, then Exit Intent Offer, end up with three rules at three priorities, and the first matching rule wins on each visitor. The template library doesn't replace the rules editor — it's a faster on-ramp into it.

Pair this with the trigger conditions that landed in v2.0.4 (time_on_page, scroll_depth, exit_intent), and several of the templates suddenly behave very differently. The Browsing Nudge and Engaged Scroller templates were near-impossible to write before behavior-based triggers existed; they're in the library because they could be in the library — v1.5.0 templates and v2.0.4 triggers landed within a week of each other for a reason.