conversation.completed

​

Payload

{
  "id": "whd_4Vk9pS2dL",
  "event": "conversation.completed",
  "createdAt": "2026-09-11T15:31:56.207Z",
  "data": {
    "conversationId": "conv_7Yn2kP",
    "status": "completed",
    "sourceType": "phone",
    "outcome": "meeting_booked"
  }
}

​

How a conversation completes

• Mark as Done. Somebody marks the conversation done from the app, and it completes straight away.
• Analysis finishes. Custral analyses a conversation after a call ends, after its recording is processed, and when it is closed. An analysis that ends with no suggested actions waiting completes the conversation.

​

Worth knowing

• It can fire more than once. Marking an already completed conversation done delivers again, and so does each later analysis run that ends in completed, for example when insights are regenerated or a report template is added. Deduplicate on conversationId if you only want the first.
• outcome is a snapshot. Setting or changing the outcome afterwards arrives as conversation.outcome_set.
• Closing sends nothing by itself. A closed conversation reports completed only once its analysis finishes.

​

Example

custral.on("conversation.completed", async (event) => {
  const {conversationId, sourceType, outcome} = event.data;
  if (sourceType !== "phone") return;

  // Completion can be delivered more than once for one conversation.
  const first = await cache.add(`completed:${conversationId}`); // false if already present
  if (!first) return;

  await reporting.recordCall({conversationId, outcome: outcome ?? null});
});