How do you remember follow-ups after meetings, calls, and chats?
by•
Hey Product Hunt 👋
Our website resonics.ai is live now!!
We’re building a conversation memory layer for meetings and calls - something that helps individuals and teams remember what was decided, who owns what, what needs follow-up, and where the original context came from.
A lot of tools can record or summarise conversations, but the real pain usually comes later: finding the right decision, remembering the next step, or knowing why something was agreed.
We welcome your feedbacks and thoughts.
54 views
Replies
Great problem to tackle! I used to rely on scattered notes and calendar reminders, but they quickly became disconnected from the original conversation.
What I've found most valuable is having follow-ups linked to their context—who said what, why a decision was made, and the exact discussion behind it. Without that context, reminders often lose their meaning after a few days.
One question: how do you handle follow-ups when a decision evolves across multiple meetings? Does resonics.ai connect related conversations into a single timeline, or does each meeting remain independent?
Looking forward to seeing how this evolves!
@kartikbatchu2003 Thank you — you're asking the exact question that separates a real memory tool from a notes app. Connecting related conversations into one evolving timeline, especially decisions that shift across meetings is actively in the works. You've picked up on the exact use case at the heart of Resonics. Longer answer to your question is the fun part, and it's coming soon. Stay tuned.
@jyoti_tiwari_resonicsai That's exciting to hear! I think that's where conversation memory becomes truly valuable.
Building ChatHop made me realize a similar problem from a different angle—people often remember that a conversation happened but struggle to find the exact context later. You're solving what happens after the conversation, while ChatHop helps people quickly get back to the right one.
I'd love to be able to ask, "Why did we decide to delay Feature X?" and have the system trace that answer across multiple meetings, chats, and decisions with the original context attached. Looking forward to seeing where you take it!
I like the distinction between summarizing a conversation and being able to recall why something was decided later! That feels like the part where the product becomes much more technically demanding once teams use it every day.
When you think about scaling Resonics for teams, what feels like the bigger challenge so far - capturing context across different tools like meetings, calls, and chats, keeping memory/retrieval accurate as conversations accumulate, or keeping the AI processing efficient enough for ongoing team usage?