Records
What was said. Written as it happened.
Every business eventually has the argument about what was said and who said it. Records is the part of the product that settles it, and it is written while the thing is happening rather than assembled afterwards.
As it happens
The record writes itself.
Not assembled afterwards.
The conversation. Whoever answers, a person or the agent, and on whichever channel, it happens in the inbox like any other.
The record. Each step lands as it happens, including a connected AI reading it, logged under the person whose access it used. A message only ever gains its delivery state.
An example: a customer asks where their order is; the record shows the message, the conversation being assigned, an AI connector reading it through get_conversation, the reply with its delivered and read times, and the conversation being exported.
Records
Everything, written down.
Including what the machines did.
Append-only messages. Not edited, not quietly removed. By anyone.
Delivery states. Sent, delivered and read, each with its own time.
Activity logs. Who did what in the project, and when.
AI tool calls. What a connected AI read or did, and for whom.
Reported messages. Flagged by the team or the AI, worked to resolved.
Usage over time. Fine enough to check an invoice against.
Exports. A large export arrives as a file, not a timeout.
Access by project. An enterprise alone opens nobody's conversations.
Evidence
Nobody edits history.
Not even the admin.
A message gains a delivery state and nothing else. A record the most powerful person in the account could change would not be a record, so there is no button for it, for anyone.
Tech specs
Everything in Records.
- Reported messages
- Activity logs
- Agent tool logs
- Usage over time
Questions
Before you ask.
The ones we hear most about Records. If yours is not here, the answer is a message away.
Can an administrator delete a message?
No. That is deliberate. A record that the most powerful person in the account can edit is not a record.
Can we export it?
Yes, and a large export is delivered as a file to download rather than squeezed through a page that would time out.
Who can read all of this?
Access follows the project and the organization. Belonging to an enterprise alone does not open anybody's conversations.
Keep exploring.
More of what Oleon does.
All productsIt 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.

Oleon
