Multiple SMS Accounts

Learn how to connect and manage multiple Android devices and SIM cards with WhatSnap to increase messaging capacity and distribute load across multiple numbers.

Scale your SMS operations by connecting multiple Android devices and SIM cards to WhatSnap. This guide shows you how to add, manage, and route messages across multiple SMS accounts for increased volume capacity and organized team communication.

Scale Your Messaging: Each additional Android device/SIM adds 100-250 messages per day of capacity, allowing you to run larger database reactivation campaigns, separate departments, or provide redundancy.

Why Use Multiple SMS Accounts?

Benefits of Multi-SIM Setup

📈 Increased Volume Capacity

• Each SIM card adds 100-250 messages/day (after warm-up)

• Distribute large campaigns across multiple numbers

• Avoid hitting individual carrier limits

👥 Department Separation

• Sales team: Dedicated number and device

• Support team: Separate number for customer service

• Marketing: Distinct number for campaigns

• Each department has its own messaging identity

🌍 Geographic Distribution

• Different area codes for different regions

• Local presence in multiple markets

• Improved trust with local numbers

🔄 Redundancy & Reliability

• Backup if one device/SIM has issues

• Continue operations if one carrier has restrictions

• Distribute risk across multiple carriers

👤 User-Based Assignment

• Assign different numbers to different team members

• Personal accountability for conversations

• Clear ownership of customer relationships

Multi-SIM Setup Overview

Adding Multiple Android Devices

Step-by-Step: Adding Your Second (or Third, Fourth...) Device

1

Prepare the New Device

1. Obtain a new Android device meeting specifications

2. Install and activate a new SIM card

3. Test that the SIM can send/receive regular SMS

4. Charge the device and connect to internet

2

Install WhatSnap Gateway App

Follow the same installation process as your first device:

1. In WhatSnap dashboard, click "Add Account" → "SMS/iMessage (P2P)" → "Android"

2. Download the WhatSnap Gateway APK to your new device

3. Install the app (disable Play Protect if needed)

4. Grant all required permissions

5. Authenticate with the new QR code shown in dashboard

6. Start the gateway service

Full instructions: SMS Installation & Setup

3

Name the Device Descriptively

Give each device a clear, meaningful name:

Good Naming Examples:

• Android-Sales-Main

• Support-Device-247

• DBR-Campaign-1

• Marketing-Team-SMS

• Sales-Rep-John-Mobile

Poor Naming Examples:

• Device 1, Device 2 (not descriptive)

• Android, Phone (too generic)

• Test (unclear purpose)

Why Naming Matters: Clear names help your team quickly identify which device handles which contacts, essential for troubleshooting and managing replies.

4

Note Each Device's Tag

Each device receives a unique tag:

• Device 1: whatsnap-account-android-sales

• Device 2: whatsnap-account-android-support

• Device 3: whatsnap-account-android-marketing

Write down all tags - you'll use these to route messages to specific devices.

5

Assign Devices to Users (Optional but Recommended)

For multi-SIM setups, assign each device to a specific GHL user:

1. In WhatSnap dashboard, open device settings

2. Find "Assign to User" or "User Assignment"

3. Select the GoHighLevel user who will manage this device

4. Save settings

Benefits:

• Messages from this device show as coming from that user

• Replies automatically route to the correct user's inbox

• Clear accountability for conversations

See: User Assignments

---

Message Distribution Strategies

Strategy 1: Manual Tag Assignment

How It Works:

• Manually add specific device tags to contacts

• Each contact routes to its tagged device

• Simple, direct control

When to Use:

• Small contact lists

• VIP customer assignment to specific reps

• Specific use cases requiring manual control

Example:

Contact: John Doe
Tags: whatsnap-account-android-sales
→ All messages to John route through Sales device

Strategy 2: Workflow-Based Distribution

How It Works:

• Use GHL workflows to automatically tag and distribute contacts

• Split actions divide contacts across devices

• Automated, scalable approach

When to Use:

• Large campaigns

• Database reactivations

• Automated lead distribution

Example Workflow:

Setting Up in GoHighLevel:

1. Create a workflow with a Split action

