# Third-Party Channels

Your users already have a preferred messaging app. Third-party channel deployments let your agent meet them there, inside WhatsApp, Viber, Slack, Microsoft Teams, Facebook Messenger, Instagram, or Unity.

Each channel connects through its own set of credentials (API tokens, app IDs, secrets) that you configure once during deployment setup. After that, conversations flow through the platform just like Webchat.

### Available Channels

| Channel            | Credentials Needed                                     | Start Workflow           | Layout Settings       |
| ------------------ | ------------------------------------------------------ | ------------------------ | --------------------- |
| Microsoft Teams    | Client ID, Client Secret, Tenant ID, Service URL       | :x: No                   | Hide Typing Indicator |
| Viber              | Authentication Token                                   | :white\_check\_mark: Yes | Agent Avatar          |
| Facebook Messenger | Page Access Token, Page ID                             | :white\_check\_mark: Yes | Hide Typing Indicator |
| Unity              | Auto-generated API Token                               | :x: No                   | None                  |
| Slack              | App ID, Client ID, Client Secret, Team ID, OAuth Token | :x: No                   | None                  |
| Instagram          | Page Access Token, Page ID                             | :x: No                   | None                  |
| WhatsApp           | Access Token, Phone Number ID                          | :x: No                   | Hide Typing Indicator |

{% hint style="info" %}
**Start Workflow** indicates whether the channel supports a welcome workflow that triggers before the user sends their first message.
{% endhint %}

### Creating a Third-Party Deployment

All third-party channel deployments follow the same creation flow.

{% stepper %}
{% step %}

#### Open the Deployments Page

Go to **Designer > Deployments**.
{% endstep %}

{% step %}

#### Select a Channel

Click the channel icon in the toolbar at the top of the deployments tab. Each channel has a distinct branded icon (e.g., <i class="fa-whatsapp">:whatsapp:</i> for WhatsApp, <i class="fa-viber">:viber:</i> for Viber).
{% endstep %}

{% step %}

#### Fill in General Settings

Every deployment shares fields such as the name, description and language. You can also choose to automatically detect and match the user's language. Only the name is required and serves as an internal identifier.
{% endstep %}

{% step %}

#### Enter Application Settings

Paste the channel-specific credentials (tokens, IDs, secrets) from the provider's portal.&#x20;
{% endstep %}

{% step %}

#### Configure Layout Settings (If Available)

Some channels offer a **Layout Settings** tab with options like hiding the typing indicator or setting an agent avatar. Skip this step if the channel has no layout options.
{% endstep %}

{% step %}

#### Save the Deployment

Click **Create Deployment**. Your agent is now live on the selected channel.
{% endstep %}
{% endstepper %}

### Managing Deployments

Once created, all third-party deployments are managed from the same table at **Designer > Deployments**.

* **Edit:** Click any deployment row to reopen its configuration dialog, then click **Save Changes**
* **Clone:** Click the **copy** icon in the **Actions** column to duplicate a deployment with identical settings
* **Delete:** Open the deployment, scroll to the bottom of **General Settings**, and click **Delete this Deployment**

{% hint style="danger" %}
**Permanent Action** Deleting a deployment disconnects your agent from the channel immediately. This cannot be undone.
{% endhint %}

### Best Practices

* **Name deployments descriptively:** Use names like `WhatsApp Support - EN` or `Slack Sales - DE` so you can identify them at a glance in the deployments table
* **Match the channel to the audience:** Deploy to WhatsApp or Viber for consumer-facing support, and Slack or Microsoft Teams for internal teams
* **Reuse Meta credentials wisely:** Keep one Facebook App with all messaging permissions rather than creating separate apps per channel
* **Monitor after launch:** Check Observatory after deploying to a new channel to verify conversations are flowing correctly

{% hint style="success" %}
You now know which third-party channels are available and how to create and manage a deployment on any of them.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helvia.ai/deploy/third-party-channels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.