# iMessage vs SMS for Real Estate Lead Follow-Up

> A GHL Agency's Guide to Running the Test That Ends the Debate

*By BG · Published 2026-03-24T00:00:00.000Z*

**Canonical URL:** https://tuco.ai/blog/imessage-vs-sms-real-estate-lead-follow-up-ab-test
**Tags:** iMessage vs SMS, real estate, lead follow-up, ab testing, GoHighLevel, iMessage automation, real estate marketing

## Summary

iMessage vs SMS real estate lead follow-up A/B test results: iMessage gets 8-15% reply rates vs 1-3% for SMS. Step-by-step GoHighLevel setup to prove it with.

---


**iMessage vs SMS for real estate** lead follow-up is no longer a theoretical debate. It's a testable hypothesis you can prove with your own leads in GoHighLevel this week.

**TL;DR:** Automated SMS is immediately recognizable as bot-sent. Your leads know it. They ignore it. iMessage lands in the same thread as texts from friends and family, gets 98% open rates, and pulls **8-15% reply rates** compared to 1-3% for SMS. This guide shows you how to set up an A/B test in GHL, route iPhone users to iMessage automatically, and track the metrics that matter. If you run a real estate marketing agency and you're tired of watching SMS reply rates collapse, this is the test that ends the argument.

## Why Does Automated SMS Feel So Obvious to Real Estate Leads?

You already know this. Jay knows this. Every GHL agency owner who's sent a follow-up sequence knows this.

**Automated SMS is immediately recognizable as bot-sent.** Why:

- **Green bubble from a 10-digit number** the lead has never seen before
- **Perfect grammar and formatting** that no human texts with
- **Instant timing**. The lead submits a Facebook form and gets a text 4 seconds later
- **[A2P 10DLC filtering](/blog/why-waiting-4-6-weeks-for-a2p-10dlc-approval-is-costing-you-sales-and-what-smart)** adds delivery delays and sometimes appends carrier warnings
- **"Spam Likely" labels** appear on the lead's phone before they even read the message
- **Keyword triggers** like "reply STOP to unsubscribe" scream automation

The lead sees all of this in a fraction of a second. They don't read the message. They don't reply. They might even block the number.

**What happens:** SMS reply rates for Facebook ad leads have dropped to **1-3%** across the real estate agencies we work with. Some are below 1%.

This isn't a copywriting problem. At all. The copy could be perfect. The channel is broken. We covered the underlying delivery gap in [why iMessage outperforms SMS for sales outreach](/blog/why-imessage-outperforms-sms-for-sales-outreach-higher-response-rates-without-th).

## Why Does iMessage Feel Personal When SMS Doesn't?

**The blue bubble changes everything.** This is the psychology that makes an **iMessage A/B test against SMS** worth running.

When a message arrives as iMessage (blue bubble), the recipient's brain processes it differently:

| Signal | SMS (Green Bubble) | iMessage (Blue Bubble) |
|--------|-------------------|----------------------|
| Visual association | Marketing, spam, 2FA codes | Friends, family, personal |
| Delivery indicator | None | "Delivered" / "Read" |
| Typing indicator | No | Yes |
| Carrier filtering | Yes (A2P 10DLC) | No |
| Spam labeling | Common | Never |
| Thread placement | Separate from personal texts | Mixed with personal texts |
| Rich media | Limited MMS | Full photos, links, tapbacks |

**Blue bubbles bypass the mental spam filter.** The lead sees a blue bubble and their brain categorizes it as "someone I know" before they've even read the first word. That split-second categorization determines whether they read or ignore.

This is why **real estate lead follow-up via iMessage** converts at 3-8x the rate of SMS. The message content can be identical. The channel changes the outcome.

## How Do You Set Up an iMessage vs SMS A/B Test in GoHighLevel?

Exact workflow to run a clean **iMessage A/B test** against SMS in GHL. No guesswork. No rebuilt workflows.

### The Test Structure

