Channels
Last reviewed: 2026-03-18
Owner: Support engineering
Source of truth:
https://dawnhq.ai/docs/channels
https://dawnhq.ai/docs/channels/slack
https://dawnhq.ai/docs/channels/teams
https://dawnhq.ai/docs/channels/telegram
https://dawnhq.ai/docs/channels/discord
https://dawnhq.ai/docs/channels/web-widget
https://dawnhq.ai/docs/channels/generic-webhook
Applies to: channel setup and troubleshooting
Refresh cadence: monthly
Facts
- Supported channels in docs: Slack, Microsoft Teams, Telegram, Discord, Web Widget, Generic Webhook.
- Channel setup pattern is now split for Slack, Discord, and Teams: workspace owner connects the workspace app first, then users create channel bindings, choose trigger/context behavior, attach bindings to agent profiles, and validate.
- Slack docs position Dawn as a bound-channel tool; App Home direct-message behavior is not the intended default setup.
- Slack and Discord docs call out the extra message permissions and events needed for recent-discussion context.
- Telegram docs now call out BotFather privacy mode as the key requirement for group discussion context.
- Discord and Teams setups rely on binding the intended server/channel or conversation target correctly.
- Teams docs position ambient context as strongest in direct chats and mention-driven flows, not as a full passive history backfill feature.
- For web widget, docs require allowed origins and recommend not leaving origin list empty.
- Generic webhook docs also require an explicit origin strategy and callback/signature setup.
- Public docs consistently say Dawn does not backfill older provider history it never received earlier.
- Telegram webhooks are token-level; last webhook configuration wins for a reused token.
FAQ snippets
- Why no replies in channel? Confirm binding is attached to active agent profile and credentials/scopes are valid.
- Why is Dawn not using the surrounding conversation? Check the binding context mode and the channel-specific permissions needed for Dawn to receive those messages.
- Why does Slack DM/App Home behavior not work? Dawn is intended for bound-channel operation; check the Slack binding setup and keep App Home
Messages disabled unless deliberately implementing that flow.
- Can one agent serve many channels? Yes, Dawn positioning and docs describe one profile used across channels.
- Web widget loaded but no responses? Check origin policy and channel binding to active profile.
Escalation trigger
- Inbound events are not reaching Dawn after credential, webhook, and binding validation.