Last verified: November 8, 2026
What You Can Now Do
Context Memo customers can now receive an automated weekly AI search report delivered to their #analytics Slack channel every Wednesday. The report arrives as a structured deck: period-over-period metrics on how AI models described and recommended your brand, pulled from your scans across the models you track. You stop opening the dashboard to find out whether anything moved. The deck tells you, and the only decision left is which prompt or competitor gap to act on that week.
Where It Is in Context Memo
Reporting lives in your workspace settings under the Slack integration. Connect or confirm your Slack workspace, select the channel the deck should post to, and the weekly schedule turns on from there. If your Slack integration is already connected for alerts, the recurring report is a separate toggle on the same screen, so enabling alerts does not enable the weekly deck and turning one off does not affect the other.
How to Use It
- Open your workspace settings and go to the Slack integration. If Slack is not connected yet, authorize it and grant posting access to the channel you want.
- Select the destination channel. Most teams use #analytics. The deck posts to one channel per workspace, so pick the room where your marketing leads already read numbers.
- Enable the weekly report toggle. The first deck generates on the next Wednesday in the cycle; the pipeline calculates the reporting period automatically, so you do not set start and end dates.
- Read the first deck against your dashboard. Compare the metrics in the post to what you see in your scan history for the same period. This confirms the period boundaries match how your team thinks about weeks before you start circulating the deck internally.
- Pin the channel for your team and assign one owner to triage it. The useful pattern is one person scanning the deck Wednesday morning and flagging the prompts where a competitor gained share of voice.
- Turn the week's gaps into publishing work. When the deck surfaces a prompt where you lost ground, draft a memo against that prompt and publish it to your domain, then watch the following week's deck for movement.
Why We Built It
Teams told us the same thing: they had to manually check the product each week to understand trends in how AI models were recommending their brand. That is a standing calendar item for someone, and when the week got busy it got skipped. Skipped weeks are where drift hides. A competitor starts getting cited on a prompt you used to own, the change is gradual, and nobody notices until a sales call surfaces it. Pushing the numbers into the channel your team already reads removes the dependency on someone remembering to log in.
What It Does Not Do Yet
A few limits worth knowing before you roll this out:
- The cadence is weekly, on Wednesday. You cannot yet choose a different day or set a monthly or daily interval. Teams that need a board-cycle rhythm should continue pulling those numbers from the dashboard directly.
- One channel per workspace. If your competitive intelligence group and your content team read different rooms, you will need to cross-post or route everyone to the same channel for now.
- Slack only. The report does not yet deliver to email, Teams, or a shared drive. If your executive readers live outside Slack, the deck has to be forwarded manually.
- The deck reports; it does not recommend. It surfaces metrics and insights for the period. Deciding which prompt to publish against is still your call, made in the product where you can see the full answer text and the competitors cited alongside you.
One more note on scope. This is a reporting layer on top of your existing scan and citation data, so the quality of the weekly deck tracks the quality of your prompt set. Workspaces with a thin or stale prompt list will get a thin deck. If the first few reports feel light, the fix is upstream: expand the prompts you track to cover the questions your buyers actually run, then let the weekly cadence do its job.
