> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemoclaw/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemoclaw/_mcp/server.

# Choose Messaging Channels

> Compare the supported Telegram, Discord, Slack, WeChat, WhatsApp, and Microsoft Teams messaging paths.

NemoClaw supports Telegram, Discord, Slack, WeChat, WhatsApp, and Microsoft Teams for OpenClaw and Hermes sandboxes.
OpenShell-managed processes and gateway resources carry channel traffic.

For token-based channels, NemoClaw registers credentials with OpenShell providers.
WeChat uses a host-side QR scan during onboarding to capture a token.

WhatsApp pairs inside the sandbox through a QR scan and intentionally stores mutable session state there.
Microsoft Teams uses Bot Framework credentials plus a public HTTPS webhook that forwards to the sandbox.

NemoClaw writes the selected channel configuration into the sandbox image and keeps runtime delivery under OpenShell control.

WeChat, WhatsApp, and Microsoft Teams are experimental.
WeChat and WhatsApp rely on QR-based pairing flows that are more fragile than token-based bots.

Microsoft Teams requires an externally reachable webhook path that depends on your host networking setup.
Interfaces, defaults, and supported features can change, and NVIDIA does not recommend these channels for production use.

## Compare Channel Requirements

| Channel         | Required credentials or pairing                               | Optional settings                                             | Setup guide                                      |
| --------------- | ------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------ |
| Telegram        | `TELEGRAM_BOT_TOKEN`                                          | DM allowlist, group policy, mention mode                      | [Set Up Telegram](set-up-telegram)               |
| Discord         | `DISCORD_BOT_TOKEN`                                           | Server ID, user ID, mention mode                              | [Set Up Discord](set-up-discord)                 |
| Slack           | `SLACK_BOT_TOKEN`, `SLACK_APP_TOKEN`                          | User and channel allowlists                                   | [Set Up Slack](set-up-slack)                     |
| WeChat          | Host-side QR scan                                             | DM allowlist                                                  | [Set Up WeChat](set-up-wechat)                   |
| WhatsApp        | In-sandbox QR pairing                                         | Hermes sender allowlist and non-interactive channel selection | [Set Up WhatsApp](set-up-whatsapp)               |
| Microsoft Teams | `MSTEAMS_APP_ID`, `MSTEAMS_APP_PASSWORD`, `MSTEAMS_TENANT_ID` | User allowlist, webhook port, mention mode                    | [Set Up Microsoft Teams](set-up-microsoft-teams) |

## Prepare the Host and Policy

* Use a machine where you can run `nemohermes onboard`.
* Prepare the token, app credentials, or paired phone required by each selected channel.
* Select the matching network policy preset or equivalent custom egress rules for each channel.
* Confirm Docker is running and your user can access the Docker socket through the `docker` group or the documented `sudo` workflow.

Use host-side `nemohermes <sandbox> channels` commands.
Do not mutate messaging configuration directly inside the sandbox because NemoClaw generates `/sandbox/.hermes/.env` and Hermes config at image build time, and changes inside the running container do not persist across rebuilds.

`nemohermes tunnel start` does not start chat bridges.
It starts optional host services such as a cloudflared tunnel when that binary is present.
Refer to [Run Sandboxes](../operate-sandboxes/run-sandboxes) for tunnel management.

## Next Steps

* [Enable Channels During Onboarding](enable-channels-during-onboarding) for a new sandbox.
* [Add Channels After Onboarding](add-channels-after-onboarding) for an existing sandbox.
* [Manage Messaging Channels](manage-messaging-channels) to rotate, pause, resume, or remove a channel.