- **Group A (Control):** Leads receive your existing SMS follow-up sequence
- **Group B (Test):** iPhone leads receive iMessage; Android leads receive SMS
- **Split:** 50/50 random assignment at the workflow trigger level
- **Duration:** 2-4 weeks or 200+ leads per group (whichever comes first)
- **Primary metric:** Reply rate within 24 hours

### Step-by-Step GHL Workflow Setup

**Step 1: Create a new workflow triggered by your Facebook lead form submission.**

Use the same trigger you have now. New lead comes in from Facebook, workflow fires.

**Step 2: Add a 50/50 random split.**

GHL's "If/Else" branch with a random condition works. Or use a custom field that alternates between "A" and "B" on each new contact.

**Step 3: Group A. Your existing SMS sequence.**

No changes. This is your control. Same copy, same timing, same everything.

**Step 4: Group B. Add the iMessage routing webhook.**

Before sending any message, hit the Tuco AI **"check iMessage" API** with the lead's phone number. This is a single HTTP request:

```
GET https://api.tuco.ai/v1/check-imessage?phone=+15551234567
```

The API returns the phone number and a boolean `imessage` field (`true` if the number is registered on iMessage, `false` if not).

**Step 5: Route based on the response.**

- If `imessage: true`: send via Tuco AI's iMessage webhook (blue bubble delivery)
- If `imessage: false`: fall back to your existing GHL SMS action

**Step 6: Tag contacts with their group and delivery channel.**

Tag with `ab-group-a`, `ab-group-b`, `sent-imessage`, or `sent-sms`. You'll need these for analysis.

**Step 7: Let it run for 2-4 weeks without touching it.**

Don't optimize mid-test. Don't change copy. Let the data accumulate.

## How Does the "Check iMessage" API Route iPhone Users Automatically?

This is the technical piece that makes the whole test work. Without it, you'd be guessing which leads have iPhones.

**The Tuco AI "check iMessage" endpoint** queries Apple's iMessage registration database in real time. When someone activates an iPhone, their phone number gets registered with Apple. The API checks that registration.

### The Routing Logic

```
Lead submits Facebook form
  → GHL workflow triggers
  → 50/50 split
  → Group B: HTTP request to check-imessage API
    → iPhone detected: send iMessage via Tuco webhook
    → Android detected: send SMS via GHL native action
  → Group A: send SMS via GHL native action (control)
```

**Key detail:** The API check adds about 200ms of latency. Your lead won't notice. But you get deterministic routing. No guessing, no wasted iMessages to Android numbers.

### What Percentage of Real Estate Leads Have iPhones?

In the U.S., **iPhone market share is 55-60%**. For real estate leads from Facebook ads, it skews higher (**60-70%**) because Facebook's mobile app usage is heavily iOS.

That means for every 100 leads in Group B:
- **60-70 get iMessage** (blue bubble, no filtering, high reply rate)
- **30-40 get SMS** (same as control)

This is enough volume to see a statistically significant difference within 2-3 weeks for most agencies running 20+ leads per day.

## What Metrics Should You Track in the A/B Test?

Track these five metrics. Everything else is noise.

| Metric | What It Tells You | How to Measure |
|--------|-------------------|----------------|
| **Reply rate (24hr)** | Channel effectiveness | Replies / messages sent |
| **Reply rate (7-day)** | Longer-term response pattern | Replies / messages sent |
| **Conversation-to-appointment rate** | Lead quality impact | Appointments / replies |
| **Cost per booked appointment** | ROI comparison | Total cost / appointments |
| **Speed to first reply** | Response urgency | Timestamp of reply - timestamp of send |

### How to Pull These Numbers in GHL

- Use **contact tags** to segment Group A vs Group B
- Use **conversation reports** to count replies per tag
- Use **pipeline stage tracking** to measure appointments booked
- Export to a spreadsheet for the final comparison

**Don't overcomplicate it.** Reply rate alone will tell you 80% of what you need to know. If iMessage reply rate is 4-5x higher than SMS, the downstream metrics will follow.

