# Owner channels (WhatsApp, Email, Telegram)

**Status:** Connect script implemented.

- MVP owner ↔ assistant channels: **WhatsApp, Email, Telegram**.
- Configured via **NemoClaw Hermes channel commands** (`nemohermes … channels add`, rebuild when required).
- Allowlists for who may talk to the bot.
- Owner never configures via host shell recipes in chat.

## Connect procedure

```bash
# Preview all channels (default)
./scripts/connect.sh channels --dry-run

# Connect a specific channel
./scripts/connect.sh channels --target whatsapp --apply
./scripts/connect.sh channels --target telegram --apply
./scripts/connect.sh channels --target email --apply

# Connect all channels
./scripts/connect.sh channels --apply
```

### What the script does

1. **Dry-run:** Shows steps for each channel without executing.
2. **Apply:**
   - Prompts for channel-specific credentials.
   - Calls `nemohermes <sandbox> channels add <channel>` with credentials.
   - Records status in `.local/capability_state.json`.

### Channel-specific requirements

| Channel | Owner steps | Operator credentials |
|---------|-------------|---------------------|
| **WhatsApp** | Set up WhatsApp Business API in Meta developer console | Phone Number ID, Verify Token |
| **Email** | Provide email address for the assistant | Email address |
| **Telegram** | Create a bot via @BotFather on Telegram | Bot Token |

### Owner steps (browser only)

- **WhatsApp:** Set up WhatsApp Business API in the Meta developer console.
- **Email:** Provide the email address the assistant will respond to.
- **Telegram:** Create a bot via @BotFather on Telegram; BotFather returns a Bot Token.

See [design/use-cases.md](../../design/use-cases.md) family C · [docs/SETUP_UX.md](../SETUP_UX.md).