Answers based on the page your visitor is reading
Written by the Allinaa team · Updated
"How much is this one?" makes no sense to a chatbot that doesn't know which page the visitor is looking at. The Allinaa assistant does know. It reads the public page the visitor has open, so short questions get answers about that listing, product or service.
"How much is this one?" needs to know which page
Visitors don't write complete questions. On a listing page they type "still available?", on a product page "does it come in black?", and on a job post "is this remote?". A chat that ignores the page has to ask "which one do you mean?" every time. That is one extra step, and many visitors don't bother. A page-aware assistant answers straight away and asks only when the page itself is ambiguous.
How page awareness works
- When the visitor chats, the widget sends the page's address, title, description, a short excerpt of its visible text (up to 2,500 characters) and the links on it.
- Only public pages of your own website are accepted. A page on another site is ignored.
- The assistant treats the page as information about what the visitor is looking at, never as instructions. The assistant is instructed to treat page text as information, not instructions; like any AI it can still be misled, so binding actions stay with people.
- Your approved knowledge still governs prices, policies and availability. The page tells the assistant what the visitor means by "this one".
Nothing extra is needed on your website: the same embed code does it.
Privacy: checkout and account pages and query strings are ignored
Some page addresses carry personal data, and some pages should never be read at all. The page context has three filters, and one rule only you can apply: where the widget is installed.
- Query strings and fragments are removed. Anything after "?" or "#" can contain an email address, a search term or an order number, so it is dropped before the assistant sees the address.
- Pages with a private path segment are skipped. The widget sends no page text from an address whose path contains a segment named account, login, sign-in, register, checkout, cart, order, orders, payment, billing, invoice, profile, admin, dashboard, password, portal, settings or subscription (and a few similar ones). It reads the visible text of any other page it is loaded on, including logged-in pages at other addresses, such as /patient-portal/ or /members/. Don't install the widget on any page that shows customer data.
- Invented links are removed. The assistant may share only links that appear in your approved information or on the current page. A link it makes up is taken out of the reply.
More about what to tell visitors is in Chatbot privacy basics.
Conversations that continue across pages and return visits
A visitor who asks about one listing, opens two more and then asks "which of these has a garage?" keeps one conversation. It follows them from page to page, survives a page reload, and is restored if they come back within 30 days. If they press "New conversation", the old chat is closed and the window is cleared. The old chat is not erased from your records.
Best fits: listings, product pages, service pages, job posts
- Property listings: "Is there parking?" or "When is the open house?" See AI chatbot for real estate agents.
- Vehicle inventory: "Does this one have a tow package?" See AI chatbot for car dealerships.
- Product pages: sizes, materials and what's in the box, as written on the page.
- Service pages: "Does this include disposal of the old unit?"
- Job posts: shift times and requirements, then the application link from the page.
- Ad landing pages: one offer, one question. See Chatbot for landing pages.
It helps less on a one-page website, where every question already has the same context.
Illustrative example
Illustrative example, not a real customer conversation.
Page: a used-truck listing that says "Towing package, bed liner, one owner"
Visitor: does this one have a tow hitch
Assistant: Yes, this listing includes the towing package. I can't confirm it's still on the lot right now, but I can send your question to the sales team so they can check and get back to you.
Visitor: ok and the white one I looked at before?
Assistant: Do you mean the white truck you viewed earlier in this chat? Let me know which one, or paste its link, and I'll check what its page says.
The assistant answers from the page it can see and doesn't claim stock it can't confirm, because availability must come from your approved information.
Questions and answers
Does the assistant track visitors across other websites?
No. It only uses public pages of your own website, and only the page the visitor has open while chatting.
Do I need to tag my pages or change my website?
No. The standard embed code sends the page context. Clear page titles and descriptions help, but nothing special is required.
Can it read pages behind a login?
It depends on the address. The widget sends no page text from addresses whose path contains a segment such as account, login, portal, checkout, cart, order, profile or dashboard. On a logged-in page at any other address, such as /members/ or /patient-portal/, it reads the visible text like on any other page. So load the widget only on pages without customer data. Query strings are removed from every address.
What if the page and my knowledge disagree?
Fix whichever is out of date. Prices, policies and availability should match on both, because the assistant may quote either one.