Last verified: September 16, 2026
What You Can Now Do
Context Memo customers can now view and browse ideas in the Hopper section of their brand dashboard. Hopper held that content before; there was no interface to read it. Now there is. The practical change is a decision you can make in one sitting: open Ideas, read what's queued for the brand, and pick which item becomes your next memo instead of starting from a blank page. This release also changes how failures behave. Read errors in Hopper used to be swallowed quietly, which made a broken fetch look identical to an empty queue. Those errors now surface, so an empty Ideas list means empty, not broken.
Where It Is in Context Memo
Open your brand dashboard and go to Hopper. The new Ideas view sits inside that section as its own screen. It lists the ideas currently held for the brand you have selected, so switching brands switches the set you see. Nothing moved out of Hopper to make room for it.
How to Use It
- Sign in and select the brand you're working on. The dashboard loads scoped to that brand, and Hopper reads from the same selection.
- Open Hopper from the brand dashboard, then open the Ideas view. The screen returns the ideas stored for that brand.
- Read through the list and identify which ideas match a prompt or gap you're already trying to win. This is the step that replaces guessing at what's in the queue.
- Take your chosen idea into your memo drafting workflow and write it up as a citation-grade memo on your own domain. Hopper tells you what to write next; publishing still happens where it always has.
- If the view returns an error instead of a list, treat it as a read failure rather than an empty queue. Reload the screen. If it repeats, send us the error text and the brand so we can trace it.
- Re-check Ideas before your next publishing cycle so the queue informs the calendar instead of the other way around.
Why We Built It
The complaint was simple: "I have no visibility into what's in there." Ideas existed in Hopper with no place to look at them, which meant the queue could not influence what anyone actually wrote. Teams planned memos from memory and from whichever gap was loudest that week, and anything sitting in Hopper aged without being read. The silent-error behavior compounded it. A failed read looked like nothing to do, so a real problem could sit unreported for as long as nobody thought to question an empty screen. Both of those are now visible states you can act on.
What It Does Not Do Yet
This release covers viewing and browsing. It is a read surface, not a workflow engine, so anything you decide to do with an idea still happens in your memo drafting and publishing steps rather than inside the Ideas view. Error handling now surfaces read failures, but surfacing is not diagnosing: you'll see that a read failed, not why, which is why we're asking for the error text when it happens. And Hopper does not replace your CMS or your marketing automation stack. Those systems do more, and they should stay where they are; treat Ideas as the input that decides what gets written, then publish through the tooling you already own.
