Docs

Page Awareness

Page Awareness lets your AI agent know which page the visitor is currently on. This enables more relevant, context-aware answers and provides richer context when escalating to human agents.

Page Awareness works with the web widget only. Telegram and other messaging channels do not have a concept of "current page".

Overview#

When enabled, the widget automatically collects the visitor's current page URL, title, and description. This context is injected into the AI's system prompt, allowing it to tailor answers based on where the user is browsing.

Page Context

Agent sees the current page URL, title, and meta description

Escalation Context

Human agents receive the visitor's current page info on escalation

How It Works#

The widget captures page context automatically — no code changes required on your site. Here is what gets collected with each message:

DataSourceExample
Page URLwindow.location.hrefhttps://example.com/pricing
Page Titledocument.titlePricing — Acme Corp
Pathwindow.location.pathname/pricing
Descriptionmeta[name=description]Compare our plans
Referrerdocument.referrerhttps://google.com

Example: What the agent sees#

When a visitor on /pricing asks "How much does it cost?", the agent's system prompt includes:

Injected into system prompttext
PAGE CONTEXT (where the user is right now):
- Page: Pricing — Acme Corp
- Path: /pricing
- Description: Compare our plans and pricing

Use this page context to provide more relevant, page-specific answers.

Setup#

Page Awareness is an opt-in feature. To enable it:

  1. Go to your Agent Settings page in the dashboard
  2. Scroll down and expand the Page Awareness section
  3. Toggle on Enable page awareness
  4. Optionally enable Include context in escalations
  5. Save your settings
No changes to your widget embed code are needed. The widget automatically sends page context once the feature is enabled on the agent.

Escalation Context#

When a conversation is escalated to a human agent, the escalation notification email (and Zendesk ticket, if enabled) automatically includes the visitor's current page context. The human agent sees exactly where the visitor was browsing without having to ask.

Full example of what the escalation email contains:

Escalation email body
A conversation has been escalated to a human agent.

Conversation ID: 9f3a1c2d-...
Last user message: I need help with the Enterprise plan — our team
  needs SSO and I can't find pricing info anywhere

--- Page Context ---
URL: https://example.com/pricing
Page: Pricing — Acme Corp

Please respond to the customer as soon as possible.

-- RespondoAI Escalation Alert
The Include context in escalations toggle controls this. It is on by default when Page Awareness is enabled.

Troubleshooting#

If Page Awareness does not seem to work, check the following:

Agent gives generic answers, ignoring the current page

Make sure Enable page awareness is toggled on in agent settings and that settings were saved. The feature is disabled by default.

Escalation email has no page context section

Check that Include context in escalations is enabled in agent settings. Also confirm that Escalation Alerts are configured (escalation email address set).

Page title shows the wrong value

The widget reads document.title at the moment the user sends a message. If your site updates the title after the initial render (e.g. async), the widget captures whatever is set at send time.