You knew this last week. Someone asked about the rollout date, you gave a number, and now it is gone. With Sayli, it is not gone. The call you finished is the call you can ask.
Memory is the part that compounds
Every meeting you finish is transcribed and indexed. That means past calls are retrievable, not just readable. The product gets better the longer you use it, because each call adds to what you can find later.
You do not file anything. You finish a call, and it joins the rest.
Search across every call
Cross-call search finds anything across every meeting you are allowed to see. A phrase, a name, a decision, a number someone said out loud. You type what you remember, and Sayli surfaces the moment it was said.
During a live call, Recall can pull a fact from up to 200 past meetings you have access to. The answer streams back while you are still talking.
You do not need the exact words. A rough memory of the topic is enough to find the moment. See Search.
Ask across your history
Ask across your history takes one question and runs it over all of your meetings, or over a single folder. You ask in plain language, and the answer comes back with the calls it came from.
Threads can persist, so a line of questioning stays where you left it. If you would rather they did not, one setting turns persistence off and purges what was stored.
Folders, digests, and the weekly mirror
Folders let you group meetings by hand. A client, a project, a hiring loop. Once grouped, you can ask a question against just that folder.
Three things arrive on their own.
What stays private
Retrieval is gated by visibility. You only ever retrieve from meetings you are allowed to see, and never from anyone else's. The same rule covers search, Ask, and live Recall.
Bookmarks are yours. They are private, and the language model never reads them.
Memory respects the same access rules as everything else in Sayli. Read how that works in Visibility.