The primitives
On the spine
Conversations sit at the center of the spine: channels deliver to an entity, and every touch lands as an interaction on that entity’s conversation. The component reads entity identity to attach each interaction to the right thread, and writes the interaction record and its resulting outcome. Every change - interaction created, conversation updated, outcome recorded - emits an event.What stays hidden
Channel-specific storage details. How a WhatsApp payload, a call recording reference, and a raw email are persisted differs per channel, and none of it surfaces in the conversation model. You query threads, interactions, and outcomes; the per-channel record formats stay internal.Status
In build. The channel-neutral thread model is shipping in the open. Today, each call produces a transcript (Recordings & Transcripts) and the platform shows a per-person conversation view (Conversation view). There is no callable conversations API yet.Go deeper
Conversation view
The per-person conversation view in the platform today.
Recordings & Transcripts
What each call produces today - the first interaction type.
Entities
The system-of-record identity every conversation belongs to.
Events
The events conversations and interactions emit.