Last verified: October 10, 2026
What You Can Now Do
Context Memo customers can now dismiss offers in chat and have those dismissals persist across page refreshes, and see cleaner mid-answer updates without empty rows appearing. Before this deploy, a dismissed offer came back the next time the page loaded, so the same person could close the same card several times in one session. That no longer happens. The second fix is visual but it matters for trust: while an answer is still streaming and the view refreshes mid-response, the interface no longer draws placeholder rows with nothing in them. For you, this removes a support pattern. If your team has been fielding "I already closed that" messages or screenshots of blank rows in a live chat, those reports should stop, and you can read dismissal behavior as a real signal rather than a UI artifact.
Where It Is in Context Memo
Both changes live in the chat experience, on the offer cards shown inside a conversation and in the answer area that updates while a response is being generated. There is no new screen, setting, or toggle. Dismissal state is now retained and read back when the page loads, so the behavior applies to existing conversations as soon as the deploy lands for your workspace.
How to Use It
- Open a chat where offers appear and run a prompt that surfaces one. The offer card renders in the conversation as it did before.
- Dismiss the card. It clears from the thread immediately.
- Reload the browser and reopen the same conversation. The offer you dismissed stays gone instead of reappearing.
- Run a longer prompt and watch the answer as it updates mid-response. Rows now render only once they carry content, so the thread stays readable while the answer is still assembling.
- Check your support queue and session recordings over the next week for repeat-dismissal complaints and blank-row screenshots. If either still shows up, capture the conversation and send it to us with the timestamp.
Why We Built It
The complaint was plain: customers had already closed an offer, and the product kept asking again. Re-dismissing the same card is a small irritation on its own, but it quietly taught people that the chat wasn't tracking what they did, which is a bad lesson to teach anyone evaluating your brand in a live conversation. The empty rows had the same effect from a different direction, making a working answer look broken while it was still being written. Both issues cost attention at the exact moment a buyer was engaged, and they generated support volume for work that produced nothing.
What It Does Not Do Yet
This deploy changes behavior only. It does not add reporting on dismissals, so you cannot yet see which offers get closed most often or segment that by conversation inside Context Memo. If you need that view now, pull it from your own analytics on the chat surface and treat the dismissal event as the signal. There are also no new controls for offer frequency or re-display rules; a dismissal persists, and that is the full extent of the change.