The conversation channel is how diio classifies each interaction it analyzes. When you finish a meeting, a call or a message thread and diio processes it, the result appears in your list under one of three channels: Meeting, Call or Message. It's also the "Channel" filter in All conversations. This classification matters because it determines how the analysis is displayed, which fields are available and how the activity is logged in your CRM.
The three channels
Meeting
A Meeting is a synchronous encounter with two or more people, whether remote or in person. It applies to:
Video calls in Zoom, Google Meet or Microsoft Teams.
In-person meetings whose audio was uploaded to diio via WhatsApp.
Meetings show the full transcript with voice attribution, the executive summary, commitments grouped by owner, the playbook fields and the Success prediction.
Call
A Call is a voice conversation between two people, typically shorter than a meeting. It applies to:
Calls made from HubSpot Call, Aircall or CloudTalk.
Phone audio uploaded to diio that the user classified as a call.
The analysis is identical to a Meeting's, but the activity is logged in the CRM as a Call (not as a Meeting), which can affect any automation flows you have set up.
Message
A Message is a written thread with one or more people. It applies to:
WhatsApp conversations captured by the Chrome plugin.
LinkedIn messages captured by the Chrome plugin.
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 assesses the overall mood of the thread.
Channel vs. platform: the key distinction
The channel is how the conversation ends up classified: Meeting, Call or Message.
The platform is the specific system it came in through: Zoom, Google Meet, Microsoft Teams, HubSpot Call, Aircall, CloudTalk, WhatsApp Web, LinkedIn or Intercom.
Put another way: the channel is Call, and the platform behind it might be Aircall.
For example: audio uploaded via WhatsApp can end up as a Meeting or a Call, depending on what you answer when diio asks. The platform is always WhatsApp; the channel is up to you.
Don't confuse it with the conversation type
The conversation type is something else: it describes the nature of what was discussed (Discovery, Sales Presentation, Sales Follow-up, Negotiation) and belongs to how playbooks are organized.
A single conversation has all three at once. For example: a Negotiation (type) that happened as a Meeting (channel) in Google Meet (platform).
Why the channel affects the CRM
When diio syncs a conversation to the CRM, the channel determines which object is created:
Call and Meeting → logged as an Activity in HubSpot, Salesforce and equivalents.
Message → logged as a Transcript.