Conversation Threads and Per-Message Views in Brand Chat

Last verified: October 10, 2026

What You Can Now Do

Context Memo now gives you dedicated pages for individual messages and lets you organize chat conversations into threads inside the brand chat interface. A single answer from a long chat session is no longer buried in the scroll position where you happened to find it. It has its own page and its own link. That changes one task in particular: when a model response describes your brand incorrectly, or names a competitor you didn't expect, you can isolate that message, send the link to whoever needs to act on it, and keep the surrounding conversation intact as context. Chat starters are now served through their own API routes, so the prompts you open a session with load as a defined set rather than as free text you retype.

Where It Is in Context Memo

Everything in this deploy lives in the brand chat interface. Open brand chat, and the conversation view now renders threads alongside the main message flow, with each message exposing its own page. The underlying database migrations add message-level pages and thread organization, so conversations you already have in brand chat pick up the new structure rather than starting from empty.

How to Use It

1. Open brand chat and pick a chat starter to begin a session. The starter loads from the new chat starter routes, so the prompt is consistent every time you run it.
2. Run your question and read the response in the conversation view. Messages render in the updated chat components, each one addressable on its own.
3. Open the message page for any response worth keeping. You get a dedicated view of that single message, separated from the rest of the session, with a link you can copy.
4. Group related messages into a thread when one question produces follow-ups. The thread keeps the sequence together so the answer and its qualifiers stay attached.
5. Send the message page link to the person who owns the fix. A content owner reviewing a misrepresentation sees the exact message, not a screenshot and not a page they have to re-read from the top.
6. Return to the conversation to continue the session. The thread you created persists, so the next person opening that chat sees the same organization you left behind.

Why We Built It

Customers told us the same thing in different words: in a longer conversation, they couldn't follow or reference a specific message without losing context or scrolling back through the entire chat history. The cost was real work lost. A finding about how a model described a product would surface in a session, then get flattened into a pasted paragraph with no source, no prompt, and no way for a teammate to verify it. Brand chat was useful for asking questions and weak at turning the answers into something a team could act on.

What It Does Not Do Yet

This deploy is scoped to brand chat. Threads and message pages do not appear in other areas of the product, so a message you thread here is not yet pulled into scan views, memo drafts, or Slack alerts. Distribution is manual: copy the message page link and send it. Thread organization is also per conversation, which means there is no cross-conversation grouping if you want to collect related messages from several sessions into one place. For that, keep the links in whatever your team already uses to track work. Context Memo does not replace your CRM or CMS, and this release does not change that; brand chat sits alongside them and the HubSpot integration remains the path for pushing anything into your existing stack.