## What Benchmarks Should You Expect?

Benchmarks from real estate agencies running iMessage follow-up through Tuco AI:

| Metric | SMS (Automated) | iMessage | Difference |
|--------|-----------------|----------|------------|
| **Reply rate** | 1-3% | 8-15% | 3-8x higher |
| **Open rate** | 40-55% | 98% | ~2x higher |
| **Spam/filter rate** | 20-40% | 0% | Eliminated |
| **Speed to reply** | 2-6 hours | 5-15 minutes | 10-20x faster |
| **Appointment booking rate** | 0.5-1% of sends | 3-6% of sends | 4-6x higher |
| **Cost per message** | $0.02-0.08 | $0.10-0.15 | Slightly higher |

iMessage costs 2-3x more per message, but delivers 4-8x more replies. Your cost per reply drops by 50-70%. Your cost per booked appointment drops further because iMessage replies tend to be higher-intent. The lead is actually having a back-and-forth, not just sending a one-word response.

## Sending Limits for Real-Estate Warm Follow-up

If you're reaching out to leads who submitted a Facebook form, that's warm follow-up. But some agencies also run warm follow-up to expired listings, FSBOs, or purchased lists.

**Daily limits and ramp-up matter here.**

### Recommended iMessage Ramp-Up Schedule

| Week | Daily Volume | Notes |
|------|-------------|-------|
| Week 1 | 20-30/day | Warm up the Apple ID |
| Week 2 | 30-50/day | Monitor for any delivery issues |
| Week 3 | 50-70/day | Steady state for most agencies |
| Week 4+ | 70-80/day | Max recommended per Apple ID |

**For higher volume:** Add additional Apple IDs. Each Apple ID is a separate sending identity with its own limits. Tuco AI manages the rotation automatically. We wrote a full breakdown of [iMessage follow-up to warm leads limits and ramp-up](/blog/cold-imessage-outreach-what-works-daily-limits-guide).

### Warm Follow-up Limits

- **Expired listings:** Keep messages hyper-relevant. "I saw your listing at [address] expired on [date]" converts because it's specific.
- **FSBOs:** Lead with value. "I have a buyer looking in [neighborhood]" gets replies.
- **Purchased lists:** Lowest reply rates. Still 3-5x better than SMS on the same lists.
- **Daily cap per Apple ID:** Stay at 30-50/day on warm follow-up. Conservative volume protects your sending reputation. Tuco AI does not support first-touch outreach to strangers — only form-fills, ad opt-ins, replied prospects, and existing customers.

## Is iMessage Follow-Up TCPA Compliant?

**Yes, with the same rules as SMS.**

TCPA compliance is about **consent**, not the delivery channel. What you need:

- **Facebook ad leads:** The lead submitted a form with their phone number. This constitutes **express consent** to be contacted. You're good for both SMS and iMessage follow-up.
- **Website form leads:** Same logic. They gave you their number and expected contact.
- **Warm follow-up (expired/FSBO):** These are **business-to-business** communications to licensed agents or public listings. Different rules apply, but keep records of your data source.
- **Purchased lists:** Highest risk. Ensure the list provider certifies opt-in consent. Document everything.

**What doesn't change between SMS and iMessage:**
- Honor opt-out requests immediately
- Don't message before 8 AM or after 9 PM local time
- Keep records of consent for every contact
- Include your identity in the first message

**What's different with iMessage:**
- No A2P 10DLC registration required
- No carrier-level compliance filtering
- No "STOP" keyword requirement (but you should still honor opt-outs)

If you're compliant with SMS, you're compliant with iMessage. The consent requirements are identical. The delivery mechanism is irrelevant to TCPA.

## What Does 50 iMessages Per Day Look Like Over a Month?

Real numbers for a real estate agency sending **50 iMessages per day** to Facebook ad leads.

### Monthly Projection: 50 iMessages/Day

