B Blengi docs

Embed the widget

Inline embed in your pages

Diese Seite ist noch nicht auf Deutsch verfügbar, daher lesen Sie sie auf Englisch.

Besides the floating launcher, the same agent can sit inside your pages — between the products on a category page, next to the product details on a product page. The inline block runs no chat of its own: a chip click, or a typed question and Enter, opens the floating chat with that question already asked. One agent, one session, one transcript, and the page context goes along.

Place it

<div data-ai-assistant-inline></div>

Anywhere in your template, as many times as you like — a WordPress Custom HTML block, a page-builder HTML widget, a theme file. The widget script you already load finds every block and renders a card in it. Nobody needs access to your site for this: the block is the whole integration, and everything about it — copy, layout, colours — is managed from the dashboard afterwards. The snippet with a copy button is under Website › Install code › Inline block (optional). The snippet uses the neutral data-ai-assistant-inline, which names no product, so it fits a white-label install. Blocks pasted earlier with data-pitchbar-inline or data-blengi-inline keep working; all three names do the same.

With no attributes and no settings the card shows the segment's persona and greeting and the agent's starter questions — whatever the floating chat would show on that page.

One-click placement (no template edits)

under Website › Place the block on your pages you open one of your own pages, hover to see an element, and click the spot where the block should go, for example the add-to-cart button. Choose Below it, Above it or Inside it, at the end, and the pages it is for: /product/* is every page under /product, /* every page, / the homepage. That is all: with only the normal script tag on the site, the widget adds the block next to that element on every matching page. Browse to another page follows the site's links in the preview to find, say, a product page.

  • The element is remembered as a CSS selector that prefers what stays the same across pages: an id, a button's name (WooCommerce button[name="add-to-cart"], Shopify button[name="add"]), the element's own classes, and only then its position. You can edit it before saving.
  • A page that builds its content late is watched for 8 seconds. When the element is not on a page, the chat button is the way in there, and the Widget Monitor shows Block not placed (at most once an hour per placement).
  • Several placements per AI employee are fine (product pages and category pages, say); each one can be switched off or removed.
  • The preview is a copy of your page without its own scripts, so a part that only your scripts draw may be missing there; pick a nearby element that is in the page itself.

Placed automatically for your shop system

On a WooCommerce, Shopify, PrestaShop, Magento, Shopware or OpenCart shop the block can place itself, without a click: below the add-to-cart button on the product pages (WooCommerce form.cart on /product/*, Shopify the add-to-cart form on /products/*). The Website page shows it as Placed automatically, with Switch off.

  • New AI employees have it on. Existing ones keep their pages as they are until the owner clicks Place automatically.
  • A place of your own wins: once you pick a spot (also one you then switch off), the automatic place stops. Switch off stops it too.
  • It follows the shop system our server read from your site (when the AI employee was set up, by Check installation, or right after the widget first saw the shop). The widget's own guess is only shown to you; it never moves the block by itself.
  • A page that already has a block of its own (a data-ai-assistant-inline element, or the WordPress plugin's answer block) gets no second one.
  • Pages without the element simply show the chat button; these misses are not reported to the Widget Monitor.

Appearance and copy from the dashboard

Appearance › Inline block manages the block without touching the site. Two modes:

  • Match the floating widget (default) — the block takes the theme's accent, corner radius and launcher icon. Nothing to set; a bare block already looks like the chat.
  • Customize inline appearance — background, border, text, muted text, title, accent, text on accent, input background and border, chip background, border and text; corner radius, padding, avatar size; shadow on or off.

In both modes you can set the layout (As set on the page, card, bar or answer in the block; a chosen layout applies to every block on the site, whatever the page's own data-layout says), how many starter questions show, whether the avatar shows, and the block's title, subtitle and input placeholder. Filled copy fields go through the same translation overrides as the launcher label; empty ones fall back. The live preview on that page renders a real block.

Where the block's content comes from

The block holds nothing itself. On every page load it asks the dashboard with the page URL and the page's own product category, and the dashboard decides — the site only says "render the block here":

  • Starter questions: the matched segment's questions → automatic page questions for this page → the agent's own questions → live product questions from the page's product data.
  • Title: the block's data-title → the dashboard's inline title → the segment's persona name → the agent's.
  • Subtitle: the block's data-subtitle → the dashboard's inline subtitle → the segment's greeting → the generated page line → the agent's welcome message → "Ask anything".
  • Segment: by URL path first; when no path claims a product page, by the category the page declares in its JSON-LD or breadcrumb, matched against the segment's product categories.

Precedence, lowest to highest: shipped defaults → dashboard settings → the block's own data-* attributes and the site's --pb-inline-* CSS. A web agency that styled the block by hand keeps every override; a customer who never wrote CSS manages everything from the dashboard. The one exception is the layout: a layout chosen in the dashboard (card, bar or answer in the block) applies to every block, also where the page's code sets its own data-layout; the attribute decides only while the dashboard says As set on the page, so switching on Answer in the block never needs a template change.

One agent, a different role per place

Do not create an agent per category. Create a segment per place, matched by URL pattern, and give it its own persona name, greeting, starter questions and instructions:

SegmentURL patternRole
Thermosokken/thermosokken*Advisor within that category: "Niet zeker welke thermosok?"
Product pages/product/*Product specialist — the widget also reads the product's JSON-LD, so no segment per product is needed
Defaulteverything elseGeneral shopping assistant

The segment drives both the inline block and the floating chat on that page, and its instructions are appended to the agent's prompt for that conversation.

Per-block options

All optional. Anything absent falls back to the segment and the agent.

AttributeWhat it does
data-titleHeading. Default: the persona name.
data-subtitleLine under the heading. Default: the segment greeting.
data-placeholderInput placeholder. Default: "Ask a question…" (translated).
data-promptsThis block's starter questions, pipe-separated: Help mij kiezen|Koude & klamme voeten?. Default: the agent's.
data-max-promptsHow many to show, 1–6. Default 3.
data-avatarImage URL for the avatar. Default: the launcher icon.
data-hide-avatarPresent = no avatar.
data-layoutcard (default, stacked), bar (one row on desktop, stacks under 640px) or answer (the answer appears in the block itself, see below). Applies while the dashboard's layout is As set on the page; a layout chosen under Customize › Inline block › Layout applies to every block on the site, whatever this attribute says.
data-contextExplicit placement context, see below.

Styling with CSS — for agencies

The block lives in its own shadow root so your CSS cannot break it, but it is themed entirely through CSS custom properties, which inherit into the shadow root. Set them on the block itself or on any ancestor; a variable you set beats the dashboard's setting for that knob:

[data-ai-assistant-inline] {
  --pb-inline-bg: #f1f8f3;
  --pb-inline-border: 1px solid #cfe6d6;
  --pb-inline-radius: 14px;
  --pb-inline-padding: 18px;
  --pb-inline-font: "Inter", sans-serif;
  --pb-inline-title: #0b3d1f;
  --pb-inline-text: #1a1a1a;
  --pb-inline-muted: #4b5f52;
  --pb-inline-accent: #1e8a4c;       /* send button, initial, focus ring */
  --pb-inline-accent-ink: #fff;      /* text on the accent */
  --pb-inline-chip-bg: #fff;
  --pb-inline-chip-border: 1px solid #cfe6d6;
  --pb-inline-chip-color: #0b3d1f;
  --pb-inline-input-bg: #fff;
  --pb-inline-input-border: 1px solid #cfe6d6;
  --pb-inline-shadow: none;
}

