Call lifecycle
After you submit a call, it moves through a fixed sequence of statuses automatically. You do not drive any of these transitions; they occur 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 converted to 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. The call may be resubmitted. |
The typical path
received → queued → transcribing → analyzing → completed
(phase 1) (phase 2 / recording in)A call submitted in a single request, with the 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
callIdupdates the existing call instead of creating a second one. - A call that has already
completedis not reprocessed if it is submitted again, so an accidental duplicate submission is harmless. - A
failedcall can be resubmitted to try again.
Because retries are keyed on callId, you can safely resend a call when you are
unsure whether the first request succeeded, without creating a duplicate or
triggering a second round of analysis on a finished call.
Last updated on