Last verified: October 9, 2026
What You Can Now Do
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. Before this deploy, the widget was a single setting applied across every page you published, so the Copilot either appeared everywhere or nowhere. Now each page carries its own value, and the embed logic honors it. The practical change: you can run the widget on the pages where you want an assisted path (memos, solution pages, comparison content) and keep it off the pages where it doesn't belong, such as legal copy, pages under review, or a campaign landing page that needs one conversion path and no distractions.
Where It Is in Context Memo
The toggle appears in two places for the same page: Page settings, and the Page Builder while you're editing. Both read and write the same page-level value, so the state you see in one surface matches the other. Page serving now checks that value before rendering the widget embed, which means the control applies to the live page, not just the editor preview.
How to Use It
- Open the page you want to change and go to Page settings. The chat widget control is listed with the rest of that page's configuration.
- Set the toggle on or off for this page, then save. The setting applies to this page only and leaves every other page untouched.
- If you're already editing, use the same toggle in the Page Builder instead of switching screens. It writes the same value.
- Load the published page and check for the widget. Serving logic reads the page-level setting, so the embed either loads or is omitted entirely rather than loading and hiding.
- Work through the remaining pages that need the opposite behavior from your default, and confirm each one on the live URL.
Why We Built It
Customers told us they wanted to control which pages show the chat widget instead of having to use it everywhere or nowhere. That forced a bad trade. Teams who needed the widget off a single page, usually for a legal or compliance reason or because a landing page had to stay single-purpose, had to disable it across the whole site and lose it on the pages where it was doing real work. Others kept it on and accepted it in places where it shouldn't have appeared, which is a harder conversation to have with legal than with marketing.
What It Does Not Do Yet
The control is per page. There is no bulk apply and no rule-based targeting by URL pattern, template, or page type, so a large section of pages means setting each one. If you're standing up a new set of pages, decide the widget state as part of your page setup rather than retrofitting it later. The toggle also governs presence only: it turns the widget on or off for a page and does not change widget behavior, prompts, or appearance on the pages where it stays on.