The full list:

VariableDefault
--pb-inline-bg#fff
--pb-inline-border1px solid #e6e8ee
--pb-inline-radius16px
--pb-inline-padding16px
--pb-inline-gap10px — between header, input and chips
--pb-inline-max-width560px (card), 100% (bar)
--pb-inline-height380px — the fixed height of the answer layout
--pb-inline-shadowsoft
--pb-inline-fontsystem-ui stack
--pb-inline-title, --pb-inline-title-size, --pb-inline-title-weighttext colour, 15px, 700
--pb-inline-subtitle-size12.5px
--pb-inline-text, --pb-inline-muted#131720, #6a7280
--pb-inline-accent, --pb-inline-accent-inkthe agent's accent, #fff
--pb-inline-avatar-size36px
--pb-inline-input-bg, --pb-inline-input-border, --pb-inline-input-radius, --pb-inline-input-size#fff, 1px solid #e6e8ee, 999px, 13.5px
--pb-inline-chip-bg, --pb-inline-chip-border, --pb-inline-chip-color, --pb-inline-chip-radius, --pb-inline-chip-size, --pb-inline-chip-gap#f7f8fa, 1px solid #e6e8ee, text colour, 999px, 12.5px, 6px
--pb-inline-chip-hover-bg, --pb-inline-chip-hover-color12% accent tint, text colour

