A little help. A clear record.

dyna.ai - Call-review guide

Build a bot. Agree its boundaries. Follow the evidence.

Your organisation. Your operating rules. Build lending and servicing workflows with reviewed policies, controlled access and a record of the decisions behind the work.

Review a recorded call

Sign in to Passer. Open Call recordings in the voice workspace, then select a call. Your assigned role and access to the parent call or mission determine which records you can review.

Listen and follow

Use the audio controls to play, pause, seek or change playback speed. Elapsed time and duration refer to the recording. Changing the selected call resets the player and transcript-follow state. The transcript appears beside the recording. When timestamped turns are available, select a turn to seek to that point. Follow playback keeps the current turn visible. Switch it off to read another part of the transcript while listening.

A transcript without recording-relative timestamps remains readable. Its wall-clock timestamps are not seek positions. A reviewer or operator can request Align transcript to recording for a supported retained recording. Preparation runs in the background. The review shows progress and offers Retry transcript timing if preparation fails. Resolve the reported failure before requesting a retry. An Auditor can read prepared timing but cannot request preparation.

Generated alignment is approximate. It maps the saved transcript to the recording and preserves the saved words and speaker labels. Listen to the audio when timing or wording matters. The alignment does not certify that the transcript is complete or accurate.

Missing recordings

A call can have a transcript without retained audio. The review shows when no recording is available. It does not create a recording for a past call or substitute browser speech for the conversation.

If your access changes, audio playback and transcript access may stop. Ask your administrator to check your role and the record's access restrictions.

Administrator notes

Recordings remain private. Each audio request checks the caller's permissions. The server retrieves audio from a configured provider or a private call attachment. It does not expose provider credentials or accept arbitrary recording URLs.

Alignment needs its enabled site setting, configured provider credential and a worker with access to the recording source. Historical Dograh recordings require the worker's Dograh connection settings as well as the web backend's settings. A worker failure before provider access does not establish a provider outage.

Prepared alignment and the matching audio use a private cache with a seven-day expiry and hourly cleanup. The original call record and recording follow their own retention settings. Disable new alignment requests with the site setting when the processor has not been approved for that organisation.

API

Authenticate each request with a Frappe session or Authorization: token API_KEY:API_SECRET. Session mutations also require X-Frappe-CSRF-Token. Never embed a service key in a public web page.

Supported record types are Passer Call and Voice Test Call. JSON methods return business data under message. The audio endpoint returns binary audio. HTTP 206 indicates a byte range and 416 indicates an invalid range. Treat HTTP 403 as an access denial. Do not repeatedly retry it.

Example using an environment variable populated by your secret manager:

bash curl --get 'https://passer.dynaai.us/api/method/dyna_control.call_review.detail' \ -H "Authorization: token $PASSER_API_KEY:$PASSER_API_SECRET" \ --data-urlencode 'doctype=Passer Call' \ --data-urlencode "name=$PASSER_CALL_ID"

Use the authenticated OpenAPI endpoint for the deployed method list. Call-review access does not grant permission to publish policies or launch calls.