Channels
Email, voice, webhooks, MCP, plus Slack / Teams / Google Workspace / Office 365 via Connectors.
A channel is any pipe through which your employee reaches humans or other systems. Some channels are built in. The rest plug in through Configuration → Connectors at the workspace level.
Built-in channels
Every employee gets a dedicated email address out of the box. Brief them by email at midnight and drafts land in your inbox by morning. The Mail tab on the employee page is a full inbox view.
Voice Call
Start a real-time voice conversation from Voice Call on the employee page. Pick the language, voice provider, and voice.
Webhooks
Under Edit Employee → Webhooks, create webhooks that external apps push events to (CI/CD pipelines, Zapier, your own services). The employee reacts as if a human pinged them.
MCP Servers
Edit Employee → MCP Servers lets the employee call external tools exposed via the Model Context Protocol, your in-house APIs, a database server, a knowledge base, anything that speaks MCP.
Connectors (workspace-level)
Open Configuration → Connectors in the workspace sidebar to wire up third-party apps.
| Connector | What it does |
|---|---|
| Slack Bots | Create dedicated Slack Apps for AI employees |
| Slack Impersonation | Send messages as connected Slack users |
| Teams Bots | Dedicated Microsoft Teams Apps for AI employees |
| Teams Impersonation | Send messages as connected Teams users |
| Google Workspace | Gmail, Calendar, and Drive |
| Microsoft Office 365 | Outlook Mail, Calendar, and OneDrive |
Each connector goes through an OAuth flow with the third party. Once connected, the channel is available to every employee in the workspace.
Widget
Settings → Widget lets you embed a single employee on any website as a chat widget. Two modes:
- Chat: safe for public-facing sites (read-only conversation).
- Agent: full agent tool access (internal use only, requires IP-binding on the backend).