Turn your team's meetings into a searchable knowledge base you can ask questions across

Every recorded meeting in your workspace becomes part of a searchable knowledge base you can ask questions across. Reline's RAG chat works at three scopes — one note, one folder, or the whole workspace — and every answer links back to the exact transcript second it came from, so the team's memory is both searchable and verifiable.

A team knowledge base from meeting notes is a searchable, askable corpus of every meeting your team has recorded — not a folder of files you have to reopen and skim. You ask a question in plain language, and Reline retrieves the relevant moments across your captured meetings and answers them with citations back to the transcript.

Three things make it a knowledge base rather than a pile of recordings: it works at three RAG scopes (one note, one folder, or the whole workspace), every answer is grounded in your actual transcripts, and each answer links to the exact second it came from. You're not trusting a floating summary — you can click straight to the moment someone said it.

The contrast with a static wiki is the whole point. A wiki is only as current as the last person who remembered to write something down. This fills itself from the meetings you're already recording. The decision someone made on a call is in the base the moment the meeting ends — nobody has to transcribe it into a doc first.

Reline gives you three scopes for asking questions, and choosing the right one is how you keep answers precise instead of noisy.

One note is the tightest scope: ask about a single meeting. Great for "what did we agree at the end of this call?" without pulling in anything else. One folder widens it to a project, a client, or a topic — every meeting you've grouped together becomes one askable body. The whole workspace is the broadest: ask AI across all our team meetings at once, and Reline searches everything the team has captured.

The pattern most teams settle into: folder scope for day-to-day work (one client, one initiative), workspace scope when you genuinely need to chat with all our company meeting notes — like surfacing every call that touched a theme across quarters.

Every answer links to the exact transcript timestamp it came from, so you can verify a claim in one click instead of trusting an ungrounded summary. That single behavior is what turns recordings into a single source of truth for meeting decisions rather than a confident guess.

It matters most when stakes are real. When someone asks "didn't we decide to hold the price?", an unsourced AI answer is just another opinion in the thread. A cited answer jumps you to the moment it was said, in whose voice, in what context. You're not arguing about what happened — you're watching it.

This is also what makes the base trustworthy across many seats. The more people rely on it, the more important it is that answers can be checked rather than taken on faith. Verifiability is the difference between a team record people defer to and one they quietly distrust.

You don't set up a knowledge base — you accumulate one by recording and organizing as you go. Here's the path from first meeting to asking across everything.

1. Record meetings bot-free. Reline captures your mic and your system audio directly — no bot joins the call, so there's no "Reline has entered the meeting" awkwardness and nothing to invite. Capture runs locally; transcription then runs in the cloud on Soniox across 60+ languages.
2. Organize into folders and teamspaces. Group meetings by project, client, or function. The folder structure you create is the same structure your RAG scopes follow — a well-organized workspace is a well-scoped knowledge base.
3. Apply a shared Lens. A Lens is a reusable summary template. Apply the same one across a team's meetings and every recap comes out in a consistent shape — same sections, same decision and action-item format — so the base reads coherently instead of like ten different note-takers.
4. Ask across a folder or the whole workspace. Once meetings are flowing in and organized, open RAG chat at the scope you need and ask. The answers compound: every new meeting makes the base more useful without anyone writing a word of documentation.

RAG results respect permissions, always. Reline is private-by-default: a workspace role alone grants no access to any note or folder. People only get answers from content they've been explicitly granted, even at workspace scope — the search reaches everything they're allowed to see and nothing more.

That's what keeps the base safe to grow across many seats. Per-client folders stay walled between account teams — one team's RAG chat can't surface another client's calls just because both live in the same workspace. An "open" teamspace gives its Members Edit access only; Owners and Admins get no silent reach into content they haven't been granted. Web-publish is a separate, deliberate public link — it's never the same thing as workspace visibility.

The base earns its keep on the questions you'd otherwise answer by scrubbing through old recordings or pinging whoever was on the call. Each of these returns a cited, timestamp-linked answer at folder or workspace scope:

• "What did we decide about pricing in Q1?" — pulls the decision and links you to the moment it was made.
• "What are the open action items for the Acme account?" — sweeps every call in the Acme folder for commitments that were named.
• "Which calls mentioned renewal risk?" — surfaces every meeting where the theme came up, across the whole workspace.
• "What did the customer say they needed before they'd expand?" — answers in the customer's own words, with the timestamp.
• "Who owns the migration follow-up?" — finds where ownership was assigned, not where you think it was.

Notice what these have in common: they cut across many meetings, and the answer is only trustworthy if you can check it. That's exactly the combination RAG chat is built for — retrieval across the corpus, grounded in citations you can open.

Reline is the meeting layer, and it complements a wiki rather than replacing it. Your wiki holds the deliberate, written canon — the things someone sat down to document. Reline holds the living record of what was actually said and decided in the room. Together they cover both halves of how teams remember.

Two honest scope notes so you know what you're buying. Transcription is cloud-based — audio is captured locally, then processed on Soniox under a data-processing agreement; it does not run on your machine. And there's no live connector write-back yet: Slack, Notion, and Linear integrations are rolling out, not available today, so don't plan around auto-syncing decisions into those tools right now. What works today is the part that matters most — recording, organizing, and asking across the whole base with cited answers.

If you're weighing Reline against other meeting tools, compare on the things that compound: bot-free capture, three RAG scopes, citation-backed answers, and a permission model that lets the base grow safely across seats.

Start small — record a few meetings into one folder, apply a shared Lens, and ask your first question across them. The base compounds from there, and it's free to begin.