For teams whose answers live in docs nobody has open

The answer was in a doc. The reply was from memory.

Someone asks in a channel. A teammate answers from memory — helpful, fast, and a little bit wrong. The real answer was written down the whole time, in a doc nobody had open, so the thread now carries a confident guess instead of the source. The next person to search finds the guess.

MikeMike · Tuesday 10:38am what's our refund window on annual plans? customer's asking
SarahSarah · 10:41am pretty sure it's 30 days? might be 14, check with finance
○ answered from memory — maybe
· the real answer was in the billing doc the whole time — nobody had it open

thread staged with our recurring cast

01 · What Ayven does with the same question — answer, with the source

She reads the docs and answers with the citation attached.

Ayven answers in the thread from the docs you've connected — and shows the citation: source and location, so you can check her rather than trust her. She cites what she actually read. When the answer isn't written down anywhere yet, she runs a research mission and returns a document instead of a guess.

10:38read the connected docs — the billing policy, the terms doc
10:42answered in the thread with the citation — source and section
Weda later question wasn't in any doc — ran a research mission instead of guessing
Wedreturned a drafted document for review — sources listed

02 · The register — an answer you can check

The answer arrives grounded in the source, not in memory.

Ayven APP · Tuesday 10:42am Annual plans have a 14-day refund window from renewal — not 30. I'm pulling that from the billing policy, and here's exactly where, so you don't have to take my word for it.
Answered from 1 connected source
Refund window — annual plansView
14 days from the renewal date; pro-rated after that. Reads straight from the policy — this is what it says, not what anyone remembered.
CitationBilling Policy · §4 Refunds — "annual plans, 14 days"
Cited — Billing Policy §4 · 10:42

the citation is the receipt — the answer points at the exact place it came from

03 · It's real — the product, not a promise

The answer in the thread, the document when there isn't one.

Ayven answering a question in a Slack thread
staged example — the answer arrives where the question was asked
Ayven document with its sources listed
when the answer isn't written down, a research mission returns a document — with the sources it read

threads shown are staged with our recurring cast · screenshots are the live product

04 · The honest answer — where this fits, and where it doesn't

Search returns links. This returns the answer, with its citation.

Honest scope first: Ayven is not an enterprise search index. If you need a company-wide search layer that crawls every system and ranks documents, a dedicated tool like Glean is built for that, and Ayven doesn't claim parity. What Ayven does is narrower and sits closer to the work: it reads the docs you connect, answers the question inside the conversation with the citation, and — because it's a coordinator, not just a search box — follows through on what the answer requires.

Search returns links; Ayven returns the answer

A search tool hands you ranked documents and leaves the reading to you. Ayven answers the actual question in the thread and shows the citation, so the resolution and its source land together where the question was asked.

answer + citation, in the conversation

It cites what it read, not everything you own

Ayven answers from the sources you connect and points at the exact place the answer came from. It doesn't claim to index every system in the company — it's honest about its reach, which is what makes the citation trustworthy.

grounded, scoped, checkable

When it isn't written down, it researches

If no doc has the answer, Ayven doesn't invent one. It runs a research mission across the sources it can reach and returns a drafted document with those sources listed — a document to review, not a guess to trust.

a document, not a hallucination

The answer can carry a loop

An answer often implies a task — update the stale doc, get the policy confirmed. Ayven can open that loop, route it to an owner, and chase it to done, which a search box can't do.

answer, then follow-through

"How do I know it isn't just making the citation up?"

Fair — a confident wrong answer is worse than no answer. That's the whole point of showing the source and location: every answer points at the exact place it came from, so you can open the doc and read the line yourself. When Ayven can't ground an answer in a connected source, it says so and offers to research it rather than filling the gap from memory.

Stop answering from memory. Answer with the source.

Start free

connect your docs · ask in Slack · she answers with the citation, or researches when there isn't one yet