> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Messaging

> Connect customer and workplace messaging to a Voiceflow agent through verified platform events and text replies.

Connect a Voiceflow agent to the messaging destination your customers or team already use. These manuals teach developer-hosted text relays: the platform delivers an authenticated event, the relay selects an isolated Voiceflow session, and its text reply returns to the same destination.

A bot token, integration listing or Send Message action supplies only part of that path. Each installation guide includes its account setup, incoming registration, reply mapping, customer test and release requirements. The examples are single-process starting points with persistent state; your team operates the host, secrets and recovery.

## Choose a starting point

1. [Build an agent](/docs/documentation/build/overview), give it a known support answer and publish a reviewed [Environment](/docs/documentation/deploy/environments/publishing).
2. Choose an installation guide below. Obtain the required app/account access before hosting its relay.
3. Test a real question and follow-up through that platform. A saved webhook or Voiceflow Run alone does not prove the connection. Verify the production route again after platform approval and release.

**Note:** 

**Implementation scope:** The downloads implement text support through the stated provider/API. Apple requires an approved Messaging Service Provider and a tested human escalation path. WeChat uses Sinch’s verified Service Account integration. Discord uses explicit `/ask` commands. The manuals do not claim a managed Voiceflow connector or a second Studio installation path.

## Installation guides

| Platform | Completed walkthrough | Starting requirement |
| --- | --- | --- |
| [WhatsApp](/docs/guides/channels/messaging/whatsapp) | WhatsApp Cloud API | WhatsApp business/test sender. |
| [Facebook Messenger](/docs/guides/channels/messaging/facebook-messenger) | Messenger Platform for a Facebook Page | Facebook Page and app access. |
| [Instagram](/docs/guides/channels/messaging/instagram) | Instagram Messaging with Facebook Login | Professional account linked to a Facebook Page. |
| [Telegram](/docs/guides/channels/messaging/telegram) | Telegram Bot API webhooks | BotFather bot and a customer-initiated chat. |
| [WeChat](/docs/guides/channels/messaging/wechat) | WeChat through Sinch Conversation API | Verified Service Account and Sinch app. |
| [LINE](/docs/guides/channels/messaging/line) | LINE Official Account Messaging API | Official Account with Messaging API. |
| [Viber](/docs/guides/channels/messaging/viber) | Rakuten Viber Bot API | Commercially provisioned Viber bot. |
| [Slack](/docs/guides/channels/messaging/slack) | Slack Events API over HTTP | Approved single-workspace app installation. |
| [Microsoft Teams](/docs/guides/channels/messaging/microsoft-teams) | Microsoft Teams SDK personal bot | Single-tenant bot and personal app installation. |
| [Discord](/docs/guides/channels/messaging/discord) | Discord HTTP interactions | Installed application and `/ask` command. |
| [Apple Messages for Business](/docs/guides/channels/messaging/apple-messages-for-business) | Apple Messages for Business through Sunshine Conversations | Apple/MSP approval and Agent Workspace. |
| [RCS for Business](/docs/guides/channels/messaging/rcs-for-business) | Google RCS for Business partner APIs | Partner agent and accepted test device. |

## Guides

- **[Separate customer conversations](/docs/guides/channels/messaging/separate-conversations)** — Preserve follow-ups without sharing memory between customers.
- **[Pass trusted customer context](/docs/guides/channels/messaging/pass-customer-context)** — Inject verified service context and keep business authorization on your backend.
- **[Adapt agent replies](/docs/guides/channels/messaging/adapt-agent-replies)** — Deliver usable text and handle unsupported interactions explicitly.
- **[Pause automated replies](/docs/guides/channels/messaging/pause-automated-replies)** — Assign a person without competing automated responses.
- **[Recover failed messages](/docs/guides/channels/messaging/recover-failed-messages)** — Reconcile retries, uncertain execution and delivery failures.

## Existing documentation

- **[Chat agents](/docs/api-reference/agent-runtime/chat)** — exact session, action and trace contracts for your relay.
- **[SMS](/docs/guides/channels/sms)** — telephone text-message deployment and its provider-specific constraints.
- **[Human agent hand-off](/docs/documentation/handoff/overview)** — configure supported human-support integrations; a generic Messaging relay does not automatically inherit them.
- **[Transcripts](/docs/documentation/measure/transcripts)** — inspect the agent’s exchange alongside provider delivery records.
