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

> Configure supported iMessage conversations, sender identity, replies, consent, and troubleshooting.

iMessage is available as a limited Photon-powered pilot for the RevDesk workspace. It supports manual,
two-way text conversations in the Inbox. Replies attach to the corresponding RevDesk contact and conversation.

## What changes

* **Photon-owned sender.** The pilot uses the iMessage address assigned by Photon; it is separate from
  your RevDesk/Telnyx SMS number.
* **Manual text conversations.** Team members can send and receive plain-text iMessages from the Inbox.
* **One shared timeline.** Inbound and outbound iMessages appear on the associated contact.
* **Consent-aware sending.** Opt-outs update the contact's applicable channel permissions and block later
  actions that are no longer allowed.

## Setup

<Steps>
  <Step title="Ask RevDesk to enable the pilot">
    Photon setup is managed by a RevDesk platform administrator during the pilot.
  </Step>

  <Step title="Assign the Photon project and sender">
    The administrator binds one Photon project and one active Photon-owned iMessage sender to the workspace.
  </Step>

  <Step title="Verify a two-way test">
    Send a manual Inbox message, reply from the recipient, and confirm both messages appear on the same
    contact.
  </Step>
</Steps>

## Standard flows

| Scenario | Pilot behavior |
| - | - |
| Manual Inbox reply | Queued and sent through the workspace's Photon sender. |
| Customer text reply | Verified, deduplicated, and written to the same contact conversation. |
| Unknown phone number | Creates an organization-scoped contact for the inbound conversation. |
| Job or automated send | Blocked during the pilot. |
| Delivery failure | Shown as an iMessage failure; never silently retried as SMS. |

## Two-way replies

Customer replies open a conversation with the configured owner when one is assigned. STOP suppresses
phone messaging and iMessage; START records iMessage consent. Attachments, tapbacks, typing indicators,
read receipts, and automated replies are outside the pilot.

## Troubleshooting

<AccordionGroup>
  <Accordion title="iMessage failed instead of sending an SMS">
    This is intentional. RevDesk does not silently change the sender identity, compliance rules, or channel.
    Send an SMS separately only after reviewing consent and choosing an SMS sender.
  </Accordion>

  <Accordion title="iMessage shows a warning for one contact">
    The last iMessage to this contact failed because the number can't receive iMessage (for example, an
    Android phone). The channel picker shows a warning, but iMessage stays available, so you can try again or
    send a text instead. The warning clears after a message gets through in either direction.
  </Accordion>

  <Accordion title="This number isn't enabled on the workspace's iMessage line">
    The workspace sends from a shared Photon line, which only reaches numbers registered on the Photon
    project. Ask a platform administrator to add the number or assign a dedicated line, then send a new
    message.
  </Accordion>

  <Accordion title="iMessage is unavailable in the Inbox">
    The workspace does not have exactly one healthy Photon sender. Ask a platform administrator to inspect the
    connection and webhook status.
  </Accordion>

  <Accordion title="Customer stopped receiving messages">
    Check the contact's timeline for an opt-out event. A phone STOP suppresses calls, SMS, and iMessage for
    that number.
  </Accordion>
</AccordionGroup>

<Card title="Photon pilot" icon="comment" href="https://www.revdesk.com/settings/integrations">
  Contact RevDesk to enable the workspace-managed pilot.
</Card>


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