Core channels
Telegram, Discord, Slack, Signal, iMessage, WhatsApp Web, and web chat in core runtime.
Channel strategy and rollout guide
Resonix-AG supports multi-channel communication through core channels plus extension-based channels. Build rollout plans in layers rather than enabling every channel at once.
Channel model
Extension channels
Teams, Matrix, Zalo, and additional connectors via extension packages.
Routing layer
Centralized route and allowlist control across channel boundaries.
Operational controls
Probe-based status checks and command gating for safe production operations.
Recommended rollout order
- Start with web chat or one low-risk channel for smoke testing.
- Add one team channel (Slack/Discord/Telegram) with strict allowlists.
- Enable business-critical channels only after route and audit checks pass.
- Scale to extension channels with separate monitoring and fallback routing.
Operations checklist
- Define per-channel credentials and ownership boundaries.
- Use `resonix channels status --probe` in health checks.
- Keep command allowlists narrow, especially on public channels.
- Audit route behavior when adding new channels or plugins.
resonix channels status --probe
resonix gateway start
resonix --helpNext docs to read
Install methods
Align channel rollout with your deployment path.
Getting started flow
Validate baseline runtime before enabling more channels.