Last verified: September 20, 2026
What You Can Now Do
Context Memo now inserts a curated Unsplash photo after the first section of each daily memo, so your briefing carries visual interest and context instead of arriving as an unbroken block of text. The practical change is in how you read it. The opening section still carries the headline signal: which prompts moved, which models shifted, where a competitor gained ground. The image now marks the end of that summary and the start of the detail beneath it, which gives you a clean stopping point if you only have a minute. It also changes one small decision: forwarding the memo to a stakeholder who does not live in AI visibility data every day is now a lower-friction ask.
Where It Is in Context Memo
There is nothing new to switch on. The photo appears inside the daily memo itself, in the body, directly below the opening section. If you receive daily memos by email or read them in the app, you will see it on the next one generated. The change also touches widget configuration, so memo output embedded in a dashboard view renders the image as part of the standard layout rather than dropping it.
How to Use It
- Open your next daily memo. Scroll past the opening section and confirm the photo renders in your email client or browser.
- Read the opening section as your executive summary, then treat the image as the boundary. Everything below it is the supporting detail: model-by-model movement, citation changes, competitor share of voice.
- Forward or paste the memo to a stakeholder who needs the top-line read. Check that the image carries through in whatever surface you use, because some email clients and internal wikis strip remote images by default.
- If you embed daily memo output in a dashboard, review your widget configuration once so the container height accounts for the image. Memo widgets should render the photo without clipping the sections that follow it.
- Tell us if an image lands in a place that reads as tonally wrong for that day's briefing. Image selection is curated, and reports of mismatches are what improve the selection logic.
Why We Built It
Daily memos carried the right signal in the wrong shape. Customers told us the briefings were text-heavy, which meant they got skimmed at the top and abandoned before the sections that mattered most, or forwarded to a colleague who never opened them. A memo that reports a competitor overtaking you in Perplexity answers is worthless if nobody reads past line four. Breaking up dense text with relevant imagery makes the daily memo function the way a briefing should: a document you actually finish.
What It Does Not Do Yet
A few limits worth knowing before you build a process around this.
- Image selection is automatic. There is no per-memo override, no manual upload, and no way to pin a specific photo to a recurring section.
- Placement is fixed. One image, positioned after the opening section. You cannot add images to later sections or move the existing one.
- Photos are decorative and contextual, not data. They do not visualize your citation trend, share of voice, or crawl volume. For that, the charts in the memo body and your dashboard remain the source.
- This applies to daily memos. Citation-grade memos you publish to your own domain are unchanged, and deliberately so. That format stays structured text with schema markup, because that is what AI models parse and cite.
- Email clients that block remote images will show the memo without the photo. The text layout degrades cleanly, so nothing else breaks.
If your team relies on the daily memo as the standing input to a morning standup or a weekly pipeline review, the useful test is simple: watch whether the people you forward it to start replying about the sections below the fold. That is the behavior this change is meant to produce, and it is observable in your own thread history within a week.