> ## 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.

# Events

> Distinguish client events, monitoring selections, and post-call notifications before designing an integration.

An event describes something an integration may need to observe or submit. The event category determines its timing, recipient, and data requirements.

| Category | Configuration | Purpose |
| - | - | - |
| Client events | `conversation_config.conversation.client_events` | Select conversation events intended for a supported client. |
| Monitoring events | `conversation_config.conversation.monitoring_events` | Select events for a supported monitoring path. |
| Post-call notifications | Workspace `webhooks.events` and permitted agent overrides. | Request notifications associated with completed or failed calls. |

The public schemas describe these selections. They do not establish a released socket protocol, SDK subscription method, delivery order, or replay mechanism.

## Choose an event design

Use [client events](/agents-platform/advanced/events/client-events) to plan what the interface needs to display. Use [client-to-server context](/agents-platform/advanced/events/client-to-server) to define what a supported client may submit. Use [post-call webhooks](/agents-platform/advanced/post-call-webhooks) for server-side notification preparation.

Document the event's owner, required fields, privacy classification, conversation identifier, and failure behavior. Treat external event data as untrusted input. Separate displaying an event from authorizing an action based on it.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Are event names proof of delivery?" id="faq-event-schema-delivery">No. Verify the released transport, emitted payload, authorization, and failure behavior before implementing a subscription.</Accordion>
  <Accordion title="Can a client event replace a post-call notification?" id="faq-event-notification-types">They serve different recipients and lifecycle points. Choose the supported path for the job rather than assuming identical timing or persistence.</Accordion>
</AccordionGroup>


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