2. Configure the split:

   • Random: Distribute contacts randomly across paths

   • Percentage: Set exact percentages (e.g., 33% / 33% / 34%)

3. After each split path, add "Add Tag" action with appropriate device tag

4. Add "Send SMS" action (automatically uses the tagged device)

Even Distribution: Use random or percentage-based splits to evenly distribute load across your SIM cards, preventing any single carrier from flagging high volume.

Strategy 3: Department-Based Routing

How It Works:

• Assign different devices to different business functions

• Route contacts based on their status or source

When to Use:

• Multi-department businesses

• Different messaging use cases

• Organized team structures

Example Setup:

Device	Purpose	User	Tag	Contact Types
Android 1	Sales	Sales Team	sms-sales	New leads, prospects
Android 2	Support	Support Team	sms-support	Existing customers
Android 3	Marketing	Marketing Team	sms-marketing	Campaign contacts

Workflow Example:

Trigger: New lead added
Condition: If source = "Website form" → Tag: sms-sales
Condition: If source = "Customer portal" → Tag: sms-support

Strategy 4: Geographic Distribution

How It Works:

• Use SIM cards with different area codes

• Route contacts to devices with matching local area code

• Builds local trust

When to Use:

• Multi-location businesses

• Regional campaigns

• Local service providers (plumbers, HVAC, etc.)

Example:

• Device 1: Los Angeles area code (213/310) → LA contacts

• Device 2: New York area code (212/917) → NYC contacts

• Device 3: Chicago area code (312/773) → Chicago contacts

---

Reply Management with Multiple SIMs

Critical: When using multiple SIM cards, you must reply to contacts from the same device/number they originally messaged. Otherwise, conversations will be confusing for recipients.

How Message Routing Works

Inbound Message Flow:

📱 Contact texts your Android 1 number
→ WhatSnap tags contact with device-1 tag
→ Message appears in GHL
→ Future outbound messages automatically use Android 1 (same number)

The Problem: If you're logged in as the wrong user or don't have the right tag, your reply might send from a different number, confusing the contact.

Solution 1: Login As Correct User

When replying to messages from different devices:

1

Check the Lead's Assignment

1. Open the contact in GoHighLevel

2. Check which device tag is assigned (or which user is assigned)

3. Note which device/number this contact expects messages from

2

Use "Login As" Function

1. In GoHighLevel, find the "Login As" function (usually in user management)

2. Select the user assigned to the device this contact uses

3. Once logged in as that user, your replies will send from the correct number

4. Send your reply

Why This Works: When you log in as a specific user, GHL sends messages using that user's assigned device/number, maintaining conversation continuity.

3

Return to Your User Account

After replying, you can switch back to your own user account or stay logged in as the other user to reply to more of their assigned conversations.

Solution 2: Use Conversation Filters

Manage multiple device conversations more efficiently:

1

Apply Conversation Filters

1. In GoHighLevel, go to Conversations

2. Click Filters

3. Under "Assigned To", select a specific user or device tag

4. This shows only conversations for that device/user

2

Login As That User

1. Use "Login As" to switch to that user

2. Reply to all conversations in the filtered view

3. All replies send from the correct number

3

Repeat for Other Devices

1. Clear filters or apply new filter for next device

2. Login as the next user

3. Reply to those conversations

4. Repeat for all devices

Efficiency Tip: This batching approach is faster than switching users for individual conversations. Handle all Device 1 conversations, then all Device 2, etc.

Solution 3: Multi-SIM Reply Override Feature

WhatSnap includes a reply override snapshot for advanced multi-SIM management:

How It Works:

• Automatically detects which device/number a contact last messaged

• Routes your reply through the correct device, regardless of which user is logged in

• No need to switch users

Setup:

1. Install the WhatSnap Multi-SIM Override Snapshot in your sub-account

2. The snapshot includes workflows that handle reply routing

3. Reply normally - the system routes to the correct device automatically

Advanced Feature: Contact WhatSnap support for access to the Multi-SIM Override Snapshot and installation instructions.

---

Load Balancing and Volume Management

Calculating Your Total Capacity

Single Device Capacity (after warm-up):

• Conservative: 100 messages/day

