SMS Marketing for SaaS
The few SaaS moments that justify an SMS, consent rules by region, cost per message against email, and how to add SMS without annoying paying customers.
On this page 8 sections
- Which five SaaS moments actually justify a text message?
- Why does everything else belong in email?
- What does consent actually require in the US and the EU?
- What is 10DLC and how long does registration take?
- What does SMS cost against email at 10,000 sends?
- How do you orchestrate SMS alongside an email sequence?
- What are the honest failure modes?
- What to do next
- Frequently asked questions
The short answer
SMS works in B2B SaaS as a transactional channel, not a marketing one. Five moments justify a text: two factor codes and security alerts, the final dunning retry before a downgrade, critical system incidents, meeting reminders inside 24 hours, and field or mobile first products. Everything else belongs in email. SMS costs roughly 40 to 100 times more per send, requires explicit consent under TCPA and GDPR, and needs 10DLC carrier registration before a single message leaves.
Key points before you start
Most SaaS teams discover SMS the same way. Someone quotes a 98 percent open rate in a growth meeting, the channel gets added to the roadmap, and six months later there’s a Twilio bill, a 10DLC registration nobody finished, and a support ticket from a customer asking how to stop the texts. The open rate was real. The value was not.
Here’s the position this page takes. SMS earns a place in five specific SaaS moments, all of them either transactional or time-bound, and every other message you were planning to text belongs in email. A promotional text to a work mobile number spends trust you cannot buy back, and the click through almost never covers the cost.
Which five SaaS moments actually justify a text message?
Two factor codes, the final dunning retry, critical incidents, meeting reminders inside 24 hours, and field or mobile first products. That’s the list. Each one shares the same two properties: the message is time sensitive to the minute, and the recipient’s next action happens on the phone they’re holding.
Two factor and security alerts. New device sign in, password reset, admin permission change. Nobody resents these. They’re the reason the number is on file, and they’re the reason the number stays on file.
Payment failure on the final retry. Stripe’s smart retry logic usually gives you three or four attempts over about two weeks. Run the first notices through email. Send exactly one SMS before the last attempt, when the account is hours from losing access. Updating a card takes half a minute on a phone and the recovery rate on that single message tends to be several times the email that preceded it.
Critical system incidents. If your product is a monitoring tool, a payments rail or anything an on call engineer depends on, a text is the correct medium for a Sev 1. Datadog and PagerDuty built entire notification products on this assumption. If your product is a design tool, your outage is not a Sev 1 for the customer’s phone.
Meeting reminders inside 24 hours. A Calendly style reminder 60 minutes before a demo measurably reduces no shows. That’s a transactional message tied to an appointment the person booked themselves.
Field and mobile first verticals. Construction software, home services dispatch, trucking, restaurant scheduling. If your user’s job happens away from a desk, email is the wrong assumption and SMS is the primary channel, not a supplement.
The sixth use case people invent
Product announcements. Feature launches. Webinar invites. Trial day three nudges. Every one of these is an email in a costume. If the message still makes sense when read four hours later, it was never an SMS.
Why does everything else belong in email?
Because email is the channel your buyer has consented to for commercial contact, and because the economics are not close. A work mobile number is a personal device with a corporate SIM. The person carries it to dinner. Your upgrade prompt arrives next to a message from their kid’s school.
Email also gives you room to argue. A good subject line plus 150 words of context plus a link beats 160 characters every time for anything persuasive. SMS has no formatting, no preview text, no sender reputation you can improve, and no second chance if the first line lands badly.
The one measurable thing SMS wins on is speed to read. That advantage only matters if the deadline is real.
Newsletter launch list
The Friday SaaS Marketing Brief
Join the list for the upcoming SaaS Marketing Brief. Get the marketing planning worksheet immediately.
What does consent actually require in the US and the EU?
In the United States, the TCPA distinguishes informational messages, which need prior express consent, from marketing messages, which need prior express written consent with clear disclosure next to the opt in. Statutory damages run per message, which is why the plaintiff bar pays attention to bulk sends. There is no legitimate interest carve out that saves a promotional text.
Under GDPR, an SMS opt in has to be freely given, specific, informed and unbundled. Consent for the newsletter does not extend to texts. You need to log the timestamp, the wording shown, and the source, the same record keeping discipline described in our email compliance checklist.
Three rules that survive both regimes:
- Collect the phone number for a stated purpose and use it only for that purpose.
- Send a confirmation message that names your brand and includes STOP instructions.
- Honour STOP, UNSUBSCRIBE and END immediately and permanently, across every campaign, not just the one that triggered it.
Two factor numbers are not a marketing list
The single most common compliance failure in SaaS is reusing the security phone number for product messaging. It is a consent violation and it teaches your most security conscious accounts to disable two factor. Store the number with a purpose flag and enforce it in code, not in a policy document.
What is 10DLC and how long does registration take?
10DLC is the framework US carriers use to authorise application to person traffic from standard 10 digit numbers. You register a brand, then register each campaign with a use case, sample message copy and an opt in description. Unregistered traffic gets filtered, throttled or silently dropped.
Budget one to three weeks. Some use cases clear in days, others bounce back twice because the sample copy doesn’t match the declared use case. Toll free verification is a separate path with its own review. Short codes cost a great deal more and take longer, and almost no SaaS needs one.
Outside the US the rules differ again. The UK and most of the EU allow alphanumeric sender IDs, which is why your bank’s texts say the bank’s name. India requires DLT registration with pre-approved templates. If you’re sending across borders, build the country logic before you build the campaigns.
What does SMS cost against email at 10,000 sends?
Roughly 80 to 110 dollars versus roughly 50 cents. Here’s the comparison at list prices, assuming single segment messages and a mid tier ESP plan.
| Channel | Cost at 10,000 sends | Setup lead time | Best used for |
|---|---|---|---|
| US SMS via Twilio | $79 plus carrier fees, roughly $80 to $110 | 1 to 3 weeks for 10DLC | Security, final dunning, Sev 1 incidents |
| Transactional email | Under $1 in send fees | 1 to 2 days for DNS auth | Receipts, resets, onboarding, dunning steps 1 to 3 |
| Marketing email | Under $1 in send fees on most plans | Same DNS setup | Everything promotional |
| WhatsApp Business API | Roughly $0.01 to $0.09 per conversation by country | 2 to 4 weeks including template approval | International and consumer adjacent SaaS |
~100x
Cost multiple of SMS over email per message sent in the US
Twilio and major ESP list pricing, September 2026
That multiple is the whole argument. A message has to be worth a hundred emails to justify the channel. A password reset is. A feature announcement is not. Our email revenue calculator is a useful sanity check here: run the same expected conversion rate through both cost structures and the promotional case collapses immediately.
The cost that doesn’t show on the invoice is bigger anyway. Every unwanted text raises the probability that someone removes their number entirely, which takes your security alerts and your dunning save with it.
Editable working copy
Get this checklist as a working file
Save the checks on this page as a working copy and assign an owner, status and evidence for each action.
How do you orchestrate SMS alongside an email sequence?
Make the text a pointer, never a copy. If both channels carry the same message, you’ve doubled the cost and halved the trust, and the reader learns that one of the two is redundant.
Adding SMS to an existing lifecycle program
- Classify every existing message
Split your lifecycle map into transactional and promotional, using the distinction covered in transactional vs marketing email. Only the transactional column is a candidate.
- Pick one use case to start
Final dunning retry is the usual best first test because the revenue is measurable and the message is obviously in the customer's interest.
- Register 10DLC before you build
Submit brand and campaign registration first. You will know it worked when your sample messages clear review without a resubmission.
- Collect consent at a purpose specific moment
Add the number with an explicit checkbox in billing settings, not at signup. Log the wording and timestamp.
- Set a global frequency ceiling
One promotional-adjacent SMS per user per 30 days, enforced in your messaging platform, not by convention. Transactional messages sit outside the cap.
- Deduplicate against email
Suppress the email if the SMS already resolved the action, and never fire both within 15 minutes. Check the event log to confirm no user received both.
- Measure recovery, not opens
For dunning, the only metric is cards updated within 48 hours. Compare against a holdout group that gets email only.
- Review opt outs monthly
If STOP rates exceed 2 percent on any campaign, the message is wrong or the consent was weak. Pause it rather than tuning the copy.
Most messaging platforms handle the mechanics. Customer.io, Braze and Iterable all treat SMS as a channel inside the same journey, which is what you want, because the suppression logic has to live in one place. If your stack can’t express “send SMS only if the email from step three went unopened for 48 hours”, fix that before you add the channel, and read our platform comparison for where the differences bite.
A dunning sequence that works
Day 0 email on first failure. Day 3 email with a one click card update link. Day 7 email plus in app banner. Day 12, four hours before the final Stripe retry, one SMS: brand name, the fact that access ends tomorrow, a short link, STOP to opt out. Then stop. No day 14 follow up text.
What are the honest failure modes?
The first is drift. SMS starts as dunning only, then someone asks to add a webinar reminder, then a launch, and within two quarters it’s a promotional channel with a transactional consent record. Write the allowed use cases into the campaign registration and make adding one require the same review as a new campaign.
This second is international breakage. A US built flow hits a German customer, gets filtered for lacking a local sender ID, and nobody notices because SMS failures are quiet. Monitor delivery rates by country weekly.
The third is cost creep from segments. Anything over 160 GSM characters splits into multiple billed segments, and a single emoji forces the whole message into UCS-2 encoding, cutting the limit to 70 characters. Long messages cost two or three times what you budgeted.
The fourth is the one nobody plans for. Your best accounts have the most senior users, and senior users are the least tolerant of unexpected texts. The people you most want to keep are the first to opt out. That asymmetry is why this page argues for restraint rather than optimisation, and it’s the same pattern behind several of the email mistakes that quietly erode list health.
What to do next
Audit what you already send. Take your lifecycle map, mark every message that is genuinely time critical to the minute, and see how few survive. If the answer is one, build that one properly.
Then start 10DLC registration this week, because it’s the long pole, and set up the consent record before you write a single message. Compare your current email performance against the benchmarks first. In most accounts the honest conclusion is that email is underused rather than that SMS is missing, and that’s true for nearly every B2B SaaS email program we’ve reviewed.
Editable CSV worksheet
SaaS Email Marketing planning worksheet
A practical email planning worksheet: decisions, owners, evidence and next actions.
Frequently asked questions
Does SMS marketing work for B2B SaaS?
Rarely as marketing. Open rates near 98 percent get quoted constantly, but an opened message you did not want is a cost, not a win. B2B SaaS gets far better returns treating SMS as a transactional channel for security codes, failed payments, incidents and meeting reminders, and keeping every promotional message in email where the recipient expects it.
What consent do I need before texting a SaaS customer?
In the United States, TCPA requires prior express written consent for marketing texts and prior express consent for informational ones, captured with clear disclosure at the point of opt in. Under GDPR you need a freely given, specific, unbundled opt in with a record of when and how it was collected. A checkbox buried in your terms of service does not qualify in either regime.
How much does SMS cost compared with email for SaaS?
US outbound SMS through Twilio lists at 0.0079 dollars per segment plus carrier fees, so 10,000 single segment messages run roughly 80 to 110 dollars. The same 10,000 emails through most ESPs cost well under a dollar in send fees. SMS has to be worth 100 times more per message to break even, which almost no promotional message is.
What is 10DLC and do I need it?
10DLC is the US carrier framework for sending application to person messages from a standard 10 digit long code. You register your brand, then register each campaign with its use case and sample messages. Without it, carriers filter or block your traffic. Approval usually takes one to three weeks, so plan it before your launch date rather than after.
Should SMS be part of a dunning sequence?
Only at the end. Run the first two or three payment failure notices through email, then send one SMS before the final retry when the account is about to lose access. That single message routinely recovers a slice of involuntary churn because a card update takes 30 seconds on a phone. Sending a text on failure one trains people to ignore you.
Can I text users who signed up with a phone number for two factor authentication?
No, not for anything other than authentication. A number collected for security is consented for security. Reusing it for product announcements or upgrade prompts is exactly the scenario TCPA enforcement targets, and it is the fastest way to make users remove two factor from their account.
What SMS open and reply rates should a SaaS expect?
Delivery and read rates are genuinely high, commonly reported above 90 percent within minutes, which is why transactional use cases work so well. Reply and click rates vary enormously by context. A payment failure text can see double digit action rates, while a promotional blast to a B2B list often produces more opt outs than clicks.
The saas-marketing.net editorial team Research and editorial
We research, write and maintain every page on this site. The library explains marketing decisions through practical frameworks, explicit assumptions and references. Corrections can be requested through the contact page.
Published September 11, 2026. Last updated .