Call lifecycle

After you submit a call, it moves through a fixed sequence of statuses on its own. You do not drive any of these transitions, they happen as VOIX processes the call.

Statuses

Status	Meaning
`received`	Registered from a “call started” submission; no recording yet.
`queued`	The recording has arrived and is waiting to be transcribed.
`transcribing`	The recording is being turned into a speaker-separated transcript.
`analyzing`	The transcript is being scored, with tasks and contacts extracted.
`completed`	Processing is finished; the full call record is available.
`failed`	Processing could not complete. You may resubmit the call.

The typical path


received  →  queued  →  transcribing  →  analyzing  →  completed
(beat 1)     (beat 2 / recording in)

A call submitted in a single request (recording included) starts at queued and skips received.

Idempotency and retries

The callId you choose is what makes the pipeline safe to retry.

Resubmitting the same callId updates the existing call instead of creating a second one.
A call that has already completed is not reprocessed if it is sent again, so an accidental duplicate submission is harmless.
A failed call can be resubmitted to try again.

Because retries are keyed on callId, you can safely re-send a call if you are unsure the first request got through, you will never create a duplicate or trigger a second round of analysis on a finished call.