• Moderate: 150 messages/day

• Aggressive: 250 messages/day (varies by carrier)

Multi-Device Capacity:

Devices	Conservative	Moderate	Aggressive
1 Device	100/day	150/day	250/day
3 Devices	300/day	450/day	750/day
5 Devices	500/day	750/day	1,250/day
10 Devices	1,000/day	1,500/day	2,500/day

Scaling Strategy: Start conservative with each new device. Increase volume gradually as you confirm deliverability and avoid carrier issues.

Monitoring Device Performance

Track metrics for each device:

Daily Monitoring:

• Messages sent (per device)

• Delivery success rate

• Response rate

• Any error messages or failed sends

Weekly Review:

• Carrier restrictions or warnings

• Device uptime and connectivity

• Unsubscribe rates

• Conversation quality

Signs of Trouble:

• ⚠️ Delivery rates dropping below 95%

• ⚠️ Increased "failed to send" errors

• ⚠️ Carrier notifications or warnings

• ⚠️ SIM card restrictions

Action Steps:

1. Reduce volume on affected device

2. Improve message quality and personalization

3. Check carrier fair use compliance

4. Contact carrier if needed

5. Consider rotating to a backup SIM

Warm-Up Strategy for Multiple Devices

Don't warm up all devices simultaneously:

Recommended Approach:

Week 1:

• Warm up Device 1 only

• Start slow: 10-20 msgs/day

Week 2:

• Device 1: Increase to 50-100 msgs/day

• Device 2: Start warm-up at 10-20 msgs/day

Week 3:

• Device 1: Full volume (100-250 msgs/day)

• Device 2: Increase to 50-100 msgs/day

• Device 3: Start warm-up at 10-20 msgs/day

Benefits:

• Staggered growth looks more natural

• Learn from first device before scaling

• Maintain some capacity while warming new devices

• Reduce risk of simultaneous carrier blocks

See: Database Reactivations - SIM Warm-Up

---

Multi-SIM Workflow Examples

Example 1: Database Reactivation Campaign (3 Devices)

Goal: Re-engage 3,000 old leads over 10 days

Setup:

• 3 Android devices, each warmed up

• Each can handle 100 messages/day = 300 messages/day total

• Campaign: 300 msgs/day × 10 days = 3,000 contacts

Workflow:

Trigger: Tag added → "DBR-Campaign-2025"
↓
Split (Random, 3 paths):
  → Path 1 (33%): Tag "sms-device-1"
  → Path 2 (33%): Tag "sms-device-2"
  → Path 3 (34%): Tag "sms-device-3"
↓
Drip Campaign (each path):
  → Day 1: Send initial message
  → Wait 2 days
  → If no reply: Send follow-up
  → Wait 3 days
  → If no reply: Final message
  → If reply: Move to "Engaged" pipeline

Example 2: Sales Team Multi-Rep Setup (5 Devices)

Goal: 5 sales reps each have dedicated numbers

Setup:

• 5 Android devices, one per sales rep

• Each device assigned to rep's GHL user

• Leads distributed based on source or round-robin

Workflow:

Trigger: New lead created
↓
Round-Robin Assignment:
  → Assign to User: Rep 1 → Auto-tag: sms-rep-1
  → Assign to User: Rep 2 → Auto-tag: sms-rep-2
  → Assign to User: Rep 3 → Auto-tag: sms-rep-3
  → Assign to User: Rep 4 → Auto-tag: sms-rep-4
  → Assign to User: Rep 5 → Auto-tag: sms-rep-5
↓
Each rep manages their assigned leads
Messages automatically send from their device

Example 3: Department Separation (3 Devices)

Goal: Separate numbers for Sales, Support, Marketing

Setup:

• Device 1: Sales number (new leads)

• Device 2: Support number (existing customers)

• Device 3: Marketing number (campaigns)

Workflow:

Trigger: Contact created or updated
↓
Conditions:
  → If Pipeline = "Sales" → Tag: sms-sales
  → If Tag contains "Customer" → Tag: sms-support
  → If Tag contains "Campaign" → Tag: sms-marketing
↓
Messages automatically route to appropriate device

