Your day-11 trial-expiry email went out at 9:04 a.m. It landed in a work inbox that already had 40 unreads by 10 a.m., got shoved below three Slack digests and a calendar invite, and by the time the trial actually expires on day 14 it's on page two of an inbox nobody scrolls. The same nudge, sent as a text, gets read inside a few minutes — most people open a text before lunch whether they meant to or not.
That's not a reason to move everything to SMS. It's a reason to map your trial lifecycle by timing sensitivity and put each message on the channel that fits. Full disclosure: I work for Ready, an SMS platform. So take the channel comparisons as coming from someone with a horse in the race — but the framing here is the honest version, including the parts where email wins.
The core principle: match urgency to channel latency
Email and SMS aren't competing on quality. They're competing on latency and attention. Rough industry approximations, framed as such:
- Marketing email open rates hover around 20–30%, and the median open happens hours after send — sometimes the next day.
- Opted-in SMS gets read by the vast majority of recipients, usually within minutes.
So the rule writes itself. When a conversion moment is time-boxed — the trial ends Friday, the feature-gate just fired, the card just failed — SMS is the channel because the window is measured in hours. When the message is detail-heavy and not clock-dependent — a feature walkthrough, a case study, a pricing breakdown — email carries it better because nobody wants a 600-character multipart text explaining your API rate limits.
The conversion-window map
Here's a 14-day trial mapped by moment, with the channel each moment should lead on and why.
| Trial moment | Timing sensitivity | Lead channel | Why |
|---|---|---|---|
| Day 0 — signup / welcome | Low | Email (SMS optional) | Detail-heavy; sets expectations, links to docs |
| Day 1–2 — activation nudge | Medium | SMS | A setup reminder that lands fast beats a day-5 email |
| Day 3–5 — feature discovery | Low | Room for screenshots, walkthroughs | |
| Feature-gate hit (event-triggered) | High | SMS | Fires in-the-moment; catch intent while it's warm |
| Day 7 — mid-trial check-in | Medium | Email + SMS | Email for value recap, SMS for a "stuck? reply here" |
| Day 11 — expiry warning | High | SMS | Time-boxed; email gets buried |
| Day 13 — final call | High | SMS | Hours left; SMS is the only channel that lands in time |
| Post-expiry winback | Medium | SMS then email | SMS for the fast ask, email for the offer detail |
Two moments carry SMS the hardest: the feature-gate hit and the expiry cliff. Both are clock-driven and both die in an inbox.
The feature-gate hit is the most underused SMS moment
When a trial user bumps into a paywall — they tried to export, invite a teammate, hit the row limit — that's the highest-intent second of the whole trial. They want the thing. An in-app banner catches them only if they stay on the page, and an email arrives after the impulse cools. A text sent within a minute of the event keeps the intent warm.
We wrote a whole piece on where SMS reaches free users who never log back in — the freemium-limit SMS vs. in-app comparison — and the feature-gate moment is the sharpest version of it.
Where email genuinely wins — say it plainly
SMS is not a universal upgrade. Email should carry:
- The onboarding walkthrough. Screenshots, embedded video, a checklist. That doesn't compress to 160 characters.
- The pricing comparison. Feature-by-feature tables belong in email.
- The case study / social proof. Long-form persuasion is an email job.
- Receipts and invoices. Legal record, formatting, attachments — email.
If you try to force those into SMS, you get 4-segment texts that read like a wall and cost 4× to send. Segment math: a 175-character message with a single emoji drops to unicode encoding (70 chars/segment), so it becomes 3 segments. At Ready's Standard rate that's 3 × ($0.02 + $0.0045) = $0.0735 per recipient — for a message that would've been a better email. Keep SMS short and event-driven; that's where the economics and the attention both line up.
The template pack (with the consent footnotes teams forget)
These are the short, time-sensitive texts. Each assumes the recipient opted in to transactional/lifecycle messaging at signup — which is the part most SaaS teams skip and then wonder why delivery drops. Notes below each one.
Day 2 — activation nudge
Hey {{first}}, it's {{product}}. Noticed you haven't connected your data source yet — it's the 2-min step that makes everything click. Need a hand? Just reply. Txt STOP to opt out.
Consent note: lifecycle message to an opted-in trial user. STOP language present. Fine under a properly registered campaign.
Feature-gate hit (event-triggered)
{{first}}, looks like you just hit the export limit on the free trial — that unlocks on any paid plan. Want me to send the upgrade link? Reply YES. STOP to opt out.
Consent note: triggered by a user action, not a blast. Still counts as marketing-adjacent — register it under a use case that matches, or delivery silently drops. See the use-case mismatch post.
Day 11 — expiry warning
{{first}}, your {{product}} trial ends {{date}}. Your setup + data stay put if you pick a plan before then: {{link}}. Questions? Reply here. STOP to opt out.
Day 13 — final call
Last day on your {{product}} trial, {{first}}. After tomorrow your workspace pauses (nothing's deleted for 30 days). Keep it going: {{link}}. STOP to opt out.
Post-expiry winback (send once, then stop)
{{first}}, your trial wrapped up but your data's still saved for a few more weeks. Come back within 7 days and I'll extend it: {{link}}. STOP to opt out.
The reply-based ones ("reply YES") only work if inbound actually lands somewhere a human sees. In Ready, replies show up in a unified inbox and — for connected accounts — sync straight into GoHighLevel, so a "YES" turns into a conversation instead of vanishing. If you want the fuller set with more variants, we published 7 trial-expiry SMS templates with the consent footnotes.
Wiring it up without babysitting sends
None of this scales if someone's manually firing texts on day 11. The pattern:
- Event triggers for the feature-gate hit — fire the SMS off the product event, not a schedule.
- Time-boxed triggers for day 2, 11, and 13 — anchored to each user's trial start, not a global calendar date.
- Suppression so a user who converts on day 12 never gets the day-13 "last day" text. That's the most common self-own: texting someone who already paid.
Ready's automations handle the triggers and the automatic STOP handling means an opt-out on one campaign propagates everywhere — the user can't get re-messaged across a different sequence. Quiet-hours enforcement holds sends outside permitted local hours, which matters when your day-13 trigger would otherwise fire at 11 p.m. for a West Coast user.
The compliance part you can't skip
SaaS lifecycle SMS runs on registered 10DLC. Brand + campaign registration inside Ready runs roughly ~$10/mo per brand and ~$20/mo per campaign, approval typically 1–3 days. Skip it and carriers filter your traffic — meaning your perfectly-timed expiry text never arrives, which is worse than an unopened email. If your trial-expiry text and your MFA codes share a number, split them; we covered why that split matters.
The math on whether it's worth it
Say you run 3,000 trials a month and send four single-segment texts to each over the lifecycle. That's 12,000 segments at Standard: 12,000 × ($0.02 + $0.0045) = $294/mo. If those texts convert even 1% more of your trials than email alone — 30 extra paid accounts — and your plan is $40/mo, that's $1,200 in new MRR against $294 in send cost. The ratio holds at almost any reasonable ARPU. The failure mode isn't cost; it's sending the wrong message on the wrong channel, or sending to someone who never consented.
The practical takeaway
Don't replace email. Layer SMS onto the two or three moments where the clock is running — feature-gate hits, the day-11 warning, the day-13 final call — and let email keep carrying the long-form detail. Anchor triggers to each user's trial start, suppress converters, and register the campaign so the messages actually land.
If you want to see how the automations and unified inbox handle the trigger-and-suppress part, the product and pricing page lays it out, and you can start with 2,500 free credits to test a single sequence before you wire up the whole map. Build the feature-gate trigger first — it's the highest-intent moment you're probably not messaging at all.