Blog / Deliverability

Why Leads Ghost Your Emails but Answer Texts

Saad Khan8 min readDeliverability

TL;DR

Leads ghost email because email is a work queue and your message is losing a priority contest inside it, not because they decided against you. The same buyer answers texts because messages are a conversation surface with near-total open rates and a reply cost of one thumb. The fix is not better subject lines. It is moving the thread to the surface where replying is easy, and asking permission makes that move feel like a courtesy instead of an escalation.

How a message falls backEvery message is attempted as iMessage first, falls back to RCS if the number cannot receive iMessage, and falls back to SMS if it cannot receive RCS, so the message arrives either way.iMessageBlue bubble, read in minutesRCSIf the number is Android and RCS-...SMSIf neither, so it still arrives
Every message is attempted as iMessage first, falls back to RCS if the number cannot receive iMessage, and falls back to SMS if it cannot receive RCS, so the message arrives either way.
On this page
  1. 01Why do leads who showed real interest stop replying to email?
  2. 02Why does the same lead answer a text in minutes?
  3. 03Is texting a B2B lead appropriate, or does it cross a line?
  4. 04How do you move a live thread from email to iMessage politely?
  5. 05What about the leads who already ghosted months ago?
  6. 06Where Blue Reacher fits
  7. 07Frequently asked questions

Why do leads who showed real interest stop replying to email?

Silence is the default output of a saturated queue. Your demo follow-up got skimmed, filed as "answer later," and later never arrived. Email is the most saturated queue in professional life.

You can't copy your way out of a queue position. A sharper subject line moves you from unread to skimmed, but replying is a composed act at a desk. The buyer's day has no room for it. The leak is structural, not copy. You paid for the lead, the interest was real, and the channel is dying.

Why does the same lead answer a text in minutes?

Different surface, different physics. A text lands on the lock screen, gets read almost immediately, and open rates on messages run around 98%, against email open rates that live in the low double digits for outreach. But the open rate is the small half of the story. The real difference is what replying costs.

Replying to an email means opening a composer and writing prose that represents you professionally. Replying to a text means thumbing "yes, Thursday works" while walking to a meeting. The message format gives the buyer permission to be brief, and brief is the only thing their day has room for. The channel where answering is easiest is the channel that gets answers: iMessage outreach runs at 2-3x the reply rate of cold email, and the gap is wider still against a fourth follow-up email that has already been deferred three times.

There is a status mechanic underneath as well. An inbox is where buyers process strangers, so everything in it gets stranger treatment. The messages app is where their actual life happens, colleagues, family, people they know, and a message that lands there inherits the assumption that a person is on the other end. On iMessage specifically, the blue thread carries typing indicators and read receipts, so the exchange feels live in a way email never does. Conversations that feel live get finished. Threads that feel like correspondence get deferred, and deferred is the ghosting you are seeing.

Is texting a B2B lead appropriate, or does it cross a line?

Texting a B2B lead is appropriate exactly when email would be appropriate, with the same consent obligations, and buyers themselves settled the cultural question years ago: deals are negotiated in text threads, investors close rounds over messages, and executives run half their working relationships out of their phone. The line that matters is not the channel. It is whether the message respects the medium it arrives in.

Respecting the medium means three things. Short: under 300 characters, no paragraph blocks, no signature footer. Personal: it names them, names the context, and could not have been sent to anyone else. Low-pressure: one question, answerable with a thumb, with no link and no calendar ask in the first message. A text that reads like an email got lost on the way to the inbox breaks the deal; a text that reads like a colleague checking in makes the seller easier to buy from, which is the whole point.

The compliance line is the same one email lives under, plus telecom rules: appropriate consent, instant opt-out handling, suppression that syncs across every channel you run. None of that changes by channel, and a seller who is sloppy about it on email will be sloppy on text with sharper consequences. Handled properly, the buyer experience is strictly better: fewer, shorter, more answerable messages instead of a lengthening chain of "bumping this to the top of your inbox."

How do you move a live thread from email to iMessage politely?

You ask, and the ask does the selling. Somewhere natural in the email exchange, usually after the first substantive reply or a demo, one line: "Easier to text for scheduling? What's the best number, or feel free to text me at [number]." That is the entire move. It offers convenience rather than demanding attention, it lets the buyer pick the door, and a meaningful share will take it, because they hate the email chain as much as you do.

If the number is already in your CRM from the original form fill, the move is even lighter: reference the live thread in the first text so it arrives as a continuation, not an ambush. "Hey Dana, Saad here, following up on the pricing thread from Tuesday. Figured a text beats email tag. Is the rollout question the main blocker?" The buyer instantly has context, the reply costs one line, and the conversation now lives where replies happen. First texts that name a real prior interaction get treated as conversation; first texts that read like a broadcast get filtered, both by the phone and by the person.