---

Best Practices for Multi-SIM Management

Organization

✅ Do:

• Maintain a spreadsheet tracking all devices, SIMs, and assignments

• Document which phone number belongs to which device

• Keep tags consistent and descriptive

• Label physical devices clearly (write device name on phone with label)

❌ Don't:

• Mix personal and business use on the same device

• Swap SIM cards between devices without updating settings

• Use vague or generic device names

Redundancy Planning

Prepare for device failures:

• Keep 1-2 backup devices ready

• Store backup SIM cards (inactive but available)

• Document the process for activating backup devices

• Test backups periodically

If a device fails:

1. Activate backup device with same number (SIM swap)

2. Or: Quickly reassign contacts to working devices

3. Update tags and user assignments

4. Notify team of changes

Cost Management

Track monthly costs per device:

• SIM plan: $10-30/month

• Device cost (amortized): $3-10/month

• Electricity: ~$2/month per device

• Total: ~$15-42/month per device

ROI Calculation:

• Cost per device: ~$30/month

• Capacity: 100-250 messages/day = 3,000-7,500/month

• Equivalent Twilio cost: $22-56/month (at $0.0075/msg)

• Break-even or better, plus benefits of personal number

Security

Protect your devices and SIMs:

• Use screen locks on all devices

• Store devices in secure location

• Don't share authentication credentials

• Monitor for unauthorized access

• Regularly review message logs for anomalies

---

Troubleshooting Multi-SIM Setups

Message Sent from Wrong Number

Problem: Contact receives message from different number than they expect.

Cause: Wrong user logged in, or contact has wrong tag.

Solution:

1. Check contact's current device tag

2. Ensure tag matches the number they've been messaging

3. Use "Login As" to switch to correct user before replying

4. Or: Use Multi-SIM Reply Override feature

Conversations Split Across Devices

Problem: Same contact has conversations in multiple devices/threads.

Cause: Contact's tag was changed mid-conversation, or manual messages sent from different devices.

Solution:

1. Choose the primary device for this contact

2. Update contact's tag to match primary device

3. Reply only from that device going forward

4. Archive or delete duplicate threads (if possible in GHL)

Uneven Load Distribution

Problem: One device handles much more volume than others.

Cause: Workflow split not configured correctly, or manual tag assignment is unbalanced.

Solution:

1. Review workflow split percentages - should be equal

2. Check "Random" split is truly random (test with small sample)

3. Manually review contact distribution across tags

4. Re-balance by changing tags on some contacts

Device Shows as Offline but Phone is On

Problem: WhatSnap dashboard shows device offline, but phone is powered on with internet.

Cause: Gateway app stopped, network issue, or authentication expired.

Solution:

1. Open WhatSnap Gateway app on device - check status

2. Restart gateway service (stop and start)

3. Check internet connection (WiFi and/or mobile data)

4. Re-authenticate if needed (scan new QR code)

5. Check battery optimization settings (ensure app isn't being killed)

See: SMS Troubleshooting Guide

---

Scaling Beyond 10 Devices

For enterprise-level operations requiring more than 10 devices:

Infrastructure Considerations:

• Dedicated device charging station

• Managed WiFi network for all devices

• Device management software (MDM)

• Centralized monitoring dashboard

Alternative Approaches:

• Consider Twilio SMS for ultra-high volume (1,000+ msgs/day)

• Hybrid: P2P SMS for personal conversations, Twilio for bulk

• WhatsApp for international contacts (no SMS charges)

Contact WhatSnap Support: For enterprise multi-SIM setups requiring 10+ devices, contact [e-mail] for consultation and advanced features.

---

Next Steps

After setting up multiple SMS accounts:

1. Create distribution workflows - Automate contact routing

2. Set up drip campaigns - Maximize your capacity

3. Configure user assignments - Organize team communication

4. Monitor performance - Track deliverability and issues

5. Review compliance - Stay within regulations

Multi-SIM Mastery! With multiple devices properly configured, you can scale your SMS operations significantly while maintaining personal touch and high deliverability.

---

Questions about multi-SIM strategies? Contact WhatSnap support at [e-mail] for personalized guidance.