Assistant uses one renderer across all supported surfaces, so catalogue rules, language, knowledge and appearance remain consistent. Placement controls decide where and how the experience appears.

Global floating widget

Enable Settings → General → Show a floating chat bubble on the storefront for site-wide access. Configure size, side and offsets under Settings → Embed, and appearance under Settings → Appearance.

Use the floating widget when visitors should reach Assistant from most public pages. Test pages with other fixed controls before launch.

Reusable embed profiles

Under Settings → Embed → Reusable embed profiles, each profile has a stable ID and its own:

• label;
• inline or floating mode;
• width and height;
• launcher size;
• left/right side and offsets;
• mobile layout.

The package starts with inline-standard and floating-compact. Create descriptive IDs before publishing them; changing an ID later breaks shortcodes or snippets that refer to it. Removing a profile on save should be treated as a compatibility change.

Shortcode

Use the native shortcode in a WordPress post, page or shortcode-capable builder:

Use a saved profile when the page needs a reusable configuration:

Keep the shortcode in a container wide enough for product cards and long translated labels. Do not paste it into code that escapes shortcodes as plain text.

Gutenberg block and PHP helper

Assistant registers a dynamic block named NextlerAI Assistant. Add it from the block inserter and choose the intended profile/options.

Theme and plugin developers can call the plugin’s native render helper instead of duplicating markup. Use the helper only after the plugin has loaded, and guard custom theme code so the page does not fatal when Assistant is temporarily disabled.

Elementor widgets

Assistant adds three widgets:

• NextlerAI Assistant Chat: inline panel or launcher, with heading, input placeholder and inline height.
• NextlerAI Assistant Search: semantic product search with heading, placeholder, product count and 1–4 columns.
• NextlerAI Assistant Recommendations: context/cart-aware products with heading, count and 1–4 columns. On a product or product-category page it receives that page context.

Each widget also inherits shared style controls. Elementor is not required for the global widget, shortcode, Gutenberg block or external embed.

External website embed

The external embed is opt-in and renders an isolated iframe hosted by the licensed WordPress site.

1. Open Settings → Embed → External website embed.
2. Enable the external loader.
3. Add one allowed HTTPS origin per line, such as https://example.com.
4. Use a wildcard only as an explicit subdomain rule such as https://*.example.org.
5. Choose the mobile layout.
6. Copy the generated loader snippet to the approved external site.

Optional data attributes can override mode, width, height, side, offsets and launcher size. The public widget ID identifies the renderer; it is not an API key.

The loader uses an origin-scoped, short-lived token. API keys and transcripts do not enter the host page. For security, cross-site embeds intentionally disable sensitive commerce/account actions: cart, checkout, order lookup and stock-notification subscription. Use an on-site embed when those actions are required.

Caching and content-security checks

After adding or changing an embed:

• clear WordPress, page-builder, CDN and external-site caches;
• confirm the external origin matches exactly, including scheme and port;
• allow the licensed site’s frame/script endpoints in the external site’s Content Security Policy when applicable;
• verify that privacy/cookie controls do not block required requests without a clear recovery path;
• test token expiry by reloading after the previous session ends.

Troubleshooting

• Shortcode appears as text: use a shortcode-capable content area and confirm Assistant is active.
• Blank Gutenberg/Elementor preview: verify the licence runtime gate and provider configuration; test the published page as well as the editor.
• External iframe says invalid/expired: verify the exact allowed origin, clear cached loader code and reload.
• External embed works on one subdomain only: add every exact origin or a deliberate wildcard-subdomain entry.
• Cart/checkout unavailable externally: expected security boundary; place Assistant on the licensed WooCommerce site.
• Duplicate bubble: the global widget and a floating profile are both enabled on the page.
• Mobile panel is clipped: select sheet/full-screen mobile mode or reduce contained dimensions.

Verification checklist

• Every used profile ID is stable and documented.
• Only the intended surface appears on each template.
• Shortcode, block or Elementor output works logged out.
• External origins are minimal and HTTPS.
• External embed does not expose keys or enable sensitive commerce routes.
• Mobile, keyboard, cache and CSP tests pass.