Changelog

A text or Slack conversation that ends delivers conversation.completed

When a text or Slack conversation ends - the agent’s own end_call, a terminal step in its flow, or POST /v1/agents/conversations/{conversation_id}/end - the conversation.completed event now fans out to every subscribed workspace endpoint, and the agent’s webhook_url receives its post-call payload, exactly as they do when a voice call hangs up. An endpoint that opted into include: [messages] receives the transcript; include: [evaluations] receives the scores once the agent’s evaluation criteria have run.

Before this, the event was raised from the LiveKit room a voice call held, so a conversation with no room ended without a word to your endpoints: the row read completed, the delivery log stayed empty, and your evaluation criteria never ran on a chat.

What has not changed: a text or Slack conversation is a thread, not a call. It does not end because it went quiet, so a thread nobody closes still raises no event. Conversations that ended before today are not re-delivered.