> ## 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

> Configure supported customer messaging channels and keep conversations, consent, and handoffs attached to the right contact.

RevDesk can continue customer work across supported voice and messaging channels. Availability depends on the
workspace, country, sender, recipient capability, consent, and enabled integrations. Team notifications such
as Slack are separate from customer messaging.

## Why channel choice matters

Choose a channel based on customer preference, recipient capability, the purpose of the message, and the
consent attached to the contact. Do not assume that an available phone number is eligible for every channel.

## 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 when the integration is enabled |
| Slack | — | Cards, threads | — | Internal notifications and escalation |

## One contact timeline

* **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.
* **Channel-aware delivery.** A workflow may select or fall back between channels only when the sender,
  recipient, account, and consent state support it.
* **Team handoff.** When a person should take over, the conversation remains visible in the inbox and may
  notify an enabled team integration.

## Compliance, synced

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

* A phone opt-out stops calls, SMS, and iMessage to that number. Email and WhatsApp opt-outs apply to that
  channel.
* Broadcasts respect TCPA calling windows and per-state rulebooks.
* WhatsApp and iMessage business messaging follow each platform's template and policy rules. RevDesk submits WhatsApp templates; Meta approves them. iMessage uses a line set up for your workspace.

## 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="Slack" icon="slack" href="/integrations/messaging/slack">
    Escalations and daily digests where your team lives.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.