| Metric | Conservative (8% reply) | Moderate (12% reply) | Aggressive (15% reply) |
|--------|------------------------|---------------------|----------------------|
| **Messages sent/month** | 1,100 | 1,100 | 1,100 |
| **Replies received** | 88 | 132 | 165 |
| **Conversations started** | 88 | 132 | 165 |
| **Appointments booked (30% of replies)** | 26 | 40 | 50 |
| **Deals closed (10% of appointments)** | 2-3 | 4 | 5 |
| **Revenue at $8K avg commission** | $16,000-24,000 | $32,000 | $40,000 |
| **iMessage cost (~$0.12/msg)** | $132 | $132 | $132 |
| **Tuco AI platform cost** | $299 | $299 | $299 |
| **Total monthly cost** | $431 | $431 | $431 |
| **ROI** | 37-56x | 74x | 93x |

**Compare this to the same 1,100 messages sent via SMS:**

| Metric | SMS at 2% Reply Rate |
|--------|---------------------|
| Messages sent/month | 1,100 |
| Replies received | 22 |
| Appointments booked | 7 |
| Deals closed | 0-1 |
| Revenue | $0-8,000 |

**The gap is enormous.** Same lead list. Same message copy. Same daily effort. iMessage produces 4-7x more replies, 4-6x more appointments, and potentially 3-5x more closed deals.

At $431/month all-in, you need **one extra deal every 2-3 months** to make iMessage automation wildly profitable. Most agencies see that within the first two weeks.

## How Do You Get Started With the A/B Test This Week?

You don't need to overhaul your GHL setup. You don't need to pause your existing SMS workflows. You need three things:

1. **A Tuco AI account**. gives you the "check iMessage" API and the iMessage sending webhook
2. **A 15-minute GHL workflow edit**. add the webhook, the routing logic, and the contact tags
3. **2-3 weeks of patience**. let the data accumulate before drawing conclusions

**Most agencies see statistically significant results within 10 days** if they're running 20+ new leads per day through the test.

The agencies we work with have already run this test. They know the answer. The question is whether you want to prove it with your own data or keep watching SMS reply rates decline.

**[Book a 15-minute demo](/demo)** and we'll set up the A/B test workflow with you live. Bring your GHL account. We'll have iMessage routing live before the call ends. See [Tuco AI pricing](/pricing) for plan details, or read the full [GHL iMessage integration guide](/integrations/gohighlevel).

---

*Running a GHL agency and want to add iMessage as a service for your real estate clients? Read our guide on [how GHL agencies add $500-2,000/month per client with iMessage automation](/blog/ghl-agencies-add-imessage-revenue-stream).*


## Frequently Asked Questions

### What reply rate should I expect from iMessage vs SMS for real estate leads?

iMessage typically delivers 8-15% reply rates on real estate lead follow-up, compared to 1-3% for automated SMS. The gap is largest on Facebook ad leads where the prospect didn't explicitly opt into text messages.

### How do I route iPhone users to iMessage and Android users to SMS in GoHighLevel?

Use Tuco AI's 'check iMessage' API endpoint. Before sending, hit the API with the lead's phone number. It returns whether the number is registered on iMessage. Route iPhone users to iMessage via webhook, and fall back to SMS for Android users.

### Is sending iMessage for real estate lead follow-up TCPA compliant?

iMessage follows the same consent rules as SMS. If the lead submitted a form on your Facebook ad and provided their phone number, you have express consent to contact them. The delivery channel (iMessage vs SMS) doesn't change the consent requirement.

### How many iMessages can I send per day for real estate outreach?

Start at 20-30 per day per Apple ID and ramp to 50-80 over 2-3 weeks. For agencies managing multiple clients, each client gets a dedicated Apple ID. Tuco AI handles the ramp-up schedule automatically.

### Can I run an iMessage A/B test inside GoHighLevel without changing my existing workflows?

Yes. You add a single webhook step before your existing SMS action. The webhook checks if the number supports iMessage. If yes, it sends via iMessage and skips SMS. If no, your existing SMS workflow fires normally. No need to rebuild anything.