# Multiple iMessage Accounts per Sub-Account

Connect multiple iMessage accounts to a single GoHighLevel sub-account to enable team-based messaging, assign specific phone numbers to individual users, and scale your iMessage sending capacity across multiple devices.

{% hint style="success" %}
**Team Collaboration**: Assign each team member their own iMessage number, allowing personalized communication while maintaining centralized management in one GHL sub-account.
{% endhint %}

## 🚀 Overview

### Why Connect Multiple iMessage Accounts?

Connecting multiple iMessage numbers to one GoHighLevel sub-account is beneficial when you want to:

**Team-Based Messaging:**

* ✅ Assign individual team members their own iMessage phone number
* ✅ Maintain personal communication style per team member
* ✅ Track performance and activity by user
* ✅ Separate sales, support, and management communications

**Increased Sending Volume:**

* ✅ Distribute message sending across multiple devices
* ✅ Stay within Apple's 50 contacts/day limit per device
* ✅ Send to 200+ contacts daily across 4 iMessage accounts
* ✅ Reduce risk by spreading volume across multiple numbers

**Organizational Structure:**

* ✅ Department-specific phone numbers (Sales, Support, Billing)
* ✅ Geographic distribution (East Coast, West Coast, International)
* ✅ Role-based assignments (Account Manager, Customer Success, Sales Rep)
* ✅ VIP vs. general customer segmentation

### How It Works

