Get call results

Read results from the surface that owns the call workflow.

Result flow

Preview ──▶ Preview status
Batch ────▶ Contact export + answered call detail
Drip ─────▶ Signed callback + failed-delivery queue
Inbound ──▶ Answered call detail

Need	Read
One preview result	agent preview-status
Answered calls for one process	process list-calls
Post-tool output for one answered call	process get-call
All Batch contact outcomes	process export-contacts
Normal Drip terminal delivery	Signed HTTPS callback
Undelivered Drip outcomes	Failed-callback queue

Prompt your AI agent

Recommended

Use the applicable `dino-ping` or `dino-pong` skill to retrieve results for <workflow and ID>.
Select the result surface that owns this workflow.
Keep every call lookup bound to its process.
Return terminal status, structured post-tool output, and Lens data only when present.
For Drip failures, identify the customer records that need durable reconciliation.
Do not acknowledge any failure until I confirm that its outcome is committed.

Use the Dino CLI directly

dino agent preview-status --dd-id <dd-id>

dino process list-calls --process-id <process-id> --limit 50 --offset 0
dino process get-call --process-id <process-id> --call-id <call-id>

dino process failed-callbacks --process-id <drip-process-id>

Reconcile Drip failures

[1] Read failures ──▶ [2] Validate payload ──▶ [3] Commit outcome
                                                      │
                                                      ▼
                              [5] Read again ◀── [4] Acknowledge

After durable application, write only the successful failure IDs to a JSON array.

dino process ack-failed-callbacks --process-id <process-id> \
  --input <absolute-applied-failure-ids.json> \
  --confirm-mutation process.drip.failedCallbacks.ack

Use Drip callback receiver for signature verification and receiver deployment.

Gotchas

• list-calls contains answered calls, not every contact outcome.
• Process call pages do not guarantee newest-first order.
• A call ID from another process returns 404.
• A Lens link can expire and can be absent from a terminal result.
• Acknowledge only Drip outcomes that your application committed durably.