Skip to main content
A conversation is one end-to-end interaction — a call, a chat thread, a voicemail. Each conversation belongs to one agent and owns:
  • A transcripts row with the full turn-by-turn content.
  • An optional recording (audio for voice, transcript-only for chat).
  • Zero or more conversation_analyses — the assessment saved each time the call is analyzed.
  • Zero or more analysis_findings — per-call observations, each tagged with a finding type.
Every conversation also carries the basics you see in the list: the agent, a reference id (the provider’s call id), the ended reason, duration, cost, and whether it arrived from a provider webhook or a direct upload.

​
Summaries

The conversation detail page can generate a short AI summary on demand. Click Generate summary and Zelto summarizes the transcript and caches the result on the row; opening the call again reads the cached summary instead of regenerating it.

​
Filtering

The conversations list filters on:
FilterMatches
AgentCalls handled by one agent.
Name / Reference IDA conversation’s title, or the provider’s call id.
Ended reasonThe call’s disposition (e.g. customer-ended-call).
Has transcriptConversations that have transcript content.
Has audioConversations with a playable recording.
Date rangeFiltered against when the call was ingested.
Filters persist in the URL, so a filtered list is shareable.

​
Findings and buckets

Any conversation can be linked to a finding — the durable, shareable issue it’s an example of — and curated findings can be pushed to Linear from the finding’s panel. You can also group related calls into a static bucket to analyze or hand off as a set. The assessment saved when a call is analyzed lives in its conversation_analyses row.