Channel availability
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.
- 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, Easiware, 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.