One way SMS is a text your business sends where nobody is expected to answer: alerts, passcodes, shipping updates and broadcasts. Two-way SMS treats every outbound text as the start of a possible conversation, with replies landing somewhere a person or a rule can deal with them.
Most businesses think they need one-way and actually run two-way, because customers reply to everything. Text "Your appointment is tomorrow at 2 PM" and some people will answer "can we do 3?" The real question is whether those replies reach someone or disappear. This post covers what each model is good for, what happens to replies sent to a "no-reply" number, why carriers require STOP and HELP handling either way, and what handling replies costs, with real numbers.
What one way SMS actually is
One-way text messaging is outbound only. The sender pushes information and the conversation ends there. Common examples:
- One-time passcodes and login codes. Nobody needs to reply to "Your code is 482910."
- Transactional alerts. "Your order #1042 has shipped." "Your payment failed." "Your prescription is ready."
- System notifications. Outage notices, status changes, account security alerts.
- Broadcast announcements. "We're closed Monday for the holiday."
What these have in common is that the message is complete by itself. A reply adds nothing, and the sender usually doesn't want to staff a channel for answers.
The catch is that "one-way" describes your intent. The phone network doesn't enforce it. On a standard 10-digit business number (10DLC), any recipient can reply, and many will.
What two-way SMS is
Two-way SMS means replies are expected, captured and acted on. The outbound text is the opener:
- Appointment confirmations ("Reply C to confirm or R to reschedule")
- Lead follow-up after a form fill
- Support conversations
- Quote and estimate follow-ups
- Review requests that invite a reply first
Two way SMS marketing (also searched as "2 way SMS marketing") applies the same idea to promotions. Instead of announcing a sale and walking away, you send an offer to opted-in customers and treat replies like "do you have this in a medium?" as sales conversations. Conversational messages to opted-in lists get replies. That reply volume is why two-way marketing tends to outperform pure broadcast, and it's also why it takes more work to run.
One-way vs two-way at a glance
| One-way SMS | Two-way SMS | |
|---|---|---|
| Typical messages | OTPs, shipping alerts, outage notices, announcements | Confirmations, lead follow-up, support, conversational promos |
| Replies expected | No (but they arrive anyway) | Yes |
| Where replies go | Ignored, or an auto-response | An inbox, a CRM thread or a webhook |
| STOP and HELP handling | Required | Required |
| Staffing | Near zero | Someone has to read and answer |
| Cost driver | Outbound segments | Outbound segments + inbound segments + staff time |
| Best fit | High-volume, information-only sends | Anything where the customer might need to act |
What happens when customers reply to a one-way number
Customers reply to "no-reply" texts constantly. They reply to passcodes with "thanks," to shipping alerts with "where's my package," and to appointment reminders with real scheduling requests. Here's where those replies end up, depending on how the sender is set up:
- Nowhere. The reply hits a number nobody monitors. The customer thinks they rescheduled. You think they're coming. They don't show.
- A canned auto-response. "This number is not monitored. Call us at..." Better than silence, but it pushes the customer to a channel they were trying to avoid.
- An inbox. The reply lands in a thread next to the original message, and someone or some rule handles it.
The first option looks free but has hidden costs: missed reschedules, angry customers and complaints that can hurt your number's reputation. If your "one-way" texts concern anything a customer could act on, such as appointments, deliveries or payments, build for replies even if you expect few of them. Our appointment reminder SMS guide shows how a confirm-or-reschedule reply turns a reminder into a no-show reducer.
If you do want an auto-response, our auto reply text message examples cover wording that sets expectations without sounding like a dead end.
Why carriers require STOP and HELP even for one-way traffic
This is the part one-way senders most often get wrong. Calling your program "one-way" does not exempt it from reply handling. Carriers expect every registered 10DLC campaign to:
- Honor STOP (and variants like UNSUBSCRIBE, CANCEL, END, QUIT). Once someone opts out, you can't text them again until they opt back in.
- Respond to HELP with your business name and a way to reach you.
- Disclose opt-out instructions in your messaging, usually "Reply STOP to opt out" in the first message.
Campaign reviewers look for these during registration, and carriers filter traffic that ignores them. Our post on 10DLC rules and requirements goes through what reviewers actually check.
The legal side matters too. Texting someone after they've opted out is a classic TCPA problem, with statutory exposure of $500 to $1,500 per text. A "one-way" system that throws inbound messages away is also throwing away opt-outs. That's the most expensive way to save on an inbox.
On Ready, inbound STOP and UNSUBSCRIBE are honored automatically, and the opt-out applies across every campaign, so the contact can't be texted from another campaign by accident. If you send through the API, an opted-out number is refused up front and you aren't charged for it. You can read opt-outs back with GET /v1/opt-outs (docs at docs.tryready.com/api/opt-outs). Make sure your HELP response names your business and gives a real contact method. Compliance remains the sender's responsibility. Tooling lowers the risk but doesn't transfer it.
Use case matters at registration
Your registered campaign use case should match what you actually send. If you register "account notifications" and then send promos, or the other way around, expect filtering. Our guide to matching use case to what you send covers this in detail. Registration on Ready is done in the app with no setup fee. You pay $25 at submit for the first month, then $25/mo for registration + $2 per number. Most approvals take 2 to 7 days.
The cost of handling replies: a worked example
Replies cost money in two ways: inbound segments and staff time. On Ready, a reply you receive is billed like a sent text, at the Standard rate of $0.0075 per segment plus a $0.0045 carrier fee.
Assumptions for this example (stated, not measured):
- 5,000 appointment reminders a month, each under 160 plain characters, so 1 segment each
- 10% of recipients reply, so 500 inbound messages
- Every reply fits in 1 segment. A reply that's just an emoji is still 1 segment, because a lone 👍 sits well under the 70-character unicode limit
- Of the 500 replies, 100 are STOP or C (confirm) and get handled by rules, and 400 need a human to read and answer
- A human reply takes about 1 minute, and each one sends 1 outbound segment
Message costs:
- Outbound reminders: 5,000 × $0.0075 = $38, plus 5,000 × $0.0045 in carrier fees
- Inbound replies: 500 × $0.0075 = $4, plus 500 × $0.0045 in carrier fees
- Human responses: 400 × $0.0075 = $3, plus 400 × $0.0045 in carrier fees
So going two-way adds about 18% to your message volume in this example: 900 extra segments on top of 5,000. Those figures exclude the optional compliance surcharge. Scrubbing and landline validation are each $0.003 extra per segment when switched on, and both are off by default.
Staff time: 400 replies × 1 minute ≈ 6.7 hours a month. That's usually the bigger number, and it's the one to plan for.
What you get back: if even a fraction of those 400 humans were trying to reschedule, every recovered appointment is worth far more than those 400 responses cost to send. That trade decides most one-way vs two-way calls. If replies carry business value, the inbox pays for itself. If they don't, as with OTPs, it doesn't.
Where replies land on Ready
Replies show up in the Inbox in the same thread as the original message. For accounts connected to GoHighLevel, inbound and outbound messages sync both ways, mapped per GHL location, so each sub-account stays separate. For platforms building on the API, each customer gets its own sub-account with its own numbers and registration, and replies stay with that sub-account.
A one-way send through the API looks like this:
POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: 3f2b9c1e-7a4d-4e8b-9c2f-1a2b3c4d5e6f
{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true}The same number can still receive replies, so "one-way" here is a sending pattern, not a separate product. Texts sent during the recipient's quiet hours are held and sent later, and you're charged only when they go out. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
When pure one-way is genuinely fine
Here's the tradeoff stated plainly. If you only send passcodes and system alerts from your own app, and replies have no business value, you may not need an inbox at all. A raw CPaaS API like Twilio (around $0.0083 per segment) costs less per segment for that kind of traffic. You'd still need to handle STOP and HELP, register your campaign and build your own opt-out logic, but for pure OTP volume that's a reasonable choice.
Two-way tooling matters once your texts ask for anything: a confirmation, a reschedule, a purchase, a question. At that point the inbox, automatic opt-out handling and quiet-hours holds are the features you're paying for. Ready includes them alongside the CRM, pipeline, automations and the API.
The practical takeaway
- Use one-way patterns for information-only sends: codes, alerts and announcements.
- Assume people will reply anyway, and decide on purpose where those replies go.
- STOP and HELP handling are required either way. A system that ignores inbound texts also ignores opt-outs.
- Budget for inbound segments and staff time, not just outbound volume.
- If replies carry value, go two-way. If they don't, keep it simple.
If you want to try the two-way setup, you can create an account. Your first 20 texts are free one-to-one sends (campaigns are paid from the first text), and to send any text you need a card and a number ($2 a month, the first month charged when you get it). Use those free texts before you register, because they end once registration is paid for.
FAQ
What is one way SMS?
One-way SMS is outbound-only texting, such as alerts, passcodes and announcements, where the sender doesn't expect or act on replies. Recipients on a standard 10DLC number can still reply.
Can customers reply to a one-way text?
Yes. On a 10-digit business number, replies are delivered like any other text. Whether anyone sees them depends on your setup. Unmonitored replies often include reschedule requests and opt-outs.
Do one-way SMS programs still need STOP and HELP?
Yes. Carriers expect every registered campaign to honor STOP and respond to HELP. Ignoring inbound messages means ignoring opt-outs, which creates TCPA exposure.
What's the difference between two way SMS marketing and a broadcast?
A broadcast announces something and ends. Two way SMS marketing (or 2 way SMS marketing) sends offers to opted-in contacts and treats replies as sales conversations, which takes an inbox and someone to answer.
How much do replies cost on Ready?
A reply you receive is billed like a sent text: $0.0075 per segment on Standard plus a $0.0045 carrier fee. The bigger cost is usually staff time, so plan for the human side as well.