{% @mermaid/diagram content="graph TD;
A\["🏢 GHL Sub-Account"] --> B\["👤 User 1: Sales Rep"];
A --> C\["👤 User 2: Support Agent"];
A --> D\["👤 User 3: Account Manager"];

```
B --> E["📱 iMessage Account 1<br/>+1-555-0101"];
C --> F["📱 iMessage Account 2<br/>+1-555-0102"];
D --> G["📱 iMessage Account 3<br/>+1-555-0103"];

E --> H["💬 Messages"];
F --> H;
G --> H;

H --> I{Contact Assignment?};
I -->|"Assigned to User 1"| J["📤 Sends from +1-555-0101"];
I -->|"Assigned to User 2"| K["📤 Sends from +1-555-0102"];
I -->|"Assigned to User 3"| L["📤 Sends from +1-555-0103"];
I -->|"Unassigned"| M["📤 Sends from Default Account"];

classDef ghl fill:#e3f2fd,stroke:#1976d2,stroke-width:3px,color:#000000;
classDef user fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px,color:#000000;
classDef device fill:#e8f5e8,stroke:#00695c,stroke-width:2px,color:#000000;
classDef routing fill:#e1f5fe,stroke:#3f51b5,stroke-width:2px,color:#000000;

class A ghl;
class B,C,D user;
class E,F,G device;
class H,I,J,K,L,M routing;" %}
```

## ✅ Prerequisites

Before setting up multiple iMessage accounts, ensure you have:

### Device Requirements

* [ ] **Multiple Mac Devices** - One Mac per iMessage account (recommended)
  * OR one Mac with multiple user profiles (see [Advanced Setup](#advanced-single-mac-setup) below)
* [ ] **Multiple iPhones** - One iPhone per iMessage account
* [ ] **Each device** meets [iMessage specifications](/whatsnap-docs/account-management/imessage/imessage-specifications.md)
* [ ] All devices are **properly connected** to WhatSnap (see [Adding iMessage Accounts](/whatsnap-docs/account-management/imessage.md))

### GoHighLevel Requirements

* [ ] **Multiple GHL Users** created in your sub-account
  * One user per iMessage number
  * Even if using for volume only, create a user (can be a "dummy" profile)
* [ ] **User permissions** properly configured
* [ ] Access to **Settings → Phone Numbers** in GHL

### WhatSnap Requirements

* [ ] **WhatSnap account** active with sufficient device slots
* [ ] Each iMessage device **connected** and showing as "Active"
* [ ] Each device has a **unique account tag** (e.g., `whatsnap-account-imessage-1`, `whatsnap-account-imessage-2`)

## ⚙️ Step-by-Step Setup

{% stepper %}
{% step %}

#### Step 1: Connect All iMessage Devices

Before assigning to users, ensure all devices are connected to WhatSnap:

1. **Connect First iMessage Device**:
   * Follow the [Adding iMessage Accounts](/whatsnap-docs/account-management/imessage.md) guide
   * Complete setup and verify it works
   * Note the account tag (e.g., `whatsnap-account-imessage-1`)
2. **Connect Additional Devices**:
   * Repeat the connection process for each additional iPhone/Mac pair
   * Use separate Macs or separate user profiles on one Mac
   * Each device gets a unique account tag
   * Verify each device shows as "Connected" in WhatSnap dashboard
3. **Verify All Connections**:
   * Go to **WhatSnap Dashboard** → **Connected Accounts**
   * You should see all iMessage devices listed
   * Status should show **"Active"** or **"Connected"** for each
   * Test send a message from each device's Mac to confirm functionality

{% hint style="info" %}
**Device Naming**: Give each device a descriptive name in WhatSnap for easy identification (e.g., "Sales iMessage", "Support iMessage", "Manager iMessage").
{% endhint %}
{% endstep %}

{% step %}

#### Step 2: Create or Verify GHL Users

Each iMessage account must be assigned to a unique GoHighLevel user:

**Create New Users:**

1. In GoHighLevel, go to **Settings** → **My Staff**
2. Click **"+ Add User"**
3. Enter user details:
   * **Name**: Team member's name (or descriptive name like "Sales iMessage User")
   * **Email**: Valid email address
   * **Role**: Appropriate role based on permissions needed
4. Set **Permissions** as needed
5. Click **"Create User"**
6. Repeat for each iMessage account

**For Volume-Only Setup (No Real Team Member):**

If you're connecting multiple devices just for volume (not actual team members):

1. Create "dummy" user profiles
2. Name them descriptively: "iMessage Device 2", "iMessage Volume Account"
3. Set minimal permissions (these won't be used for actual login)
4. These serve only to enable device assignment

{% hint style="warning" %}
**One User Per Device**: You cannot assign multiple iMessage devices to the same GHL user. Each device requires a unique user assignment.
{% endhint %}
{% endstep %}

{% step %}

#### Step 3: Assign Devices to Users in WhatSnap

Now connect each iMessage device to its corresponding GHL user:

1. **Open WhatSnap Dashboard**
2. Navigate to **Connected Accounts** or **Devices**
3. Locate your first unassigned iMessage device
4. Click **device settings** or **menu** (⋮)
5. Select **"User Assignment"** or **"Assign to User"**
6. Choose the **GHL user** from the dropdown
7. Click **"Assign"** or **"Save"**
8. Repeat for each iMessage device

**Verify Assignments:**

* Each device should now show the assigned user's name
* In GoHighLevel, each user should have an associated iMessage account
* Test by logging in as each user and sending a test message

{% hint style="success" %}
**Assignment Complete!** Each team member (or volume account) now has their own iMessage number for sending messages.
{% endhint %}
{% endstep %}

{% step %}

#### Step 4: Configure Default Account

Set a default iMessage account for unassigned contacts:

1. In **WhatSnap Dashboard**, go to **Settings**
2. Find **"Default iMessage Account"** setting
3. Select which device should be the **default**
4. This account will be used when:
   * Contact is not assigned to any user
   * Contact is assigned to a user without an iMessage device
   * Fallback for system messages

**Recommended Default:**

* Use your primary or most reliable device
* Typically the first device you connected
* Should be the account with best uptime/reliability
  {% endstep %}
  {% endstepper %}

## 💬 How Messaging Works with Multiple Accounts

### Automated Messages (via Workflows)

When sending messages through GoHighLevel workflows, WhatSnap automatically routes based on contact assignment:

{% @mermaid/diagram content="graph TD;
A\["🤖 Workflow Triggers<br/>Send Message Action"] --> B{Check Contact<br/>Assignment};

```
B -->|"Assigned to User 1"| C["👤 User 1 has<br/>iMessage device?"];
B -->|"Assigned to User 2"| D["👤 User 2 has<br/>iMessage device?"];
B -->|"Not Assigned"| E["📱 Use Default<br/>iMessage Account"];

C -->|"✅ Yes"| F["📤 Send from<br/>User 1's iMessage"];
C -->|"❌ No"| E;

D -->|"✅ Yes"| G["📤 Send from<br/>User 2's iMessage"];
D -->|"❌ No"| E;

F --> H["✅ Message Delivered"];
G --> H;
E --> H;

classDef workflow fill:#e3f2fd,stroke:#1976d2,stroke-width:3px,color:#000000;
classDef decision fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px,color:#000000;
classDef send fill:#e8f5e8,stroke:#00695c,stroke-width:2px,color:#000000;
classDef complete fill:#e1f5fe,stroke:#3f51b5,stroke-width:2px,color:#000000;

class A workflow;
class B,C,D decision;
class E,F,G send;
class H complete;" %}
```

**Workflow Routing Rules:**

| Contact Status | Assigned User | User Has Device? | Message Sends From        |
| -------------- | ------------- | ---------------- | ------------------------- |
| **Assigned**   | User 1        | ✅ Yes            | User 1's iMessage account |
| **Assigned**   | User 2        | ✅ Yes            | User 2's iMessage account |
| **Assigned**   | User 3        | ❌ No             | Default iMessage account  |
| **Unassigned** | None          | N/A              | Default iMessage account  |

**Example Workflow:**

```
Trigger: New lead added
Condition: Lead source = "Facebook"
Action: Assign to User "Sales Rep 1"
Action: Send SMS - "Hi {{first_name}}, thanks for your interest!"
Result: Message automatically sends from Sales Rep 1's iMessage number
```

### Manual Messages (Conversation Tab)

When manually sending messages from the GoHighLevel conversation tab, routing depends on who is logged in:

**Default Behavior:**

* Messages send from the **logged-in user's** assigned iMessage account
* NOT from the contact's assigned user (unless they're the same)

**Example Scenarios:**

| Logged-in User     | Contact Assigned To | Message Sends From                  |
| ------------------ | ------------------- | ----------------------------------- |
| User 1 (Sales)     | User 1 (Sales)      | ✅ User 1's iMessage                 |
| User 1 (Sales)     | User 2 (Support)    | ⚠️ User 1's iMessage (not User 2's) |
| User 2 (Support)   | User 1 (Sales)      | ⚠️ User 2's iMessage (not User 1's) |
| User 3 (No device) | User 1 (Sales)      | Default iMessage                    |

{% hint style="warning" %}
**Important**: When manually messaging from the conversation tab, the message sends from YOUR (logged-in user's) iMessage number, not the contact's assigned user. See override options below.
{% endhint %}

## 🔄 Overriding Message Routing

Sometimes you need to send from a specific iMessage account regardless of who is logged in or who the contact is assigned to.

### Method 1: Using #switch Commands (Recommended)

WhatSnap's command system allows you to override the default routing:

**Permanently Switch Contact to Different Account:**

```
#switch|whatsnap-account-imessage-2 Hi {{first_name}}, this is Sarah from support taking over your case...
```

**Effect:**

* Contact's account tag changes to `whatsnap-account-imessage-2`
* All future messages (manual and automated) use this account
* Contact effectively "belongs" to this iMessage number now

**Send One Message from Different Account:**

```
#switch_unique|whatsnap-account-imessage-3 Hi {{first_name}}, this is Mike the manager checking in on your experience...
```

**Effect:**

* This message sends from `whatsnap-account-imessage-3`
* Contact's original tag remains unchanged
* Next message reverts to original account

### Method 2: Log In as Correct User

The simplest approach when manually messaging:

1. **Identify** which user the contact is assigned to
2. **Log out** of your current GHL account
3. **Log in** as the assigned user
4. **Send message** - will automatically use that user's iMessage account
5. **Log back in** as yourself when done

**Pros:**

* Simple and straightforward
* No need to remember commands
* Works with all GHL features

**Cons:**

* Requires multiple logins
* Time-consuming for quick messages
* Not practical for high volume

### Method 3: Change Contact Assignment

For ongoing conversations, reassign the contact:

1. Open the **contact record** in GoHighLevel
2. Find **"Assigned User"** field
3. Change to the user whose iMessage number you want to use
4. **Save** the contact
5. Future messages will use the new user's iMessage account

**Use When:**

* Contact needs to be handed off permanently
* Reassigning from sales to support
* Moving VIP clients to senior account manager
* Consolidating contacts under one user

### Comparison of Methods

| Method               | Use Case                   | Permanent? | Ease of Use              |
| -------------------- | -------------------------- | ---------- | ------------------------ |
| **#switch Command**  | Change account for contact | ✅ Yes      | Medium (remember syntax) |
| **#switch\_unique**  | One-off message override   | ❌ No       | Medium (remember syntax) |
| **Login as User**    | Quick manual message       | N/A        | Easy but time-consuming  |
| **Reassign Contact** | Long-term handoff          | ✅ Yes      | Easy (UI-based)          |

## 📊 Team Collaboration Scenarios

### Scenario 1: Sales Team with Individual Numbers

**Setup:**

* **User 1** (Sarah - Sales Rep): `whatsnap-account-sales-sarah`
* **User 2** (Mike - Sales Rep): `whatsnap-account-sales-mike`
* **User 3** (Lisa - Sales Manager): `whatsnap-account-sales-manager`

**Workflow:**

1. New lead comes in from Facebook ad
2. Round-robin assignment puts lead on Sarah
3. Automated welcome message sends from **Sarah's iMessage number**
4. Sarah manually messages from her account (logged in as Sarah)
5. If lead needs escalation, use `#switch|whatsnap-account-sales-manager` to transfer to Lisa
6. All future messages come from Lisa's iMessage

**Benefits:**

* Personal touch with consistent phone number per rep
* Easy tracking of individual rep performance
* Smooth escalation process
* Each rep stays within 50 contacts/day limit

### Scenario 2: Department-Based Assignment

**Setup:**

* **Sales Dept**: `whatsnap-account-sales` (assigned to Sales User)
* **Support Dept**: `whatsnap-account-support` (assigned to Support User)
* **Billing Dept**: `whatsnap-account-billing` (assigned to Billing User)

**Workflow:**

1. All new leads assigned to "Sales User"
2. Messages send from sales iMessage number
3. When customer purchases, reassign to "Support User"
4. Support messages now come from support iMessage number
5. For billing issues, reassign to "Billing User"
6. Billing communications from dedicated billing number

**Benefits:**

* Clear departmental communication
* Customers know which number reaches which department
* Volume distributed across departments
* Professional organization

### Scenario 3: Volume Distribution (No Team)

**Setup:**

* **Device 1**: `whatsnap-account-volume-1` (dummy user)
* **Device 2**: `whatsnap-account-volume-2` (dummy user)
* **Device 3**: `whatsnap-account-volume-3` (dummy user)
* **Device 4**: `whatsnap-account-volume-4` (dummy user)

**Workflow:**

1. All devices assigned to dummy users for volume only
2. Contacts distributed equally via tag assignment
3. 250 contacts per device per week (under 50/day limit)
4. Total capacity: 1000 contacts per week
5. You manage all from your main login using commands when needed

**Benefits:**

* Massive volume increase (4x capacity)
* Stay within Apple's limits per device
* Risk distribution across multiple numbers
* All managed from single login

## 📈 Volume Planning

### Calculating Capacity

**Single iMessage Account:**

* Limit: 50 contacts/day
* Weekly: 350 contacts (7 days)
* Monthly: \~1,500 contacts (30 days)

**Multiple Accounts:**

| # of Accounts  | Daily Capacity | Weekly Capacity | Monthly Capacity |
| -------------- | -------------- | --------------- | ---------------- |
| **1 Account**  | 50             | 350             | 1,500            |
| **2 Accounts** | 100            | 700             | 3,000            |
| **3 Accounts** | 150            | 1,050           | 4,500            |
| **4 Accounts** | 200            | 1,400           | 6,000            |

{% hint style="warning" %}
**Apple Limit Compliance**: Never exceed 50 unique contacts per day per device. Distribute your volume, don't concentrate it.
{% endhint %}

### Volume Distribution Strategies

**Strategy 1: Equal Distribution**

* Divide contacts evenly across all devices
* Each device sends to same number of contacts
* Simple to manage and track

**Strategy 2: Priority-Based**

* VIP/urgent contacts on most reliable device
* General contacts distributed across other devices
* Ensures critical messages always send

**Strategy 3: Time-Based**

* Device 1: Morning messages (9 AM - 12 PM)
* Device 2: Afternoon messages (12 PM - 3 PM)
* Device 3: Evening messages (3 PM - 6 PM)
* Spreads load throughout the day

## 🔧 Advanced: Single Mac Setup

For cost savings, you can run multiple iMessage accounts on **one Mac** using separate user profiles:

{% hint style="info" %}
**Single Mac Multi-Account**: Detailed instructions are available in our [iMessage Specifications - Multiple iPhone Setup](/whatsnap-docs/account-management/imessage/imessage-specifications.md#multiple-iphone-setup-advanced) section.
{% endhint %}

**Quick Overview:**

1. **Create Mac User Profiles** - One per iMessage account
2. **Install WhatSnap Gateway** in each profile
3. **Connect Each iPhone** to its respective Mac profile
4. **Use Fast User Switching** - Keep all profiles logged in simultaneously
5. **Maximum 4 iPhones** per Mac recommended

**Requirements:**

* **16-32 GB RAM** for multiple accounts
* **Mac mini M1/M2** recommended for reliability
* **Strong internet** connection (Ethernet preferred)

See [iMessage Specifications](/whatsnap-docs/account-management/imessage/imessage-specifications.md) for full hardware requirements.

## 🔍 Monitoring & Management

### Tracking Performance by Account

**WhatSnap Dashboard:**

* View message volume per device
* Monitor connection status for each account
* Track delivery rates per account
* Identify which accounts are most active

**GoHighLevel Reporting:**

* Filter conversations by assigned user
* Track response rates per team member
* Monitor message volume by user
* Analyze performance metrics

### Best Practices

**Daily Monitoring:**

* [ ] Check all devices show as "Connected" in WhatSnap
* [ ] Verify no devices are offline or disconnected
* [ ] Monitor daily message count per device (stay under 50)
* [ ] Review any failed messages or errors

**Weekly Review:**

* [ ] Analyze which accounts have best engagement
* [ ] Rebalance contact distribution if needed
* [ ] Check Mac devices are staying awake and running
* [ ] Review team performance if using team-based setup

**Monthly Optimization:**

* [ ] Review device reliability and uptime
* [ ] Optimize contact assignment strategy
* [ ] Assess if you need more or fewer devices
* [ ] Update team assignments if needed

## ⚠️ Troubleshooting Multiple Accounts

### Common Issues

<details>

<summary>Message sending from wrong iMessage account</summary>

**Problem:** Contact assigned to User 1, but message sends from User 2's iMessage.

**Solutions:**

1. Verify contact is assigned to correct user in GHL
2. Check user has an iMessage device assigned in WhatSnap
3. Verify WhatSnap Gateway app is running for that user's device
4. Use `#switch` command to force correct account
5. Check default account settings in WhatSnap

</details>

<details>

<summary>Some accounts work, others don't</summary>

**Problem:** Messages send from some iMessage accounts but not others.

**Solutions:**

1. Check WhatSnap Gateway app is running for affected devices
2. Verify Mac is online and not asleep
3. Check Messages in iCloud is enabled on affected iPhone/Mac
4. Reconnect affected device with fresh authentication token
5. Verify Full Disk Access permission granted for each Mac

</details>

<details>

<summary>Can't assign device to user</summary>

**Problem:** WhatSnap won't let you assign device to a specific user.

**Solutions:**

1. Verify user exists in the correct GHL sub-account
2. Check if device is already assigned to another user (unassign first)
3. Ensure device is showing as "Connected" before assigning
4. Try refreshing WhatSnap dashboard
5. Contact WhatSnap support if issue persists

</details>

For comprehensive troubleshooting, see our [iMessage Troubleshooting Guide](/whatsnap-docs/account-management/imessage/troubleshooting-imessage.md).

## 📚 Related Documentation

* [**Adding iMessage Accounts**](/whatsnap-docs/account-management/imessage.md) - How to connect your first iMessage device
* [**iMessage Specifications**](/whatsnap-docs/account-management/imessage/imessage-specifications.md) - Hardware requirements for multiple devices
* [**iMessage Troubleshooting**](/whatsnap-docs/account-management/imessage/troubleshooting-imessage.md) - Solve common issues
* [**iMessage Account Blocked**](/whatsnap-docs/account-management/imessage/imessage-account-blocked.md) - Recover from Apple iMessage deactivation
* [**User Assignments**](/whatsnap-docs/account-management/settings/user-assignments.md) - Understanding automatic user assignment
* [**Tag Management**](/whatsnap-docs/account-management/settings/tag-management.md) - How tags work with multiple accounts
* [**Command System**](https://github.com/WhatSnap/documentation/blob/main/conversations/commands-system.md) - Using #switch commands

{% hint style="success" %}
**Ready to Scale!** With multiple iMessage accounts connected to your GoHighLevel sub-account, you can now handle team-based communications, increase your sending volume, and provide more personalized customer experiences.
{% endhint %}

***

**Questions?** Contact <support@whatsnap.ai> for help with multi-account setup.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whatsnap.gitbook.io/whatsnap-docs/account-management/imessage/multiple-imessage-accounts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
