> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Post-call webhooks

> Review persisted notification preferences and prepare a receiver without assuming webhook resource storage or delivery is released.

A post-call webhook is a server notification associated with a completed or failed call. It can support downstream review or business processing once its event and delivery contract is released.

<Note>
  Workspace notification preferences persist, but the current webhook-resource CRUD is placeholder behavior. Creating a resource returns an identifier without verified persistence. There is no verified delivery, signature, retry, or callback-log implementation. Do not use the current create response as evidence of a working receiver.
</Note>

## Configuration shape

Workspace settings expose `webhooks.post_call_webhook_id`, `webhooks.events`, and `webhooks.transcript_format`. Agent-specific intent belongs under `platform_settings.workspace_overrides.webhooks`. Transcript format accepts `json` or `opentelemetry`.

Use [Get Agents Platform settings](/api-reference/agents-platform/get-agents-platform-settings) and [Update Agents Platform settings](/api-reference/agents-platform/update-agents-platform-settings) to inspect the committed contract. The dashboard currently reads the selected post-call default; it is not a verified end-to-end setup wizard.

## Prepare a receiver

| Requirement | Design to review before delivery is enabled |
| - | - |
| Authentication | Verify the exact released signature or authentication contract against raw request bytes. |
| Event ownership | Bind the event to the intended workspace, conversation, and agent version. |
| Repeated delivery | Deduplicate using a released stable event identifier and persist processing state. |
| Processing | Acknowledge according to the released delivery contract and run expensive work in a durable worker. |
| Failures | Record failed or uncertain processing without silently repeating business mutations. |
| Data | Minimize transcript/audio retention and restrict access to private content. |

No signature-header name, payload envelope, or retry schedule is promised here. Add executable receiver examples when those contracts are released and verified.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does a saved webhook ID prove the receiver is registered?" id="faq-post-call-resource">No. Preference storage and webhook resource persistence are separate. Current resource CRUD does not establish a working registration.</Accordion>
  <Accordion title="Will selecting OpenTelemetry send traces to my collector?" id="faq-post-call-otel">No verified collector delivery is established. Review [OpenTelemetry](/agents-platform/monitor/opentelemetry) for the supported stored-data distinction.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.