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

# iMessage

> Blue-bubble follow-up with booking cards, tapbacks, and read receipts. iMessage sees 3–4× higher engagement than SMS.

iMessage sees **3–4× higher engagement than SMS** (industry benchmark). The same reminder that dies as a green bubble gets read — and answered — as a blue one. RevDesk sends confirmations, reminders, and follow-ups over iMessage where it's available, and falls back to WhatsApp or SMS automatically where it isn't. Replies route into the same RevDesk contact record as every other channel.

## What changes

* **Blue-bubble trust.** Messages arrive in the customer's native thread with your business name — not a shortcode.
* **Rich, native content.** Booking cards, rich links, and images render the way Apple designed them.
* **Read receipts and typing indicators.** You see when a customer has read the reminder; customers see the agent composing.
* **Tapbacks count.** A 👍 on a confirmation registers as a confirm — no reply required.
* **Suppression synced.** An opt-out on iMessage suppresses every channel, and vice versa.

## Setup

<Steps>
  <Step title="Open the integrations panel">
    Inside the app: **Settings → Integrations → Messaging**.
  </Step>

  <Step title="Enable iMessage">
    Register your business for iMessage delivery. Your existing RevDesk number stays the sender identity.
  </Step>

  <Step title="Verify your brand">
    Business name and logo are verified before messages carry your identity.
  </Step>

  <Step title="Pick your fallback">
    Choose the fallback order for contacts without iMessage — WhatsApp first or straight to SMS.
  </Step>
</Steps>

## Standard flows

| Scenario         | Behavior                                                                             |
| ---------------- | ------------------------------------------------------------------------------------ |
| Confirmation     | Booking card with time, location, and a reschedule action, sent right after booking. |
| 24-hour reminder | "Your appointment is tomorrow at 2pm." — a tapback 👍 confirms.                      |
| 1-hour reminder  | "Your appointment starts in 1 hour."                                                 |
| Follow-up        | Review request with a direct link.                                                   |
| Fallback         | Contacts without iMessage get the same flow via WhatsApp or SMS automatically.       |

## Two-way replies

Customer replies open a live conversation with the agent — questions answered, reschedules handled, and escalation to your team when intent spikes. The full thread, across every channel, stays on one contact timeline.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Message delivered as SMS instead of iMessage">
    The contact's number isn't registered with iMessage, or they've disabled it. The fallback chain handled delivery — no action needed.
  </Accordion>

  <Accordion title="Business name not showing">
    Brand verification is still in review. Messages send from your number in the meantime.
  </Accordion>

  <Accordion title="Customer stopped receiving messages">
    Check the contact's timeline for an opt-out event — a STOP on any channel suppresses iMessage too.
  </Accordion>
</AccordionGroup>

<Card title="Enable iMessage" icon="comment" href="https://www.revdesk.com/settings/integrations">
  Five-minute setup. For international reach, pair it with [WhatsApp](/integrations/messaging/whatsapp).
</Card>