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

# Messaging channels

> One agent across iMessage, WhatsApp, SMS, email, and more — every conversation in one thread, with consent and opt-outs synced everywhere.

RevDesk runs your follow-up on the app your customers actually answer. Voice, iMessage, WhatsApp, SMS, and email are first-class channels; Telegram, Instagram, Slack, and Discord extend the same agent to community and team surfaces. Whatever the channel, everything writes to one contact record — the agent never loses the thread.

## Why channel choice matters

iMessage sees **3–4× higher engagement than SMS** (industry benchmark, open + reply rates). A reminder that gets ignored as a green bubble gets answered as a blue one. RevDesk picks the best available channel for each contact and falls back automatically — iMessage where it's available, WhatsApp or SMS where it isn't.

## Channel capabilities

| Channel         | Two-way | Rich content                           | Broadcast templates | Typical use                               |
| --------------- | ------- | -------------------------------------- | ------------------- | ----------------------------------------- |
| iMessage        | ✓       | Booking cards, tapbacks, read receipts | ✓                   | Follow-up, reminders, confirmations       |
| WhatsApp        | ✓       | Templates, media, one-tap replies      | ✓                   | International + high-engagement follow-up |
| SMS             | ✓       | Links, keywords                        | ✓                   | Universal fallback, compliance keywords   |
| Email           | ✓       | Full HTML, attachments                 | ✓                   | Recaps, documents, email-to-call triggers |
| Telegram        | ✓       | Media, buttons                         | —                   | Customer conversations                    |
| Instagram       | ✓       | DMs, story replies                     | —                   | Inbound social leads                      |
| Slack / Discord | ✓       | Cards, threads                         | —                   | Team escalation + community               |

## One thread, every channel

* **Same memory.** A voice call, an iMessage reply, and an email open all land on the same contact timeline. The agent carries full context across channels.
* **Smart channel selection.** Business-initiated sends ride the highest-engagement channel available for that contact, with automatic fallback.
* **Team handoff.** When intent spikes, the conversation escalates to your team — in the inbox, or in Slack/Discord.

## Compliance, synced

Consent, quiet hours, and opt-outs are enforced per contact, across channels:

* A **STOP** on any channel suppresses every channel.
* Broadcasts respect TCPA calling windows and per-state rulebooks.
* WhatsApp and iMessage business messaging follow each platform's template and policy rules — RevDesk handles submission and approval.

## Set up your channels

<CardGroup cols={2}>
  <Card title="iMessage" icon="comment" href="/integrations/messaging/imessage">
    Blue-bubble follow-up with booking cards and read receipts.
  </Card>

  <Card title="WhatsApp" icon="whatsapp" href="/integrations/messaging/whatsapp">
    WhatsApp Business templates and two-way replies.
  </Card>

  <Card title="SMS" icon="message-sms" href="/getting-started/features/sms">
    Registered 10DLC texting with compliance keywords.
  </Card>

  <Card title="Email" icon="envelope" href="/integrations/messaging/email">
    Confirmations, recaps, and email-to-call triggers.
  </Card>

  <Card title="Telegram" icon="paper-plane" href="/integrations/messaging/telegram">
    Customer conversations on Telegram.
  </Card>

  <Card title="Instagram" icon="instagram" href="/integrations/messaging/instagram">
    Answer DMs and story replies automatically.
  </Card>

  <Card title="Slack" icon="slack" href="/integrations/messaging/slack">
    Escalations and daily digests where your team lives.
  </Card>

  <Card title="Discord" icon="discord" href="/integrations/messaging/discord">
    Community questions and team alerts.
  </Card>
</CardGroup>