OleonWritten as it happens.
Activity is recorded at the moment of the event rather than assembled later. A log written after a complaint is not evidence, it is a statement.
Conversation records and audit
Proof of what happened, written down as it happens.
Every team believes it will remember what happened until the first time somebody disputes it. The useful property of a record is not that it is detailed. It is that it was written before anyone knew it would be needed.
Messages are append-only.
A message is only ever added to, or marked read. Nothing in the product edits or deletes one, which is what makes a thread quotable months later.
Including what the machines did.
MCP logs record what an AI client asked for and what it was given, so an agent acting on your data leaves the same trail a person would.
Usage you can reconcile.
The figures behind the invoice, itemised, so a bill can be checked rather than believed.
Tech specs
Every one of these is a screen in the product.
- Reported conversations
- Call logs
- Activity logs
- MCP logs
- Usage
Questions
Before you ask.
The ones we hear most about Conversation records and audit. If yours is not here, the answer is a message away.
Can a message be deleted?
Not by the product. Messages gain rows and change state; nothing edits or removes one. Deletion for a data subject request is handled separately and deliberately.
How long is history kept?
The API is the source of truth for history and search. The copy in your browser is a bounded cache, so clearing it loses nothing.
Do the logs cover the AI agent?
Yes, including MCP, where an external AI client is the one making the request.
Keep exploring.
More of what Oleon does.
All solutionsIt starts with one conversation.
Bring the channels you already answer on into one place, and see what the rest of the week looks like.
Not ready to sign up? Join the waitlist and we will come to you.
