Skip to main content
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

​
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

iMessage

Blue-bubble follow-up with booking cards and read receipts.

WhatsApp

WhatsApp Business templates and two-way replies.

SMS

Registered 10DLC texting with compliance keywords.

Email

Confirmations, recaps, and email-to-call triggers.

Telegram

Customer conversations on Telegram.

Slack

Escalations and daily digests where your team lives.