Features

iMessage Sequences and Automated Follow-Up

The short answer

An iMessage sequence is a multi-step series of blue-bubble texts that your CRM sends on a schedule you set, with a delay between each step, a branch on whether the contact replied, and a stop the moment they do. Blue Reacher is the send channel underneath it, so your workflow keeps its triggers, delays, and conditions while every step goes out as an iMessage. Follow-up is where the money sits, and unlimited messages, with pacing only on new conversations at up to 50 opted-in / 30 cold per line per day, mean a seven-step sequence costs what a one-step send costs.

$249 per line per month, published No A2P registration required 50 opted-in / 30 cold new contacts a day, unlimited replies

Key takeaways

  • A multi-step series of texts that fires automatically from your CRM on your schedule.
  • Most people who eventually answer don't answer the first message.
  • A sequence step is a message body with merge fields resolved at send.
  • A sequence stops the moment the contact does something that makes the next message wrong.
  • Post-call sequence starts when a call ends without close.

How a message falls back

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.

What is an iMessage sequence?

A multi-step series of texts that fires automatically from your CRM on your schedule. Each step has its own message, delay, and condition. Every step lands in one thread, reading like step five from someone already texting the contact.

  • A sequence tracks each contact and reacts to what they do. Two contacts entering same day can be on different paths by Thursday. Blue Reacher carries send and reply; your CRM carries branching. No second tool to sync.
  • Entry trigger: a tag, a pipeline stage change, a form submission, an appointment status, or an API call
  • Steps and delays: message bodies with merge fields your CRM resolves at send time, spaced by minutes, hours, or days
  • Branches: different next steps on reply, no reply, or a CRM field change
  • Exits: reply, opt-out, booking created, deal closed, or the last step sending
  • Send action: Blue Reacher fires each step over iMessage, with RCS then SMS fallback

Follow-up roughly doubles reply rates

Most people who eventually answer don't answer the first message. Woodpecker's 20M email analysis (June 2026) shows 3-5 follow-up steps at 8.3% reply rate versus 4.1% for no follow-up. That's cold email baseline.

  • iMessage changes the math: 98% open, 90% read in three minutes, 2-3x cold email reply rates. Unlimited messages at $249 a month, paced at 50 opted-in / 30 cold new contacts a day, means step seven costs what step one did. Step count limited only by judgment about conversation.

Steps, delays, and branches: the three controls

A sequence step is a message body with merge fields resolved at send. Delays run in minutes, hours, or business days, clamped to the contact's timezone so 4am waits for morning. Branches read state and pick the next step on conditions: replied, booked, tag added, stage moved, payment received.

  • Blue Reacher attempts iMessage first, falls back to RCS then SMS. Replies return via webhook with from, content, channel, and external_id. Branching never needs to know which channel carried a step.

What stops a sequence?

A sequence stops the moment the contact does something that makes the next message wrong. Reply is the primary stop: the inbound message cancels remaining steps. Stop-on-reply belongs on every sequence, or step four lands after they've already answered.

  • Opt-out ends everything. Flags the contact record, pulling them out of every sequence. Booking, closed deal, and payment received are other exits. A rep can pull someone by hand when a reply says something branch logic would miss.
Sequences at every funnel stage recover traffic you paid for

Sequences at every funnel stage recover traffic you paid for

Cold outbound is the smaller return. Bigger half is converting traffic already purchased. A paid lead dark after one email is more expensive than a cold prospect who never replied.

  • Top: cold outbound, reactivation, speed-to-lead at 60 seconds post-form. Middle: confirmations and reminders. Bottom: no-show recovery, post-call follow-up, payment reminders. For booking funnels, reminder and recovery sequences pay for the line first.

Top

Sequence
Cold outbound
Typical shape
5 to 6 steps over 14 to 21 days, branch on reply

Top

Sequence
Speed-to-lead
Typical shape
4 steps in the first 24 hours, stop on reply

Middle

Sequence
Confirmation and reminders
Typical shape
3 steps: booking, 24 hours before, 1 hour before

Bottom

Sequence
No-show recovery
Typical shape
4 steps over 7 days, branch on rebook

Bottom

Sequence
Post-call follow-up
Typical shape
5 steps over 14 days, branch on objection tag

