Channels normalize customer messages into organization-scoped contacts, conversations, and messages. Once normalized, the same inbox, AI pipeline, tickets, routing, analytics, and human-handoff behavior can serve every source.
Channel
Inbound transport
Outbound transport
Identity key
Web widget
HTTPS + Socket.IO
Socket.IO
Stable/ephemeral visitor session
Email
AWS SES/SNS webhook
Configured email adapter
Sender address/thread metadata
WhatsApp
Twilio webhook
Twilio Messages API
whatsapp-<phone> session
Telegram
Telegram webhook
Bot API
telegram-<chatId> session
QR/direct link
Hosted /c/:publicKey page
Widget transport
Widget visitor session plus source attribution
Web widget
Iframe-isolated chat with configurable appearance, visibility, AI, and visitor fields.
Email
Domain-verified support addresses and inbound/outbound email.
WhatsApp
Twilio-backed WhatsApp messages with signed inbound webhooks.
Telegram
Bot token verification, webhook registration, and chat mapping.
Administrators manage channels; agents consume the resulting conversations. One organization can have one saved channel per type under the current unique index.
Webhook routes are public by necessity. Treat provider signature verification, HTTPS, secret rotation, replay/idempotency controls, and minimal error responses as mandatory production controls.