Event lifecycle

1. Partner creates a conversation via REST.
2. Core dispatches the dial; JetStream conv.events.* stays internal.
3. Worker maps internal outbox events to the public Partner envelope, evaluates event subscriptions + agent.id filters, then POSTs signed HTTPS webhooks ( conversation.dispatched → connected → ended / failed).
4. Optional external NATS subject partner.events.{customer_id} mirrors the same public payload when enabled.

Inspect each attempt under Govern → Partner API → Recent Deliveries .