What is short message service (SMS)?
Short message service (SMS) is the text messaging service built into cellular networks, delivering short plain-text messages between mobile phone numbers. It operates on a store-and-forward model: the network holds each message and retries delivery until the receiving handset is reachable, so the recipient's phone does not need to be online at send time.
The first text message was sent in December 1992, and the channel has outlived every messaging fashion since because it requires nothing beyond a working phone number: no app install, no data plan, and no operating system newer than the network itself.
What does SMS stand for?
SMS stands for short message service, the name given to the text messaging function specified during GSM standardization in the late 1980s. The full form is rarely used in conversation; almost everyone says text, texting, or SMS. The acronym survives in technical and commercial contexts because it names the specific carrier service, as distinct from multimedia messaging or app-based chat, and that distinction still decides cost, reach, and character limits.
How short message service (SMS) works
An SMS travels over the control channels of the cellular network rather than a data connection. When a phone sends a message, it goes first to a short message service center (SMSC), the store-and-forward hub that queues it, locates the recipient, and retries until the handset comes into coverage. Delivery confirmations flow back as status reports, the mechanism behind carrier delivery receipts.
Addressing is what gives the channel its reach. Every message is routed to a telephone number drawn from ITU-T E.164, the international public telecommunication numbering plan, so any reachable mobile number is a valid destination. Because signaling rides the same infrastructure as voice calls on the public switched telephone network, SMS works where mobile data does not.
Businesses reach the system through aggregators and messaging APIs, which connect software to carrier networks via short codes, toll-free numbers, or local numbers.
Types of SMS messages
Person-to-person (P2P): Ordinary texting between two handsets, billed to consumer plans and outside the scope of business messaging rules.
Transactional notifications: One-way alerts such as delivery updates and appointment reminders, the classic form of proactive customer outreach.
One-time passcodes: Verification codes sent as a second authentication factor at login or checkout, though NIST digital identity guidelines classify phone-delivered codes as restricted authenticators because of SIM swap and number porting risk.
Two-way conversational: Support threads where customers reply and expect an answer; where is my order questions drive much of this inbound traffic.
Promotional campaigns: Marketing sends that require prior opt-in and carry the strictest consent and opt-out obligations of any message class.
SMS vs MMS vs RCS vs OTT messaging
These get conflated because all four can land in the same messaging app on the phone. MMS extends SMS with images, audio, and longer text, fetched over mobile data at a higher per-message price. RCS adds read receipts, typing indicators, and branded rich cards, but requires mobile data and a compatible device. OTT apps such as WhatsApp and iMessage ride the internet and offer end-to-end encryption, but only work when both parties have the app; business access runs through the WhatsApp Business API. SMS is the floor beneath all three: the one channel that reaches any mobile number without an app.
Transport | Rich media | Requirements | Encryption | Choose it when | |
|---|---|---|---|---|---|
SMS | Carrier signaling channels | Text only, short segments | Any active mobile number | None native | The message must arrive everywhere |
MMS | Carrier infrastructure | Images, audio, video, longer text | MMS-capable handset and a data connection, higher per-message cost | None native | The content needs media more than speed |
RCS | Carrier, over mobile data | Rich cards, receipts, typing indicators | Data connection and compatible device | Varies by carrier deployment | Branded experiences on supported handsets |
OTT apps (WhatsApp, iMessage) | Internet | Full rich media and files | Both parties on the same app | End-to-end on major apps | Your customers already use the app daily |
Default to SMS for anything that must arrive: passcodes, alerts, and time-sensitive replies. Move a conversation to a richer channel when both sides are known to support it, and let the message's urgency, not its polish, pick the transport.
Why SMS matters for customer experience
SMS earns its place through open behavior: texts are read quickly, on the lock screen, without a login. For time-critical moments like fraud alerts, delivery exceptions, and appointment changes, no other channel reaches customers as reliably in the seconds that matter.
The failure mode is separation. When texting runs on a standalone tool, replies land in a silo: the customer answers a delivery text with a question, nobody sees it, and the brand that proactively texted now looks unreachable. Treating SMS as one thread inside omnichannel customer support, and triaging inbound texts with the same rules as email and chat, is what turns a notification channel into a support channel.
The tradeoff is intrusiveness. A text interrupts by design, so the bar for sending one is higher than for any inbox channel.
How is short message service (SMS) measured?
There is no authoritative published benchmark for SMS delivery, response, or opt-out rates. The open-rate percentages quoted everywhere trace back to vendor marketing rather than any auditable source, so treat them as sales copy.
What can be measured sits in the delivery pipeline. Delivery rate is confirmed through carrier delivery receipts (DLRs), the status-report mechanism defined in 3GPP TS 23.040, the specification behind the short message service. On outbound programs, track opt-out rate per campaign; on two-way programs, track reply rate and time to first response. Cost per delivered message, not per sent message, is the number that survives contact with billing.
Segment counts matter too: a reply that runs past the single-message limit splits into multiple billed segments, so length discipline is a direct cost lever.
How AI agents change SMS support
The constraint that shaped SMS, one short plain-text message at a time, is exactly the shape a language model handles well. What changes with AI is capacity and latency: an agent built on conversational AI can hold thousands of two-way text threads simultaneously, parse a terse reply like "no, the other order", and answer inside the delivery window a human queue rarely hits.
The mechanics differ from chat. There are no typing indicators or rich components to lean on, so the agent must resolve ambiguity with short clarifying questions, keep each reply inside segment limits, and carry conversation state across messages that may arrive hours apart. Teams running high-volume AI support agents across email, chat, and SMS treat the channel as its own discipline for that reason.
SMS stops being a one-way blast channel once replies get answered in seconds: customers learn that texting back works, and the notification list becomes a support queue.
Choosing SMS for the support stack
Evaluate an SMS provider on five axes. Coverage: which countries it can deliver to, through which routes, and how it reports failures. Integration surface: APIs and webhooks that route inbound replies into the same queue as every other channel, so no reply lands in a dashboard nobody watches. Consent governance: prior express consent and honored STOP keywords are legal obligations under the Telephone Consumer Protection Act and its implementing rule at 47 CFR 64.1200 for US traffic, so the sending platform has to enforce opt-out handling itself. Security and compliance: SOC 2 Type II and ISO 27001 as a baseline, GDPR handling for European recipients; a comparison of SMS-capable support tools on GDPR terms is worth the diligence. The operational constraint is sender registration: carrier vetting of business numbers takes days to weeks, so registration lead time belongs in the rollout plan.
SMS and the omnichannel stack
SMS sits at the junction of two stacks. It is a service of the telephony network, provisioned alongside voice numbers, yet the conversations it carries belong with chat and email in the support queue. Where a team lands on the multi-channel versus omnichannel spectrum decides whether a customer's text and their earlier email read as one history or two strangers. Platforms built around a unified support workspace resolve the split by giving every channel, SMS included, the same thread, context, and routing.
What does short message service (SMS) mean in plain terms?
Think of SMS as the certified mail of the phone: plain, short, a little dated, and accepted everywhere. Other messaging tools are faster-looking and richer, but each one only works if the other person happens to use it. A text needs nothing but the number.
Imagine it switched off tomorrow. The login code never arrives, the delivery alert reaches only the customers who installed an app, and the fraud warning sits in an email inbox until morning. Whole workflows lean on this channel precisely because it is the one nobody has to opt into installing.
The price of that reach is plainness. A text cannot carry a photo, a button, or a receipt, and it costs real money per message. SMS wins on the single question of whether the message arrives at all, and loses on almost everything people notice when it does.
Common short message service (SMS) mistakes
Most SMS programs fail in one of four ways.
Sending without reading replies. A number that can send but not receive turns every confused customer into a dead end, and the replies still arrive; they just land nowhere.
Ignoring segment boundaries. Messages written without a length budget split into multiple billed segments, sometimes delivered out of order, which doubles cost and garbles the one channel prized for reliability.
Treating consent as a checkbox. Opt-in collected once, never refreshed, and unenforced STOP handling is how a helpful notification program drifts into a compliance liability.
Measuring sends instead of outcomes. Sent counts always look healthy; only delivery receipts, opt-out rates, and replies reveal whether messages arrive, land well, and get read by anyone at all.
What is the difference between SMS and MMS?
MMS (multimedia messaging service) extends SMS with images, audio, video, and longer text, carried over the same networks at a higher per-message cost. SMS is plain text in short segments. In practice the two are provisioned together, and the sending platform picks per message: text-only content goes as SMS, anything with media is upgraded to MMS and billed accordingly.
What is the difference between SMS and RCS?
RCS (Rich Communication Services) is the carrier-backed successor to SMS, adding read receipts, typing indicators, high-resolution media, and branded sender profiles. The differences are its requirements: RCS needs a data connection, a compatible device, and network support, while SMS needs none of those. Most business platforms send RCS where the handset supports it and fall back to SMS everywhere else.
Why is SMS limited to 160 characters?
The limit comes from the signaling channel SMS was designed to use, which left 140 octets per message. With the GSM 7-bit alphabet that yields 160 characters; other alphabets yield fewer. Longer texts still send, but they are split into concatenated segments that are billed individually and reassembled on the receiving phone, which is why length discipline affects cost.
Is SMS encrypted or secure?
SMS has no end-to-end encryption; messages are readable by carriers and can be intercepted through SIM swapping or number porting. Security guidance treats one-time codes sent by text as weaker than app-based authenticators for that reason. SMS persists in login flows because it reaches everyone, but for high-value accounts an authenticator app or hardware key is the stronger choice.
Do businesses need permission to text customers?
In the United States, yes. Texting customers requires prior express consent under the Telephone Consumer Protection Act, with a higher written-consent bar for marketing messages, and STOP replies must be honored immediately. Comparable consent rules apply in most other jurisdictions. Consent should be collected per program, logged with its source, and enforced by the sending platform rather than by policy alone.
Can AI agents handle SMS conversations?
Yes, and the channel suits them well: inbound texts are short, high-intent, and map cleanly to intents like order status, appointment changes, and account questions. An AI agent can answer within seconds, ask clarifying questions when a message is ambiguous, and escalate to a person with full context. The constraints are length limits and consent rules, which apply to automated replies exactly as they do to human ones.