Last verified: November 7, 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.
Changelog
November 7, 2026
Save Chat Conversations as Brand Facts. You can now save chat conversations as facts in your brand profile, with the system distinguishing between confirmed facts from your site profile and facts extracted from chat interactions. This gives you a persistent record of brand information discovered through the chat widget.
Apollo Lookup and Demographics for Named Accounts in Threads. You can now enrich named accounts in Threads with optional demographic data and company intelligence from Apollo. When creating or looking up a thread contact, the system can automatically populate additional account details to give your outreach team richer context.
November 5, 2026
Embeddable Offer Spotlight Widget for Brand Websites. You can now embed a Spotlight widget on brand websites to highlight specific offers and drive engagement directly from your site. The widget tracks impressions and interactions, giving you visibility into how visitors respond to your offers in context.
October 29, 2026
Per-Page Brand Chat Widget Rules. You can now set different Brand Chat Widget configurations for each page on your site. The widget loader automatically swaps widget rules on every navigation, so each page can have its own starters, settings, and behavior.
Per-Page Chat Widget Control and Data Collection Override. You can now disable the chat widget on specific pages per brand, or globally turn off data collection in chat conversations using the data-chat=off tag override. This gives you finer control over where chat appears and what data flows through your chat interactions.
October 20, 2026
Chat Settings Summary in Chat View. You can now see a summary of your chat widget settings directly in the chat view, with each setting's current value and a link to edit it. Settings are now accessible as a quiet link rather than requiring navigation away from the chat interface.
Chat Settings Summary in Chat View. You can now see a summary of your chat widget settings directly in the chat view, with each setting's current value and a link to edit it. The settings panel is now accessible as a quiet link rather than a prominent button.
Call Widget Messages and Away Status in Chat Dock. You can now see the call widget's message and away status docked in the chat interface, keeping lead context visible without switching views.
Full-Screen Scheduler Access from Website Embed. You can now open the full-screen scheduler directly from the callback offer in your website embed. The bottom dock now runs the Brand Chat Widget, giving you a unified embedded experience for both chat and scheduling.
October 15, 2026
Separate Slack Channel for Lead Notifications. You can now route Slack lead notifications to a separate channel from your digest. In Slack settings, configure a dedicated leads channel to keep incoming lead alerts distinct from your regular content digest.
Unified Chat and Call Widget Embed. You can now embed a single website tag that powers both chat and calls on your memo pages. Phase 1 consolidates the chat and call widgets into one unified embed snippet, simplifying your implementation while keeping both channels available where readers engage with your content.
October 12, 2026
Customize Chat Widget Dock Layout and Offer Button Visibility. You can now customize the layout of the chat widget dock through settings, choosing whether to display the person profile on the left, chat centered, and callback offer button positioned on the right—or hide the offer button entirely behind a toggle.
Chat Dock and Callback Offers on Same Page. You can now use the Brand Chat Widget and Call/Schedule Callback offers together on the same page. The chat dock now renders directly in your page's HTML, and the ?cm-widgets query parameter works with dashes in subdomain names.
Brand Chat Widget Initialization Without Existing Chat System. You can now use the Brand Chat Widget on sites without an existing chat system — the dock now renders at first paint and initializes automatically for all brands, removing the requirement for prior chat infrastructure.
October 11, 2026
Chat Starters Suggested from Brand Profile. Context Memo now writes your chat starters for you: you can see suggested chat starters in the dashboard that are automatically generated from your brand profile and validated against the product index before they appear.
Chat Preview Feedback with One-Click Guardrail Apply. Context Memo now lets you submit feedback on chat preview responses and apply suggested guardrails with a single click from the feedback interface.
Chat Guardrails, Voice, and Daily Budget Controls. Context Memo customers can now set guardrails, enable voice, and configure a daily budget limit for their Chat feature in the Chat settings panel.
Chat Page for Brand Conversations and Questions. Context Memo now gives you a dedicated Chat page under your brand's Content section, where you can view and manage conversations, unanswered questions, and offers, with chat settings you configure yourself.
October 10, 2026
Brand Chat Embed for Customer Sites. Context Memo customers can now embed a chat widget on their own websites and configure it through a Settings snippet in the dashboard.
Call Button in Chat Interface. Context Memo now puts a labeled call button beside the chat bar, so customers can initiate a callback directly from the chat interface and open a callback panel alongside their conversation.
Conversation Threads and Per-Message Views in Brand Chat. Context Memo now gives you dedicated pages for individual messages and lets you organize chat conversations into threads inside the brand chat interface.
Persistent Offer Dismissals and Smoother Mid-Answer Refresh. Context Memo customers can now dismiss offers in chat and have those dismissals persist across page refreshes, and see cleaner mid-answer updates without empty rows appearing.
Chat Follow-Up Email When No Answer Is Found. Context Memo can now send a customer an email follow-up with a time promise when your brand chat cannot answer their question, so an unanswered inquiry doesn't disappear the moment the tab closes.
October 9, 2026
Brand Chat. Context Memo has shipped Brand Chat, where you can chat with an AI assistant about your brand in a new conversational interface instead of navigating structured reports to find a single answer.
Toggle Chat Widget Per Page. Context Memo now lets you enable or disable the chat widget on individual pages through a per-page toggle in Page settings and the Page Builder.
