Anatomy of an agent
An agent’s company membership and a conversation’s company attribution are different.
Membership says which companies the agent can work for; each conversation still belongs
to at most one company. See Companies.
Agents are created the first time a conversation references them: ingestion looks up the
provider’s external id and reuses the matching agent, or creates one if it’s
new. If a provider rotates external ids from one conversation to the next, Zelto can collapse
those onto a single agent with an org-level pattern, so you don’t accumulate
duplicates.
Agent versions and experiments
Keep one agent identity across releases and report which deployed version handled each conversation. A version can differ in its prompt or pipeline, and experiments compare two versions of the same agent. For LiveKit and custom integrations, send top-levelversion on every conversation upload.
Read Agent versions before integrating: it covers the
identifier contract, snapshots, automatic fallback, and verification before
launch. Draft candidates created in Zelto are separate from deployed versions.
Agent activity
Click into an agent for a conversation-volume trend chart, an hour-by-day heatmap, and its most recent conversations, alongside its system prompt and the findings surfaced from its conversations. When an agent has a decision tree and mapped conversations, its Decision Tree tab also shows a flow diagram of how conversations moved between the tree’s steps. It only includes steps that conversations actually traversed, so it stays out of the way until mappings are available for that prompt version. Each agent can also post a daily status message to Slack — yesterday’s conversation count, at a time you choose — once Slack is connected.How conversations reach an agent
Every payload Zelto receives lands in the append-only webhooks table first, then becomes a conversation with a turn-by-turn transcript. How each provider delivers a conversation:
Recording the raw payload first means ingestion is always replayable, so a
delivery is never lost even if processing has to be re-run.
Connection status
Each agent’s detail page carries a Connections card — the at-a-glance signal that conversations are reaching Zelto. It names the provider the agent ingests from and reports on the last conversation received:- “Last call received 2 hours ago” — conversations are flowing; ingestion is healthy.
- “No recent calls” / “integration may be stale” — connected, but nothing has arrived lately. Place a test conversation, or check that the provider is still sending.
- “Last webhook errored” — the most recent delivery reached Zelto but couldn’t be turned into a conversation.
- “No calls received yet” — the agent has a provider but has never received a conversation.

