Understanding iMessage Limits: Apple ID vs SIM

myCRMSIM supports two distinct messaging setups: Android SMS and iPhone/iMessage. They are designed for different use cases, have different device requirements, and scale differently. This guide explains which option to choose, how SIM cards affect Android SMS, and why iMessage capacity is tied to an Apple ID rather than simply adding more SIM cards.
Important: An Android device used for myCRMSIM SMS should have RCS turned off. Incoming RCS messages cannot be received by the SMS Gateway app, so disabling RCS ensures messages use SMS/MMS and remain synchronised with myCRMSIM and your CRM.
1. At a Glance: Android SMS vs iPhone iMessage

Area

Android SMS

iPhone iMessage

Primary channel

Standard SMS/MMS sent through an Android phone and its SIM card

iMessage sent through a Mac linked to an iPhone with iMessage enabled

Best for

Higher-volume SMS outreach and distributing traffic across several numbers

Lower-volume, more personal iMessage conversations and follow-ups

What determines the sender number/capacity

The physical SIM card assigned to the sending device or user

The Apple ID / iMessage identity, not the number of SIM cards in the iPhone

How to scale

Add SIM cards/numbers, assign them to users, and distribute leads across those users

Use a separate iPhone and a separate Apple ID for each additional iMessage sending identity, along with one Mac using different user profiles with different Apple IDs (not more than 4 per machine)

Recipient compatibility

Works as SMS/MMS for mobile recipients

Sends iMessage to iPhone recipients; Android recipients receive SMS only when SMS fallback is available

Required device state

Android Gateway app must stay active, have permissions, and be the default SMS app

Mac Gateway app must stay on, connected to the internet, and not go to sleep

The key decision is simple: choose Android SMS when you need to distribute SMS volume across multiple SIM cards. Choose iPhone/iMessage when your workflow needs iMessage conversations and you can operate within Apple’s account-based sending model. A mixed setup can use both channels where required.
2. Android SMS: How SIM Cards Work
Android SMS is SIM-based. Each Android device sends messages through the SIM selected in the Gateway app. If you use Dual SIM, select the correct SIM for outgoing messages in the app settings. The SMS Gateway app must remain the default SMS app and must be permitted to run in the background so messages can send and sync reliably.
myCRMSIM’s multi-SIM functionality allows you to attach additional numbers to a sub-account and assign those numbers to different users. This lets you spread SMS traffic across SIM cards and distribute leads between users. To distribute the load properly, use a split or assignment process in the CRM so leads are assigned across the relevant users.
How Replies Work with Multiple Android SIMs
To use your own sub-account, please create a Webhook Workspace and make sure the required sub-account has been added.
When a contact is assigned to a user who has a SIM card, replies should be sent from that user’s assigned SIM. If a contact is not assigned, or the assigned user does not have a SIM assigned, myCRMSIM uses the default SIM number.
To keep a conversation on the same number, use HighLevel’s Login As function to switch into the assigned user before replying. If you reply while logged in as a different user, the message may be sent from that user’s number or from the default SIM, which can confuse the contact.
Rule for multi-SIM SMS: Check the contact’s assigned user, log in as that user, then send the reply. This keeps the outgoing number consistent with the conversation.
3. Android SMS Setup Checklist
Before you start, connect your HighLevel account to myCRMSIM or to use your own sub-account, please create a Webhook Workspace and make sure the required sub-account has been added. Then prepare the Android phone as follows.

Step

What to Do

1. Disable Play Protect

In Google Play Store, open Play Protect and turn off its protection settings before installing or updating the gateway app.

3. Install the Android app

Download the APK from https://get.mysmsgateway.app, install it, and open the app.

3. Install the Android app

Download the APK from https://get.mysmsgateway.app, install it, and open the app.

4. Grant all permissions

Allow SMS, Phone, Call logs, Contacts, and background activity permissions. Disable battery optimisation and any setting that pauses unused apps.

5. Connect the device

In myCRMSIM, go to Devices → Android Devices → Add New Device. Scan the QR code in the app or enter the supplied token. Name and save the device.

6. Assign and route

Assign the device to the correct GHL sub-account And Webhook workspace and make sure SMS is selected in Message Routing.

8. Choose the SIM and test

In Android’s Default Apps settings, set the SMS Gateway app as the default SMS app.

8. Choose the SIM and test

In Android’s Default Apps settings, set the SMS Gateway app as the default SMS app.

These settings are required to prevent common issues, including RCS conflicts, missing permissions, app suspension, or an unassigned device.
4. iPhone iMessage: How Apple ID and SIM Cards Work
iMessage is Apple ID-based, not SIM-capacity-based. For the myCRMSIM iMessage setup, your iPhone and Mac must use the same Apple ID, with iMessage enabled on both devices. The Mac acts as the always-on connection for iMessage automation.
Adding a second SIM or using Dual SIM on an iPhone gives the phone another cellular number, but it does not give you a second iMessage sending capacity for the same Apple ID. myCRMSIM’s current iMessage guidance recommends approximately 50 new contacts per day per Apple ID and states that this limit is tied to the Apple ID, not the SIM card.
Scenario
What It Means

One iPhone, one Apple ID, one SIM

One iMessage sending identity and its associated sending limit.

One iPhone, one Apple ID, Dual SIM

Two cellular numbers may be available, but this does not create another iMessage sending identity or double the Apple ID-based iMessage limit.

Additional iMessage capacity

Use a separate iPhone and a separate Apple ID for each additional iMessage sending identity, along with one Mac using different user profiles with different Apple IDs.

