> ## Documentation Index
> Fetch the complete documentation index at: https://help.iteam.works/llms.txt
> Use this file to discover all available pages before exploring further.

# Channels (WhatsApp, Telegram, Slack)

> Put your agent where your customers already are — with iTeam handling the boring parts of the setup

A **channel** is your agent's door to the real world: the company WhatsApp number, a Telegram bot,
your Slack workspace. Configure it once and the agent starts receiving and answering messages
there — with the same intelligence, knowledge and security as everywhere else.

Channels live in **Agents → (your agent) → Channels tab**.

## Official WhatsApp (Meta API)

The most used channel — and the only one that needs a bit of setup on Meta's side. iTeam automates
everything it can: it generates the verify token, keeps the webhook URL stable and, if you provide
the **WABA ID**, it subscribes the app to your WhatsApp Business account by itself.

<Steps>
  <Step title="Create the channel">
    In the **Channels** tab, click **New Channel**, pick **WhatsApp (Official API)** and name it.
  </Step>

  <Step title="Fill in the Meta credentials">
    * **Phone Number ID** — in *App Dashboard → WhatsApp → API Setup*.
    * **Access Token** — the access token (preferably a long-lived or System User token).
    * **Verify Token** — iTeam **generates one for you**; just copy it.
    * **WABA ID** *(recommended)* — your WhatsApp Business Account ID, in
      *WhatsApp Manager → Account settings*.
  </Step>

  <Step title="Register the webhook in Meta">
    Copy the **webhook URL** iTeam shows on the channel and paste it in
    *App Dashboard → WhatsApp → Configuration → Callback URL*, together with the Verify Token.
    Click **Verify and save** — verification passes instantly.
  </Step>

  <Step title="Subscribe to the messages field">
    Still in the webhook configuration, under **Webhook fields**, click *Manage* and subscribe to
    the **messages** field. Without it Meta accepts the URL but never sends the conversations.
  </Step>
</Steps>

<Tip>
  **Why provide the WABA ID?** There is an invisible step that breaks most setups: Meta's app must
  be **subscribed** to your WhatsApp Business Account (WABA). Without that subscription, Meta's
  panel shows the webhook as verified, iTeam shows "Active"… and **no message ever arrives**, with
  no error anywhere. With the WABA ID filled in, iTeam performs that subscription automatically
  when you save the channel and shows the outcome on screen ("app subscribed to the WABA ✓").
  It's optional — but it removes the #1 cause of "I configured everything and it doesn't work".
</Tip>

<Warning>
  If the channel shows "Active" but messages don't arrive, check in this order:
  is the **WABA ID** filled in and showing "✓ subscribed"? Is the **messages** field subscribed in
  Webhook fields? Has the **Access Token** expired?
</Warning>

## WhatsApp via QR Code

For quick tests or a personal number: scan the QR code like WhatsApp Web and you're done — no Meta
account needed. Great for pilots; for production, prefer the Official API.

## Telegram

Create a bot with [@BotFather](https://t.me/BotFather), paste the **Bot Token** into the channel
and iTeam registers the webhook by itself. The fastest channel to set up.

## Slack

Create a Slack app, provide the **Bot Token** and **Signing Secret**, and register the webhook URL
iTeam generates. The agent replies in channels and DMs, with progress narration.

## Good practices

* **Narration** — per channel you choose whether the agent narrates what it's doing ("let me
  check…") or answers with the result only. Inherits from the agent by default.
* **One channel, one owner agent** — a channel belongs to one agent, who answers on it. Other
  agents can join as members.
* **Security** — tokens are stored encrypted; the webhook URL carries its own secret and does not
  change when you edit the channel (editing the token never breaks the integration).