The conversation type is how diio classifies each interaction it analyzes. When a meeting, call, or message thread ends and diio processes it, the result appears in your list under one of three types: Meeting, Call, or Message.

This classification matters because it determines how the analysis is displayed, which fields are available, and how activity is recorded in your CRM.

A Meeting is a synchronous encounter with two or more people, whether remote or in person. Applies to:

Video calls on Zoom, Google Meet, or Microsoft Teams.

In-person meetings whose audio was uploaded to diio via WhatsApp.

Meetings show the complete transcript with voice attribution, the executive summary, commitments grouped by owner, playbook fields, and the Success Prediction.

A Call is a voice conversation between two people, typically shorter than a meeting. Applies to:

Calls made from HubSpot Call or Aircall.

Cell phone audio uploaded to diio that the user classified as a call.

The analysis is identical to Meeting, but the activity is recorded in the CRM as a Call (not a Meeting), which may affect any automation flows you have configured.

A Message is a written thread with one or more people. Applies to:

WhatsApp conversations captured by the Chrome extension.

LinkedIn messages captured by the Chrome extension.

Intercom threads synced by the integration.

Messages are analyzed as a whole thread, not message by message. The analysis extracts commitments, detects relevant topics, and evaluates the overall mood of the thread.

The capture channel is where the conversation came in: Zoom, HubSpot Call, WhatsApp Web, LinkedIn, etc.

The type is how it is classified afterwards: Meeting, Call, or Message.

Example: audio uploaded via WhatsApp can end up as Meeting or Call, depending on what you answer when diio asks. The channel is always WhatsApp; the type is what you define.

When diio syncs a conversation to the CRM, the type determines which object is created:

Call and Meeting

Message