Anything else: ::part()

Every piece is exposed as a shadow part, so ordinary theme CSS can restyle it completely — fonts, transforms, pseudo-elements, media queries, anything:

[data-ai-assistant-inline]::part(chip) { text-transform: uppercase; letter-spacing: .02em; }
[data-ai-assistant-inline]::part(title) { font-family: "Fraunces", serif; }
[data-ai-assistant-inline]::part(button) { border-radius: 8px; }
@media (max-width: 640px) {
  [data-ai-assistant-inline]::part(chips) { display: none; }
}

Parts: card, header, avatar, title, subtitle, form, input, button, chips, chip, answer.

Answer in the block

With the answer layout (Customize › Inline block › Layout › Answer in the block, which applies to every block on the site whatever the block's own data-layout says — or data-layout="answer" on one block while the dashboard says As set on the page) a question is answered inside the block, so the visitor stays on the page: the chat window does not open and the block keeps a fixed height (--pb-inline-height), so the page does not jump while the answer arrives.

  • Before the first question: the title, the input and the starter questions. After it: the question, a status line while it is being answered ("Searching your site…"), then "Based on the knowledge of your site" with a Learn more link to the first source, the answer in at most two short paragraphs, and two follow-up questions.
  • ‹ › browse the earlier questions and answers of this page view; Continue in chat opens the chat with the same conversation.
  • Questions from the block count as inline questions in the analytics; the server keeps their answers short (input_source=answer).
  • Per page: under Customize › Inline block › Answer in the block on these pages list paths, one per line (/product/*); on those pages the block answers in itself, whatever the layout or the block's own data-layout. The block is placed with the element above, with Website › place the block (no site access needed — once the shop system is known, from the crawl or because the widget saw it on a page, that section also suggests its usual place, such as below WooCommerce's add-to-cart button, in one click), or on WordPress with the [ai_answer] shortcode, the AI answer block, or — on WooCommerce product pages — the plugin's setting Answer block on product pages (below the summary, below the add-to-cart button, or as a tab).
  • Settings (Customize › Inline block): the block's height, your own source line instead of "Based on the knowledge of …", and a disclaimer under every answer.
  • Measurement: the block reports when it is shown, a question, a follow-up question, Continue in chat, and — on WooCommerce with the plugin — an add to cart after a question. You see them under Results › Answer block; with GA4 switched on they also reach your own GA4 as block_impression, block_question, block_followup, block_continue and block_add_to_cart (with your event prefix).

Passing context

Automatic. Every turn already carries the page URL, title, meta tags, JSON-LD, headings and visible text, so category and product context arrive without you doing anything. On a product page the agent is told which product is open.

Explicit, per block. data-context says where on the site the question was asked from, in the terse key: value; key: value form or as a JSON object. It rides along with the first message that block sends and reaches the agent as "Asked from: category: Thermosokken" — deliberately a fact about the place, never an instruction.

<div data-ai-assistant-inline
     data-context="type: category; category: Thermosokken"></div>

<div data-ai-assistant-inline
     data-context='{"type":"product","sku":"STP-BOSTON-ZW","name":"STAPP Boston Thermo — Zwart"}'></div>

Up to 10 keys, 120 characters each. For page-wide CMS context (post type, taxonomies, product fields on every turn) use data-page-context on the script tag instead — see WordPress & page builders.

A category-page example

<div class="advice-block"
     data-ai-assistant-inline
     data-layout="bar"
     data-title="Niet zeker welke thermosok?"
     data-subtitle="Stel je vraag of kies hieronder — ik denk met je mee."
     data-placeholder="Bijv. welke sok bij koude, klamme voeten?"
     data-prompts="Koude & klamme voeten?|Help mij kiezen"
     data-context="type: category; category: Thermosokken"></div>

<style>
.advice-block {
  --pb-inline-bg: #eef7f0; --pb-inline-border: 1px solid #cde5d3;
  --pb-inline-radius: 14px; --pb-inline-accent: #1e8a4c;
  --pb-inline-title: #0b3d1f; --pb-inline-chip-bg: #fff;
  --pb-inline-chip-border: 1px solid #cde5d3; --pb-inline-shadow: none;
}
</style>

Click "Koude & klamme voeten?" and the floating chat opens bottom-right with that question asked, the category named, and the conversation continues there.