Sessions
The container Auron uses to group everything that happens during a single interaction.
A session is one bounded interaction: a meeting, a voice call, or a chat. It's the unit everything else in the capture pipeline hangs off. The transcript, the signals detected inside it, the artefacts it produces, and any automation it triggers all belong to exactly one session.
What creates a session
A meeting is an agent joining a live call, video or voice, running for as long as the call does. A conversation is a chat thread with an agent, which can run over minutes or days instead of a single sitting.
Both kinds are usually linked to an entity record. That link is what lets everything the session produces attach to the right account, deal or patient instead of floating on its own.
What a session holds
A session carries the live or recorded transcript, any signals the configured detectors picked up while it ran, and interactive answers such as charts, tables and stat cards the agent rendered inline. Once it ends, it also produces the artefacts and reports generated from it.
Where sessions show up
Every session is listed in the organization's session history, Activities in the console, History in the mobile app, regardless of which surface it started on. A session started from a phone and one started from a browser are the same kind of object underneath.