The default GoHighLevel nurture I keep inheriting from clients looks like this: every step of the workflow sends an email and a text. Same message, two channels, fired in parallel, "so nobody misses it." It feels thorough. It also means you're paying for a text on every single touch, whether or not that touch needed a text — and email costs you effectively nothing per send.
Full disclosure: I work for ReadySMS, so I have a horse in the SMS-billing race. But the honest version of this argument reduces your SMS spend, which is a weird thing for an SMS company to publish. I'd rather you send fewer, better texts and stick around than blast every step and blame the channel when the bill lands.
Why "both channels, every step" is the expensive default
Email in GHL is basically free at the margin — you're paying a flat sending cost that doesn't scale with your text bill. SMS is metered per segment. On ReadySMS Standard that's $0.02/segment plus the $0.0045 carrier pass-through, so $0.0245 all-in for a single 160-character GSM-7 message. (If you don't know why 160 is the magic number, that character cliff is worth reading — one wrong character doubles the send.)
Here's the thing most agencies never audit: on a nurture sequence, most steps do not need a text. A "here's the guide you downloaded" delivery step, a "day 3 educational tip," a "case study we thought you'd like" — those are email jobs. Email's whole strength is longform, low-urgency, skimmable content. Firing an SMS alongside each one is paying premium delivery for content that had no time pressure.
The two moments that genuinely justify a text:
- Time-critical steps — appointment reminders, "your slot is held for 15 minutes," webinar-starting-now, expiring offer.
- Email-failed steps — the contact didn't open, didn't click, bounced, or unsubscribed from email. Now SMS earns its cost as a fallback, not a duplicate.
The channel-branch pattern
Instead of parallel send-both, you branch. The structure:
- Send the email step.
- Wait a realistic window (I use 12–48 hours depending on urgency).
- If/Else condition: did the contact open or click the email?
- Yes → they engaged. No SMS. Continue.
- No → now fire the SMS as a fallback nudge.
For genuinely time-critical steps you skip the branch and send SMS immediately — but those are a small minority of a nurture. Everything else gets the wait-and-check.
This is the same discipline that stops the double-texting problems I've written about in the 4 GHL workflow mistakes that double-text your contacts. Branching by engagement isn't just cost hygiene — it stops the "why did I get a text and an email for the same thing" annoyance that quietly drives opt-outs.
Worked math: a 5,000-contact, 6-step nurture
Let's price both versions. Assume 5,000 contacts, a 6-step nurture, and single-segment (160-char) texts. I'll use a realistic 45% email engagement rate — meaning 55% of contacts don't open a given email and would trigger the SMS fallback.
Version A — send both on every step
Every contact gets 6 texts, no branching.
`` 5,000 contacts × 6 steps × 1 segment × $0.0245 = 30,000 segments × $0.0245 = $735.00 ``
Version B — branch: SMS only on non-engagers, plus 2 truly time-critical steps
Say 2 of the 6 steps are time-critical (SMS to everyone), and the other 4 are email-first with an SMS fallback only for the ~55% who didn't engage.
Time-critical steps (all 5,000): `` 5,000 × 2 steps × 1 segment × $0.0245 = $245.00 ``
Fallback steps (only the ~55% non-engagers): `` 5,000 × 0.55 × 4 steps × 1 segment × $0.0245 = 11,000 segments × $0.0245 = $269.50 ``
Version B total: $514.50.
That's not "halved" in this exact scenario — it's about a 30% cut ($735 → $514.50). To actually halve it, you either raise your email engagement (better subject lines shrink the fallback pool) or you recognize that fewer of your 6 steps are truly time-critical than you assumed. Push it to 1 time-critical step and a 40% fallback rate:
`` Time-critical: 5,000 × 1 × $0.0245 = $122.50 Fallback: 5,000 × 0.40 × 5 × $0.0245 = $245.00 Total: $367.50 ``
Now you're at $367.50 vs $735 — exactly half. The lever isn't magic; it's honesty about which steps needed a text.
| Scenario | SMS segments/mo | Monthly SMS cost | vs. send-both |
|---|---|---|---|
| Send both, every step | 30,000 | $735.00 | — |
| Branch, 2 time-critical + 55% fallback | 21,000 | $514.50 | −30% |
| Branch, 1 time-critical + 40% fallback | 15,000 | $367.50 | −50% |
Run those against your contact count and engagement rate in the cost calculator before you commit to a rebuild.
Watch the segment count, not just the send count
Halving sends only halves cost if every message is one segment. The trap: your fallback SMS is longer than your reminder SMS, or somebody dropped an emoji into the template. A 😊 pulls the whole message into unicode encoding, which cuts the per-segment limit to 70 characters — so a message you thought was one segment is suddenly three. That's the emoji tax, and it quietly undoes your branching savings.
Before you launch the new structure, character-count every SMS template. Trimming a fallback from 165 to 150 characters can take it from 2 segments to 1 and cut that step's cost in half again — I've watched a 12-character rewrite do exactly that.
Where ReadySMS's GHL integration makes this cleaner
The branch logic lives entirely in your GHL workflow builder — you don't need ReadySMS to build it. What the native GHL integration gives you is the accounting that makes the savings legible:
- Two-way sync per location/sub-account, so each client's fallback sends stay isolated and you can see exactly which sub-account's texts you cut.
- Transparent per-segment billing with the $0.0045 carrier fee itemized separately, not rounded into a fuzzy per-message rate. When you tell a client "we cut your SMS 30% by branching," you can point at the segment count and prove it.
- Automatic Growth pricing — if the account clears 50,000 segments in a calendar month, the per-segment rate drops to $0.016 automatically. Branching pushes you under that threshold, which is fine; the point is the number is honest either way.
- Automatic STOP handling and quiet-hours enforcement, so your fallback SMS doesn't fire at 11pm or to someone who already opted out — the branch logic and the compliance layer don't fight each other.
One caveat: if your GHL email deliverability is poor to begin with, "email-first" is building your nurture on sand. Fix the email domain warmup and authentication first, or your fallback pool balloons and you're back to texting nearly everyone anyway.
The rebuild, step by step
- Audit every step. Label each one time-critical or not. Be strict — "day 5 educational email" is not time-critical.
- Time-critical steps → SMS immediately (or SMS + email if you want belt-and-suspenders on genuinely urgent moments).
- Everything else → email first, wait, then branch on open/click. SMS fires only in the No branch.
- Character-count every template. Get fallback texts to one segment. Kill decorative emojis.
- Add guardrails so a contact can't get double-fired by overlapping workflows — here's the duplicate-send guardrail setup.
- Measure for a month. Compare segment counts before and after in your ReadySMS billing view.
The takeaway
"Send both on every step" isn't thorough — it's untuned. Email carries the low-urgency load for basically nothing; SMS earns its per-segment cost on the two jobs it's actually best at: time-critical moments and reaching the people email couldn't. Branch your nurture on engagement, trim your templates to one segment, and a 5,000-contact sequence goes from $735 to somewhere between $370 and $515 a month with, if anything, better engagement because you stopped annoying people who already opened the email.
If you want to price your own nurture before rebuilding anything, the calculator takes your real contact count and engagement rate. And if you're weighing providers for the GHL side of this, the 2026 buyer's guide lays out the tradeoffs without the hard sell.