Additional SMS capacity

Use Android SMS with additional SIM cards/numbers and distribute contacts across users.

Important: Do not treat an extra iPhone SIM as a second iMessage account. For myCRMSIM iMessage operations, the recommended way to add a separate iMessage sender is a separate iPhone with its own Apple ID.
5. iPhone/iMessage Setup Checklist
Prepare the iPhone and Mac before installing the myCRMSIM iMessage connection.

Step

What to Do

1. Match the Apple ID

Sign in to the same Apple ID on the iPhone and Mac.

2. Enable iCloud Messages

On iPhone, turn on Messages in iCloud. On Mac, enable Messages in iCloud in Messages settings.

3. Grant all permissions

Enable Full Disk Access, Automation, Accessibility , Prevent Disk Sleep , Voice notes Setup

4. Configure the sender identity

On the Mac, set Start new conversations from to the phone number and uncheck the email address to avoid using the wrong sender identity.

5. Enable SMS fallback

On the iPhone, enable Send as Text Message so non-iMessage recipients can receive SMS when the phone is connected.

6. Test Apple sync first

Send an iMessage from the Mac to a test number. Confirm that the message and reply appear on both the iPhone and Mac.

7. Add the Mac integration

In myCRMSIM, go to Devices → iMessage → Add Device, download and install the Mac app, then authenticate it.

8. Assign the device

Refresh the iMessage device list, connect the required sub-account, then assign the Mac device to that sub-account.

9. Keep the Mac available

Keep the Mac switched on, online, and awake. Check power settings so the device does not sleep.

These requirements are necessary because the Mac must stay connected for myCRMSIM to send and receive iMessages through the linked Apple ID
⚠️ Important Considerations
  • 💻 Performance Tip: System performance and stability depend on the Mac’s memory and CPU:
    • Recommended Maximum: To reduce the risk of getting flagged we recommend to keep it to maximum 4 iPhones and associated iMessage accounts running on any one single machine.
  • 🚫 Anti-Flagging Warning: Running more than 4 iMessage instances on one Mac may risk detection or account flagging by Apple.
6. Provider and Routing Choices
The correct HighLevel provider depends on whether you use iMessage only or a mixed setup.

Your Setup

Select This Provider

Expected Routing Behaviour

Mac/iMessage only

mySMS Gateway App - iMessage Only and mySMS Gateway App - SMS,WhatsApp and iMessage

iPhone recipients receive iMessages. If the recipient cannot receive iMessage, the connected iPhone can use SMS fallback.

Android SMS + iMessage/WhatsApp

mySMS Gateway App - SMS,WhatsApp and iMessage

HighLevel uses the appropriate connected channel. For workflow automation, standard SMS actions default to Android; use the custom Send iMessage action when you need to target iMessage specifically.

When an iMessage-only configuration sends to an Android recipient, the recipient cannot receive an iMessage. In that case, the connected iPhone can send a green-bubble SMS fallback only when it is online and connected.
7. Which Setup Should I Use?
Use the following guidance to select the right setup for your workspace.

If You Need To…

Recommended Setup

Send regular SMS and spread volume across several phone numbers

Android SMS with multiple SIMs

Keep messages on the assigned salesperson’s number

Android SMS with user-to-SIM assignments

Send personal, lower-volume messages to iPhone users

iPhone + Mac iMessage

Add a second iMessage sending identity

Another iPhone and a separate Apple ID + Mac using different user profiles with Separate Apple IDs.

Use SMS outreach and iMessage follow-up together

Mixed Android + iMessage setup with the combined provider

Send to Android recipients

Android SMS, or iPhone SMS fallback where the connected iPhone is available

8. Common Questions
1. Can I increase iMessage capacity by adding another SIM to my iPhone?

No. A Dual SIM iPhone can hold two phone numbers, but it does not create a second Apple ID-based iMessage sending identity or increase the daily iMessage capacity for the same Apple ID.  If you need an additional iMessage sending identity, use a separate 2. 2. 2. iPhone and a separate Apple ID for each additional sender. You can use one Mac with different user profiles, with each profile signed in to a different Apple ID.

3. Can I add more phone numbers for SMS sending?

Yes. Use the multi-SIM feature to add numbers, assign them to users, and distribute leads across those users. Ensure that each reply is sent while logged in as the user assigned to the relevant SIM.

4. Why must I turn off RCS on Android?

The myCRMSIM SMS Gateway app cannot receive incoming RCS messages. Turning off RCS makes the device use SMS/MMS, which allows messages to synchronise correctly with myCRMSIM and the CRM.

5. Can I use iMessage to message Android users?

Android users cannot receive iMessages. With an active connected iPhone and the appropriate configuration, the message can use green-bubble SMS fallback instead.

6. Can I use Android SMS and iMessage in the same workspace?

Yes. Select the combined SMS WhatsApp iMessage Gateway provider. In workflows, use the custom Send iMessage action when iMessage must be targeted specifically; standard SMS actions default to the Android device in a mixed configuration.

9. Final Pre-Send Checklist
Before sending live messages, confirm that the selected channel is working end to end.

Android SMS

iPhone/iMessage

RCS is off and SMS Gateway is the default SMS app

iPhone and Mac use the same Apple ID

All permissions and background access are allowed

Messages in iCloud is enabled on both devices

The correct SIM is selected and device is assigned

Mac is online, awake, and assigned to the correct sub-account

The reply user matches the assigned SIM

The correct provider is selected in HighLevel

A CRM test message and a phone reply both succeed

A Mac-to-phone iMessage test and return reply both succeed

References

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us