Skip to main content

Cross-Session Context

When a session is verified, the AI agent's prompt is enriched with everything we know about that visitor across every prior session they've had on your site. This is what makes returning conversations feel personal — the AI doesn't ask the same questions twice and can pick up where the visitor left off.

What sections are available​

Each section is enabled or disabled by the super admin via the global Identity Graph defaults (or a per-company override). Leaving all sections unchecked means "include everything". See Admin Controls.

Identity​

Name, email, phone, self-reported company, industry, location (from IP geolocation), CRM contact IDs.

Company Insights​

Domain, employee-count band, annual-revenue band, industry tags. Sourced from third-party enrichment when the visitor's email or IP can be matched.

Engagement​

Lead score (total + level), total session count, first-seen and last-active timestamps, total pages viewed across sessions.

Current Session​

Current page URL and title, traffic source (organic / paid / direct / social / referral / etc.), UTM parameters, referrer domain.

Recent Pages​

Last N (default 5) unique pages the visitor has viewed across all sessions on your site, newest first, deduped by URL.

Past Conversations​

Last N (default 5) chat or call summaries on your site, newest first. Each item shows when it happened, who handled it (AI or human agent), and a one-line gist.

Behavioral Signals​

Boolean flags: visited a high-intent page (pricing, etc.), products searched, has booked a meeting, has shared email / phone, returning visitor, user-initiated call.

CRM State​

Pulled from connected HubSpot or GoHighLevel accounts. Includes lifecycle stage, lead status, active deals (HubSpot) or opportunities & pipeline stage (GoHighLevel), contact tags, and the most recent rep notes. Cached and refreshed in the background every few hours.

Bookings​

Every meeting linked to this visitor — across Google Calendar, Calendly, GHL calendars, and your widget's manual booking flow. Deduped by (type, date, time, email) so the same meeting captured via two paths shows up once.

Form Responses​

Every form the visitor has submitted on your site. Deduplicated so a visitor who fills out the same contact form twice with the same values doesn't bloat the prompt.

Extracted Facts​

Short AI-distilled takeaways from past chats and calls. Examples:

  • "Interested in the Pro plan."
  • "Budget under $5,000."
  • "Asked about migration timeline."
  • "Mentioned competitor X."

These are deduped by text hash, capped at 30 per profile (highest-importance + most-recent kept), and tagged with the source (chat or call).

Tunable limits​

Configured by the super admin alongside the section list:

  • Max Recent Pages — default 5, max 20.
  • Max Past Conversations — default 5, max 20.
  • Max Extracted Facts — default 15, max 50.

Higher values give the AI more context but make the prompt longer (and a bit slower / more expensive). The defaults are tuned for typical B2B and B2C conversations.

Custom intro​

The super admin can prepend a short paragraph to every AI prompt via the Custom Instructions field on the global Identity Graph config (or a per-company override). Use it to nudge the AI's tone or focus, e.g.:

Use the visitor's name naturally. Reference their past objections to build trust. Don't ask questions we already have answers to.

What the AI sees for unverified ("claimed") sessions​

Only the Identity section (name, email, phone) and Current Session sections are shown — plus anything that happened in the current session (own page views, own bookings made this session, own form submissions). No past conversations, CRM state, extracted facts, or cross-session bookings are exposed.

This is by design: see Identity Verification for the rationale.