Post-sale

Sequence
Review and referral activation
Typical shape
2 to 3 steps timed to an onboarding milestone

Those are our assumptions. The Blue Funnel Map runs the same arithmetic on the funnel you actually have, and you keep the map either way.

Run these numbers on your funnel
Post-call and no-show sequence mechanics

Post-call and no-show sequence mechanics

Post-call sequence starts when a call ends without close. Five steps over two weeks: recap plus objection answer in 30 minutes, specific question next morning, customer proof on day four, deadline or pricing on day eight, clean either-or on day fourteen.

  • No-show sequence runs tighter: assume-something-came-up with rebook link at five minutes post-start, two concrete times at two hours, shorter ask next morning, async alternative on day seven. Pricing objection routes to ROI math; timing objection parks and re-enters at 90 days.
Three decisions to set up a sequence

Three decisions to set up a sequence

One: what enrolls. Two: what steps say. Three: what pulls them out. GoHighLevel is native; your triggers and delays stay in your workflow. Others connect via REST API at https://api.bluereacher.com/v1/messages with Bearer auth.

  • White-glove activation provisions your line; nothing to install, no A2P required. $249 per month or $1,949 per year, unlimited iMessages with new conversation pacing at 50 opted-in / 30 cold per line per day. Mobile validation at $0.03 per contact from 700M+ database, billed monthly.

Frequently asked questions

How many follow-up steps should an iMessage sequence have?

Three to five follow-ups: 8.3% reply rate versus 4.1% for no follow-up (Woodpecker, 20M emails, June 2026). iMessage teams run 5-6 steps over 2-3 weeks for cold outbound, 3-4 over a week for post-call and no-show. Unlimited messages, paced at 50 opted-in / 30 cold new contacts a day; step count is a judgment call.

Does a sequence stop automatically when someone replies?

Yes, once stop-on-reply is turned on, and it belongs on every sequence you build. The inbound message arrives through the Blue Reacher webhook, your workflow cancels the remaining steps, and the thread routes to the assigned rep. Branch conditions can also route on what the reply says, so "send pricing" and "call me Tuesday" take different paths.

Do I need A2P registration to run iMessage sequences?

No A2P registration required. Blue Reacher sends over iMessage on a dedicated line provisioned during white-glove activation, so there is no carrier campaign approval process waiting on your first send. Nothing gets installed on your side and your team keeps working inside the CRM they already use.

What happens if a contact is not on iMessage?

Contacts who cannot receive iMessage get RCS with SMS fallback. Blue Reacher attempts iMessage first, then RCS, then SMS. Replies return via webhook with a channel field. Branching and stop conditions work identically.

Can I trigger sequences from CRM events like a no-show or a closed deal?

Yes, and CRM events are the most common trigger for the sequences that make the most money. Appointment status changing to no-show, a stage moving to proposal sent, a form submitting, a tag being added: any of these can enroll a contact. Inside GoHighLevel this is a native workflow action, and in other CRMs your automation calls the Blue Reacher API.

How do opt-outs work inside a sequence?

Opt-out replies come back through the same inbound webhook as every other reply, so your CRM sees one the moment it lands. Flag it on the contact record instead of inside a single sequence, and it pulls that contact out of every sequence pointed at them and blocks re-enrollment later.

Does Blue Reacher replace my existing GoHighLevel automation?

No. Blue Reacher plugs into GoHighLevel as a native send action inside the workflows your team already built, so triggers, delays, conditions, and reporting stay where they are. What changes is the channel each step goes out on.

Turn one send into a sequence that actually gets answered

Most of the deals a sequence recovers are leads you had already paid for and stopped chasing. Blue Reacher is a B2B iMessage platform that sends blue-bubble texts from your CRM across the entire funnel, driving 2-3x the reply rate of cold email and higher conversion at every step, with no A2P registration required. Your workflow keeps the triggers, delays, and branches, and Blue Reacher sends every step as an iMessage on a dedicated line at $249 per line per month with unlimited messages, paced at up to 50 opted-in / 30 cold new conversations per line per day. White-glove activation gets your line live and your first sequence running, and the $449 setup fee is waived on annual billing. Book your Blue Funnel Map and ask us to open it by text: the messages you get before the call are a sequence doing its job.