# Exchanges & Conversation Lifecycle

An Exchange is the record of a conversation with an Assistant. It belongs to the conversation's Project and stores the messages, events, and results produced during that call.

## Before the call

An Assistant defines the conversation's behavior, and a Channel routes callers to it. Creating either resource does not start a conversation or produce a completed Exchange.

For WebRTC, the caller must connect using the credentials returned by the Calls API. For SIP, the call must reach the configured Channel through your phone system.

## During the conversation

Reecall registers an Exchange at call startup with `status: "inProgress"`. The initial record identifies the Assistant and Project, but its messages and events are initially empty.

The Assistant processes speech and can use Tools during the call. Treat the running Exchange as an indication that a conversation has started. Its transcript and results are finalized after the conversation ends.

## After the call

Reecall saves the final conversation data and sets `status: "completed"`. The available results depend on the Assistant's configuration:

| Result | Contains |
| --- | --- |
| `messages` | The conversation transcript |
| `events` | Conversation events, such as Tool calls and transfers |
| `resources` | Configuration metadata and media references |
| `duration` | Conversation duration in seconds |
| `data` | Structured fields produced by configured Data Extraction |
| `audioUrl` | A recording URL, when a recording is available |

Recording and Data Extraction are optional. A completed Exchange does not guarantee either result. Usage and cost are queried separately through the [Metrics API](/docs/fetching-system-metrics).

If registration at startup fails, Reecall attempts to create the completed record at the end of the call. An integration that reacts to completion should handle this case as well as the usual update.

## Read conversation results

Use the Data API to list Exchanges or retrieve one by its `id`. Filter by `assistantId` to find an Assistant's conversations, and check `status` before processing final results. Project-scoped keys restrict these queries to their Project.

Integration API keys can read Exchanges. Reecall manages their creation and updates.

The [Quickstart](/docs/quickstart#step-6-read-the-conversation-record) includes a query for your first conversation. [Post-conversation processing](/docs/post-conversation) documents the Exchange fields, query examples, and Hook configuration.

## Trigger follow-up actions

A Hook can run a Process when an Exchange changes. For example, a Process can send extracted booking details to a CRM after the call.

Entity events can also occur before completion. Check for `status: "completed"` inside the Process before sending summaries or exporting results. See [Workflows & Hooks](/docs/workflows-and-hooks) for how these resources fit together.
