Skip to main content
Choose the output your application needs, then open its setup guide: These products compose, but they do not replace one another. Hear transcribes audio. Recap consumes a completed transcript. Post-call data capture applies an agent-specific schema. Trace evaluates eligible calls against compliance rules.

Speaker diarization: who said what

Speaker diarization with Hear groups a recorded conversation into speaker turns with timestamps. Use mono diarization or existing stereo channel separation to prepare transcripts for review. Speaker labels do not verify a person’s identity or determine their business role.

Fastest path from a recording to notes

Follow Recap’s recording workflow to submit a timestamped Hear job, wait for a completed Recap record, and read the notes. That guide owns the examples for recordings, streaming transcripts, and existing utterances, plus packs, output language, and callbacks.

Recap vs post-call data capture

Use Recap when the object should be consistent across calls and agents: summary, action items, next steps, disposition, talk ratio, signals, and pack-defined fields. Use post-call data capture when one Omni agent needs a custom JSON Schema such as order id, appointment date, or follow-up-required. It runs after the call and delivers the result to that agent’s signed webhook. If both are enabled, treat them as separate artifacts. Do not make one webhook consumer guess whether a payload is a Recap record or an agent extraction.

Recap vs Trace

Recap describes what happened and what should happen next. Trace evaluates whether an eligible call followed configured rules and preserves evidence for review. A call can produce both. Trace does not turn an arbitrary recording into a compliance scorecard merely because Hear transcribed it. Read Trace eligibility and setup before promising compliance coverage for imported or external calls.

Bring calls from another system

For a recording you already control, submit a Hear job directly. For continuous imports from supported phone systems, use an inbound call integration. Imports still require the relevant Recap or Trace features to be enabled; connecting a phone system does not silently enable paid processing.

Recap API and records

Inputs, packs, webhooks, CRM fields, records, and retention.

Timestamped Hear jobs

Recording submission, speaker labels, subtitles, and job lifecycle.

Post-call data capture

Agent-specific JSON Schema extraction after Omni calls.

Trace compliance

Eligibility, rule packs, scorecards, and exposure.