Last verified: October 8, 2026
What You Can Now Do
Context Memo now lets you edit the greeting text, photo, name, and callback question for your website widget on a per-brand basis in Settings. Until this deploy, the widget shipped with default copy and no identity, so the first thing a visitor saw on your memo pages looked the same as it did for everyone else. Now the widget carries your brand's voice and asks the question you actually want answered. The task this changes: instead of accepting the default prompt and sorting through generic callback requests, you decide up front what a visitor is asked, and you set that per brand rather than once across your whole account.
Where It Is in Context Memo
The controls live in Settings, in the callback widget configuration for the selected brand. The screen now shows four editable fields (greeting text, display name, callback question) plus a photo upload. If you manage more than one brand in Context Memo, switch brands first, then open Settings. Each brand holds its own widget configuration.
How to Use It
- Open Settings and confirm the brand selector is set to the brand whose widget you want to change. The configuration you see belongs to that brand only.
- Edit the greeting text. This is the opening line a visitor reads when the widget appears. Keep it short enough to read in one glance; long greetings get collapsed by the widget container.
- Upload a photo. Use a person your buyers would plausibly talk to, such as a named rep or founder, rather than a logo mark. The image renders at small size, so crop tight on the face before uploading.
- Set the display name that appears next to the photo. A real first name and role reads as a person; a department name reads as a form.
- Write the callback question. This replaces the default prompt and determines what every visitor is asked. Teams with a single product usually ask about timing or use case. Teams with several lines ask which product the visitor is evaluating, so the answer routes the follow-up.
- Save, then load one of your published memo pages for that brand and trigger the widget. What you see in the browser is what visitors see. Repeat for each additional brand.
Why We Built It
Customers told us the widget worked but felt borrowed. It sat on their own domain, under their own memo content, and still introduced itself like generic software. The question it asked was fixed, which meant a team selling into two different buyer segments got one undifferentiated answer field and had to guess at context during follow-up. Teams can now make the callback widget feel native to their brand instead of generic, and ask the questions that matter most to their business. The cost before was twofold: lower response rates on a widget that visibly did not belong to the page, and callback records that arrived without the one piece of qualifying information the team needed.
What It Does Not Do Yet
Configuration is per brand, and there is no bulk apply or copy-from-brand action. If you manage several brands with near-identical messaging, you will set each one by hand. The fields available on this screen are greeting, photo, display name, and callback question; other widget behavior is not editable here. The callback question is a single question, so if you need multiple qualifying inputs, the follow-up conversation still carries that load. We would rather ship the four controls customers asked for first and keep the surface honest about what it covers.
One practical note on measurement. The widget sits on memo pages published to your own domain, which is where your AI bot crawl data and citation traffic already land. Changing the greeting and question changes what you learn from the humans who arrive through those AI sessions, not what the models read. Memo content still drives how models describe you. The widget decides what happens after a buyer gets there.