Share page location with Agent Stacks
By default, an Agent Stack answering in Web Chat has no idea which page of your site the visitor is on. If your site has multiple products or modules, this often means the stack opens by asking the visitor which one they’re using before it can help.
The Share page location with Agent Stacks toggle fixes this by forwarding the visitor’s current page URL into the conversation, so the stack can answer page-specific questions right away.
What it does
When enabled, the widget sends the visitor’s current page location along with each message. Atender sanitizes this into a short context note and includes it in what the Agent Stack sees, so it knows where the visitor is chatting from without you having to build that into your prompts.
This is purely additive: it gives the stack more context to work with. It doesn’t change routing, doesn’t change which stack answers, and doesn’t appear as a visible message bubble to the visitor.
Where to enable it
- Go to Settings → Web Chat.
- Open the widget you want to update.
- In the widget’s AI settings, find Share page location with Agent Stacks.
- Turn the toggle on.
- Save the widget.
The toggle is off by default. Enabling it applies only to the widget you’re editing — if you run multiple widgets, turn it on separately for each one that should share page location.
What gets shared
Only the page’s origin and path are shared — for example https://example.com/billing/invoices. Any query string or hash fragment (?token=..., #section) is dropped before it reaches the Agent Stack. This keeps things like session tokens, search terms, or one-time links out of the conversation.
If your site passes an optional page or module label alongside the URL, that label is included too, giving the stack an even clearer signal about which part of the product the visitor is in.
Because the page URL comes from the visitor’s browser, it’s treated as untrusted input: it’s capped in length and normalized to a single line before it’s used.
Resulting behavior
With the toggle on, a visitor asking “how do I export this?” while on your billing page no longer gets “which product or module are you asking about?” — the Agent Stack already knows they’re on the billing page and can answer directly.
With the toggle off, nothing changes: the stack behaves exactly as it did before this setting existed.
When to turn this on
- Your site has multiple products, modules, or sections and visitors regularly ask questions that only make sense in that context.
- Your Agent Stack’s instructions currently tell it to ask “which page/product are you on?” as a first step — with page location shared, that question is often unnecessary.
When you might leave it off
- Your site is a single product with no meaningful page-to-page distinction — there’s no context to gain.
- You have privacy or compliance reasons for not wanting any page URL, even sanitized to origin+path, included in conversation content.