> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alcmeon.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Messaging channels in Simio: availability and setup

> Explore which messaging channels Simio supports, what behaves the same on every channel, and what each channel defines on its own, from connection flow to billing.

Simio keeps its product surface (campaigns, automations, chatbots, conversations inbox, contacts, analytics, integrations) separate from the messaging channel you use to reach a contact. What differs per channel is how you connect an account, the message formats and approval rules of the channel, opt-in requirements, and the channel's own billing model.

This page lists the channels available in Simio. Each available channel has its own sub-section under **Channels** with its connection flow, message specs, opt-in rules, and quality/billing information.

## Channel availability

| Channel | Status | Where to start |
| - | - | - |
| WhatsApp | Available | [WhatsApp overview](/simio/channels/whatsapp/overview) |

## What stays the same across channels

These pieces of Simio behave the same way regardless of the channel:

* **Campaigns**, **automations**, and **chatbots** are built in the same visual flow editor, with the same step types (Message, Wait, Condition, Action, AI, Opt-in/out).
* The **conversations inbox** aggregates threads from every connected account in a single view.
* **Contacts and segments** are stored once per company.
* **Consent** is tracked **per channel and per messaging account** on each contact. See [Consent and opt-in status](/simio/platform/contacts/consent).
* **Analytics** aggregate delivery, open, and click metrics, with filters to drill into a single connected account.
* **Integrations** (Brevo, Batch, Splunk) trigger flows independently of the channel the flow uses.
* **Helpdesk connectors** ([Crisp](/simio/integrations/crisp), [Easiware](/simio/integrations/easiware), [Gorgias](/simio/integrations/gorgias)) let your support team reply to contacts from the helpdesk they already use.

## What each channel defines

Each channel documents its own specifics:

* **Connection flow**: how you link an account (for example, a WhatsApp Business number pairs through Alcmeon).
* **Message formats**: what a "template" or rich message looks like on that channel, what the approval process is, and what limits apply (character counts, media size, buttons, carousels).
* **Opt-in rules**: the legal and platform requirements to contact a user on that channel.
* **Conversation billing**: how the channel charges for messages sent (for example, WhatsApp bills per 24-hour conversation window).
* **Account quality**: quality ratings, sending tiers, and restrictions the channel enforces.

## Next steps

<CardGroup cols={2}>
  <Card title="WhatsApp overview" icon="message-circle" href="/simio/channels/whatsapp/overview">
    Read how WhatsApp works in Simio.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.