Sign in

Record the originating website and page URL of a live chat conversation

Every Live Chat conversation carries the website and page the visitor was on, per message, so an operator has full context and the AI can use it.

When this happens: BootstrapAsync and subsequent messages/navigation.

Step by step

  1. 1

    Open the conversation and sees the page link next to that message, and the session's current page in the customer profile panel.

    At BootstrapAsync, sets OriginWebsiteUrl from the embedding page's validated origin and LandingPageUrl from the first page seen. Navigates to the pricing page while the widget stays open. The loader posts a page-view event; CurrentPageUrl updates (best-effort). EasyCRM sends a message from the pricing page. EasyCRM stores { pageUrl, pageTitle } on that Message.ExternalContext.

If something goes wrong

Page-view beacon fails

The page-view post fails (network blip). CurrentPageUrl stays at its last known value; messaging is unaffected — this signal is best-effort and never blocks the conversation.

Good to know

  • Page context is recorded per message, not only per session, so operators see the exact page for each message.