Most of our users assume the AI assistant knows which product page they’re viewing. As a result, they frequently ask about the product details shown on-screen, but the assistant can’t provide that information unless the user manually supplies the product ID. To improve user experience, we need a way to pass the current page’s URL (or product ID) to Apollo AI so that it can automatically fetch relevant product data via our API.
Problem Statement
User Frustration
Users expect the AI assistant to “see” the page they’re on and answer product-specific questions without extra steps.
They must explicitly tell the assistant, “I’m looking at Product #12345,” before receiving a relevant response.
Missed Opportunity for Seamless Interaction
Our backend API already exposes all product metadata—name, price, stock level, images, etc.
Apollo currently has no mechanism to detect or retrieve the page context (e.g., the URL or product ID).
Without that context, every conversation about a product becomes a multi-step interaction.
Proposed Feature
Expose Page Context to Apollo
Allow Tawk.to’s widget or embedded script to send the current page URL (or unique product identifier) to the Apollo engine whenever a user initiates or continues a chat.
The assistant can then include this URL or ID when calling our product API, eliminating the need for users to remember or repeat a product ID.
We’d like to assure you that the issue you reported has already been identified and is included in our product roadmap. It has been thoroughly investigated, and while we recognize its importance, the complexity involved—particularly due to its cross-domain nature and dependency on conversation-level data—means that a short-term solution is not feasible.
We currently have several related initiatives underway, and we’re working to ensure everything is aligned for an effective long-term resolution.
We truly appreciate your patience and understanding as we navigate these complexities. Please bear with us a little longer—we’ll keep you updated on our progress.
Just a quick update. This has been on our radar for some time, and while we can’t guarantee delivery in the immediate term, we’re actively aiming to have it addressed either later this quarter or in the third quarter of 2025.
Our team has already conducted an initial investigation and identified a few potential solutions. However, as this involves cross-domain functionality—specifically overlapping with the conversation layer to access necessary data—it adds a layer of complexity. Combined with other ongoing initiatives, this has slightly impacted the timeline.
We truly appreciate your patience and understanding, and we’re committed to keeping you updated as we make progress.