Two rules keep the move clean. Move the conversation, not the volume: the point is one thread that gets answered, not a second channel running the same cadence, so when the text thread goes live the email sequence stops. And demote email, do not delete it: proposals, security docs and anything long still travel by email, announced in the text thread. The thread becomes the spine of the deal; email becomes the filing cabinet. Once a reply lands, sequence automation should halt and a human should own the thread, which is exactly how iMessage sequences handle the handoff.

  • Ask permission in the email thread, or reference the thread explicitly in the first text. Cold channel-switching without context reads as surveillance.
  • First text under 300 characters, one question, no link, no calendar ask.
  • Stop the email sequence the moment the text thread is live. Two channels on one cadence reads as a machine.
  • Keep long-form materials on email, announced in the text thread, so each surface does the job it is good at.
  • Log the channel switch in the CRM so the next rep does not restart the email chain the buyer just escaped.

What about the leads who already ghosted months ago?

Old leads are the best list you own, and almost nobody works it. Every ghosted email thread in your CRM is a contact who showed intent, cost real money to acquire, and went quiet on a channel that was structurally rigged against a reply. Re-approaching them on a channel where replying is cheap routinely revives deals that were marked lost, because lost was never the right label. Unanswered was.

The play is a short, honest re-opener that names the gap without apologizing for it: "Hey Dana, we traded emails about reporting back in April and it went quiet, which usually means timing. Worth a second look this quarter, or should I close the file?" Two touches maximum, replies routed to a human in minutes, and the "close the file" option stated sincerely, because the permission to say no is what makes saying yes easy.

At the scale of a whole dormant segment, that is a list reactivation campaign: pull every contact whose last email went unanswered past ninety days, segment by where the thread died, and run the re-opener over iMessage. It is usually the cheapest pipeline available to a B2B team, because the acquisition cost is already sunk and the only new spend is the channel.

Where Blue Reacher fits

Blue Reacher is the iMessage layer for exactly this motion: dedicated blue-bubble lines your team sends from, set up done-for-you, with unlimited messages on a flat per-line price and no A2P registration required, so the channel is live in days instead of waiting on carrier paperwork. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered. Contacts not reachable over iMessage fall back to RCS then SMS automatically, and the whole thing runs native in GoHighLevel or over REST API and webhooks in any stack.

The broader playbook for running sales conversations on this channel lives at iMessage for sales, and if you want the ghosting math made concrete, the iMessage ROI calculator shows what your current email reply rate is costing against the same list worked over messages.

Frequently asked questions

Why do leads ghost emails even after a good demo?

Because replying to email is a composed act inside an overloaded work queue, and deferral is the queue's default output. The interest is usually still real: your follow-up simply loses a daily priority contest against forty other obligations, gets filed as "answer later," and later never arrives. It is a channel problem before it is a copy problem, which is why better subject lines rarely fix it.

Is it professional to text a B2B lead?

Yes, when consent is handled and the message respects the medium. Buyers already run deals, hiring and investor conversations over text. The professional bar is a short, personal, low-pressure message: under 300 characters, one thumb-answerable question, no link in the first touch. What reads as unprofessional is broadcast copy pasted into a text, not the channel itself.

How do I ask a lead to switch from email to text?

One line in the live email thread: "Easier to text for scheduling? Feel free to text me at this number, or tell me yours." Frame it as convenience, let them choose, and if the number is already in your CRM, open the text by referencing the email thread so it arrives as a continuation. Then stop the email sequence, so the buyer experiences one conversation rather than two cadences.

Do texts really get read more than emails?

Yes, by a wide margin. Open rates on text messages run around 98% because messages land on the lock screen and get read within minutes, while outreach email opens sit far lower and arrive on the buyer's triage schedule. The bigger gap is replies: iMessage outreach runs at 2-3x the reply rate of cold email, because answering a text costs a thumb instead of a composed paragraph.

Do I need A2P 10DLC registration before texting my leads?

On US SMS rails, yes: brand and campaign registration precede your first send and the process runs weeks. On a Blue Reacher iMessage line no A2P registration is required, with automatic RCS then SMS fallback for contacts outside iMessage. TCPA consent and opt-out rules apply identically either way; our A2P 10DLC guide covers the registration path if you also run SMS traffic.

Keep reading

More on deliverability

4 min read

Why Your Business Texts Aren't Delivering (and What Actually Fixes It)

The dashboard says sent, replies stopped, and nobody told you why. A field guide to silent SMS failure: how to tell unregistered blocking from content filtering from velocity flags, the fixes in order of effort, and when the honest answer is that the rails are the problem.

Put this on your pipeline

Blue Reacher runs outbound iMessage for B2B sales teams, from your CRM, with setup handled for you.

Book a demo