Page awareness: answer about the product on screen

Page awareness lets the website assistant know which page a visitor is looking at when they chat. Visitors can ask “how much is this?” or “does this ship free?” without naming the product — the page path, title, and summary fill in the context.

What the assistant sees

• Page path (URL path only — domain is not required)
• Document title (the browser tab title)
• Page summary (meta description / Open Graph description)
• Allowlisted product query keys when present (sku, id, product_id, variant, and similar)

This context is sent with each widget message, used for that turn only, and is not stored as a normal chat message. Form fields, passwords, and marketing tokens in the URL are not used. Path matching ignores the full query string so tokens stay out; product identity keys are re-read separately.

Generic mode vs path instructions

1. 1
   Generic (toggle on, no rules)

   The assistant gets an untrusted “visitor’s current page” note with path, title, and summary. Treat it like a helpful hint. Good page titles matter most here.

2. 2
   Path instructions (optional rules)

   You add path patterns (starts with / matches exactly / matches a glob). On a match, Concierge also injects your instruction as trusted operator guidance — for example “visitor is on cart; help them finish checkout.”

Unusual product URLs

• Static PDP: /products/sofa-linho — path and title carry the product
• SKU in path: /p/AUR-SOFA-220 or /c/sala/item/AUR-SOFA-220 — the path includes the SKU
• SKU in query: /produto.html?sku=AUR-SOFA-220 — path is shared; set a real title/summary after load, and the allowlisted sku still reaches the assistant
• Numeric id: /item/1003 — same idea as path or query id

If the HTML title stays generic (“Product | Store”) and the URL has no allowlisted identity, the assistant cannot invent which product is on screen. Fix the site meta, not only Concierge settings.

Pair with Knowledge

Page awareness is a hint for this turn. Durable facts — price lists, stock, shipping, returns — belong in Knowledge. When a visitor follows up (“and in blue?”), the agent should ground on approved chunks, not only the page summary.

• Hero products have Knowledge chunks with SKU, price, and shipping notes
• PDP templates set title and meta description with product name (and SKU when possible)
• Widget origin allow-list includes every host where the embed runs

Where to configure

1. Open Knowledge → Page awareness (same editor also lives under Settings).
2. Enable page awareness.
3. Optionally add path instructions for cart, checkout, returns, or pricing.
4. Save, then open a real product page with the widget and ask a vague question (“quanto custa esse?”).

How to test

1. 1
   Vague question on a PDP

   Without naming the product, ask about price or frete. The reply should name the on-screen item.

2. 2
   Change page, same visitor

   Open another product (or a SKU query URL) and ask again. Context should follow the new page.

3. 3
   Cart or returns with a rule

   If you added path instructions, confirm tone shifts (closing help vs policy), not only product facts.

4. 4
   Toggle off (control)

   Disable page awareness: the same vague question should no longer ground on the on-screen product.