Last verified: October 10, 2026
What You Can Now Do
Context Memo now lets you embed a chat widget on your branded memo pages and capture visitor conversations as leads, with full transcripts delivered to your inbox. Until now, your memo pages did one job: they answered the question for the AI model and the human who followed the citation. The traffic arrived, read, and left. You saw the crawl, not the conversation. With the widget live, a visitor who lands on a memo from a ChatGPT or Perplexity citation can ask a follow-up question on the page, and that exchange becomes a named lead in your pipeline instead of an anonymous session. The task this changes: you no longer have to treat memo traffic as top-of-funnel only. A memo page is now a conversion surface, which means the prompts you win are directly attributable to conversations you can act on.
Where It Is in Context Memo
Chat settings live in your memo publishing and domain configuration area, alongside the controls for custom domain publishing and schema output. From that screen you turn the widget on or off per property, set where lead notifications route, and enable transcript delivery. Captured conversations and their transcripts appear with your lead records, so chat-sourced leads sit next to the rest of your AI traffic attribution data rather than in a separate silo.
How to Use It
- Open chat settings in your publishing configuration and enable the widget for the domain where your memos are published. The widget renders on your branded pages, on your domain, not on a third-party host.
- Configure the widget's greeting and behavior so the opening prompt matches the memo's subject. A visitor who arrived from a comparison prompt should see a different opener than one who arrived from a pricing or integration question.
- Set lead routing. Choose the destination for new chat-sourced leads and the address that receives notifications. If you route marketing leads through HubSpot today, point chat capture at the same owner so nothing requires manual reassignment.
- Turn on transcript delivery. Each completed conversation is emailed as a full transcript to the addresses you specify. Sales reads the actual language the buyer used, not a summarized field.
- Publish or republish a memo and load the live page to confirm the widget renders and the test conversation arrives as a lead with its transcript attached.
- Review transcripts weekly against your scan data. The questions visitors type are the same questions buyers are putting to the models. When a transcript surfaces a question your memos don't answer, that's your next memo.
Why We Built It
Brands told us the same thing: we can see the crawls and we can see the citations, but we can't talk to the person who showed up. Building custom chat infrastructure on a published memo page meant a developer ticket, a vendor contract, and a consent and routing review, which is enough friction that most teams never did it. The cost was a measurable gap between AI-sourced traffic and AI-sourced pipeline. Marketing could prove visibility. It could not prove conversation. That gap is where AI visibility budgets get questioned, so we closed it: real-time engagement on the page, automatic lead capture, transcripts in the inbox, no engineering work.
What It Does Not Do Yet
The widget captures and routes conversations and delivers transcripts. It is not a full customer support desk. There is no agent console with queues, assignment rules, SLA timers, or canned-response libraries, and we are not trying to replace the help-desk or CRM tooling you already run. Those systems have deeper functionality for case management, and the right pattern is to use chat capture as the entry point and let your existing system own the thread after handoff.
A few other current limits worth setting expectations on:
- Routing is configured per property, not per visitor attribute. If you want different owners for different personas, you'll need separate configuration per domain or property rather than conditional rules inside one widget.
- Transcript delivery is email-based. Transcripts arrive as email to the addresses you set. If your team works transcripts inside a CRM record, treat the emailed transcript as the source and attach it to the record on your side.
- The widget assumes you already have published memo pages. Chat capture only works where there's traffic to capture. If you're standing up your first memos this month, get pages published and indexed, confirm bot crawls are logging, then enable chat once real sessions are landing.
Transcripts are also one of the more direct signals we've seen for memo gaps. Scans tell you how the models answer. Crawl logs tell you what the models read. Transcripts tell you what the human asked after the model sent them to you. Read all three together.