Channels

Beyond the first-party Alfe apps, an agent can meet people where they already talk. A channel is a messaging platform an agent connects to so it can receive messages and reply — in a Slack workspace, a Discord server, over SMS, on a phone call, and more.

Supported channels

Channel	What it does
Slack	The agent joins Slack workspaces and responds in channels and DMs.
Discord	The agent joins Discord servers and responds in text and voice channels.
Microsoft Teams	The agent participates in Teams as a bot.
Google Chat	The agent receives and responds to Google Chat messages.
SMS	The agent gets a phone number and exchanges text messages.
WhatsApp	The agent sends and receives WhatsApp messages on its number.
Voice	Inbound and outbound phone calls, with speech in and speech out.

Whichever channel a message arrives on, it reaches the same agent — with the same memory and the same abilities — so a conversation that starts in Slack and one that starts on the dashboard are both handled by the one agent you configured.

Each agent has its own identity

A defining principle on Alfe is per-agent identity. When an agent connects a channel like Slack or Discord, it does so as its own bot, with its own credentials — never a shared, global bot. That means:

• Each agent shows up under its own name and avatar in the workspace or server it joins.
• Channels aren’t shared between agents — every agent connects its own.
• Removing or reconfiguring one agent’s channel doesn’t affect any other agent.

Phone-based channels work off a phone number the agent provisions; WhatsApp layers on top of that same number.

Connecting a channel

Channels are set up the same way as other integrations. You can connect them:

• From the dashboard at app.alfe.ai, on the agent you want to give reach.
• From the CLI with alfe integration.
• From the agent itself, over MCP or the Agent API, so an agent can connect its own channels.

For the full list of channels and apps, and how connect flows work, see the Integrations overview.