Last verified: October 11, 2026
What You Can Now Do
Context Memo customers can now embed a chat widget on their own websites and configure it through a Settings snippet in the dashboard. This is Phase 5 of brand chat, and it moves the conversation off our domain and onto yours. Your site visitors ask questions in a chat interface you control, grounded in the memo content you've already published. The decision it changes: you no longer have to scope a chat build, pick a vendor, or route engineering time to stand up conversational search on your own pages. You paste a snippet and the interface is live.
Where It Is in Context Memo
Brand chat configuration lives on the Settings page in your dashboard. That screen now holds your embed snippet, the chat configuration options, and a preview link so you can open the widget and test conversations before anything touches production. The preview runs against the same chat engine that will serve your visitors, so what you see in preview is what your site will render.
How to Use It
- Open Settings in your Context Memo dashboard and locate the brand chat section. You'll see your embed snippet and the configuration options attached to your brand.
- Click the preview link. The widget opens in a test context, and you can ask the questions your buyers actually ask (pricing structure, integrations, how you compare on a specific capability) and read the answers before any visitor does.
- Adjust the chat configuration in Settings if the preview surfaces answers that are thin or off-position. Note what's missing. Thin answers usually mean thin source material, not a broken widget.
- Publish or update the memos that cover the gaps you found. The chat engine draws on your published memo content, so the fastest way to improve an answer is to strengthen the source behind it.
- Copy the embed snippet and add it to your site template. Place it wherever your buyers are already evaluating: pricing, product, comparison pages. Your engineering lift is a script tag, not a project.
- Re-run the preview after your next memo publish to confirm the new content is reflected in responses.
Why We Built It
Customers kept arriving at the same conclusion: their buyers wanted to ask questions, not read pages, and building chat infrastructure to serve that was a quarter of engineering work nobody had budgeted. So the option was a generic chatbot wired to a help center, or nothing. Most chose nothing. That meant the positioning work already done in memos, the third-person neutral framing, the external citations, the schema markup, sat on static pages while visitors with a specific question bounced instead of asking it. The content was already structured for machine consumption. The interface was the missing piece.
There's a second reason, and it's the one we care about more. The memos you publish for AI models and the answers your own site gives visitors should come from the same source of truth. When they diverge, you get the problem we built this company to fix: two versions of your positioning in the wild, one of which you aren't watching. Brand chat closes that gap by running your visitor-facing answers off the same published content that AI models crawl.
What It Does Not Do Yet
A few honest limits worth knowing before you deploy:
- Placement is on you. The snippet is yours to install. We don't inject the widget, detect your CMS, or offer per-page targeting rules from Settings yet. If you want the widget on some pages and not others, handle that in your template logic.
- Answer quality tracks your published content. Brand chat is not a general-purpose assistant. If a buyer asks about a capability you haven't documented in a memo, the answer will be weaker than one covering ground you've already published. Treat preview gaps as a content backlog, not a bug report.
- Chat conversations are separate from scan and citation data. This release ships the embed, the Settings page, and the chat engine. It does not yet join what visitors ask in chat with what you see in multi-model scans. Reading both pictures is still two places in the dashboard.
- This is not a replacement for your CMS or your support stack. Keep them. Brand chat sits alongside what you already run and answers brand and product questions from memo content. Ticketing, account lookups, and authenticated flows are outside what it does.
If you're on a trial and haven't published memos yet, install the snippet last. Get two or three memos live on your domain first, then preview the chat. The widget is only as good as the source of truth behind it, and that's the part worth building first.