Use an in app messaging API for anything a user will see while they're logged in to your product, and an SMS API for anything they need to see when they aren't. In app chat and push cost you almost nothing per message but only reach people who installed your app or opened your dashboard. SMS reaches any phone number you hold consent for, and it costs real money per segment.
Most SaaS teams end up with both. The useful question isn't which one wins. It's which message goes down which channel, and what happens when the first channel can't reach the person. This post gives you a decision table and the limits of each.
What each channel actually is
In app messaging means a banner, a chat widget, an inbox or a modal inside your own product. Your code decides what to show and when. Push is the cousin that reaches a phone's lock screen, but only for people who installed your mobile app and allowed notifications.
SMS is a text to a phone number through a carrier network. There's no app to install. You do need consent from the recipient, and for US business texting you need 10DLC registration, which our 10DLC explainer covers.
Reach: who can you contact at all
In app only reaches users in a session. If they haven't logged in for three weeks, your onboarding nudge sits unread. Push is better but depends on app install and a permission prompt the user can decline. Neither works for a lead who never created an account.
SMS reaches anyone with a phone number and consent, including a lead who filled in a form and never came back. That's the whole reason SaaS products add it. The trade is that you need that number and that consent first.
Opt-in and consent are different
In app messages generally ride on the terms the user accepted when they signed up, though you should check that with your own counsel. SMS is stricter. You need the recipient's agreement to receive texts, and you should be able to show it. Ready records an attestation when you send with consent_attested set, but it doesn't store a per-contact consent record: you keep the opt-in in your form or CRM. [A hosted opt-in page is the one exception.] Our consent record schema post shows what to store on your side.
SMS also carries a STOP right. When someone replies STOP, you can't text them again, so your product has to respect that. Ready honors it automatically and exposes opt-outs through the API.
Decision table
| Message | Best channel | Why |
|---|---|---|
| Feature tip while the user is in the app | In app | They're already there, it's free |
| Weekly digest for active users | In app or push | Low urgency, no per-message cost |
| Appointment reminder for a customer of your customer | SMS | The end customer has no login |
| Login code or security alert | SMS, with email as a fallback | Must arrive when logged out |
| Abandoned trial nudge | SMS if consented, else email | In app can't reach a user who left |
| Receipt or "your order shipped" | Email, SMS if the customer opted in | Record vs urgency |
| Reply from support while user is away | SMS if they started it by text | They're in a text thread |
What each can't do
In app can't reach logged-out users, non-users, or anyone on a device where your app isn't open. Push can't reach people who declined the prompt, and delivery isn't guaranteed by the platform.
SMS can't carry rich layouts, buttons or reliable read tracking. It's plain text and pictures (MMS), and every segment is billed. It also can't be sent at any hour: Ready's quiet-hours rules hold or refuse some sends, as the retries post explains.
A worked example with stated assumptions
Assume a SaaS with 5,000 users who haven't logged in this month, and a 1-segment text each. At $0.0075 plus a $0.0045 carrier fee per segment, the cost is 5,000 x ($0.0075 + $0.0045) = 5,000 x $0.012, which is the all-in total, and it excludes screening. The same 5,000 in app messages cost nothing in sending fees but reach none of these users, since none are logged in. That's the gap SMS pays for. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. Send only to users who consented.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
Where to go next
Build in app first, because it's free and fast. Add SMS for the moments that can't wait for a login, and use email as the backup for both. If you're weighing SMS against push specifically, read SMS vs push notifications. When you're ready to test, the API quickstart gets a first text out, and pricing has the full rate card.
Frequently asked questions
Can an in app messaging API replace SMS?
Not for logged-out users or people who've never signed up. It covers users in a session well, and costs almost nothing, but SMS fills the reach gap.
Do I need consent for in app messages?
Usually your terms cover product messages, but rules vary by message type and region, so check with counsel. SMS needs the recipient's agreement to texts and you should keep proof.
Is push the same as SMS?
No. Push needs your app installed and notifications allowed. SMS needs only a phone number and consent, but it costs per segment.
What happens if a user texts STOP?
You can't text that number again. Ready honors STOP automatically, and you can check status with GET /v1/opt-outs/:phone before sending from another tool.