What is SMS? Complete guide to short message service

SMS stands for Short Message Service, a protocol defined in the GSM standard that caps messages at 160 characters per segment. It runs on cellular networks, so it works on every mobile phone without an app or data connection. That makes SMS one of the most widely compatible messaging channels.

Takeaways

• SMS stands for Short Message Service, a protocol defined in the GSM standard that caps messages at 160 characters per segment.
• In practice, SMS uses store-and-forward delivery through an SMS Center (SMSC). Messages reach recipients even when their phones are temporarily offline.
• SMS consistently achieves open rates above 90%, making it one of the highest-engagement communication channels.
• A2P (application-to-person) messaging requires registered sending routes like 10DLC, toll-free, or short code phone numbers in the US.
• SMS is unencrypted and limited to plain text. Businesses pair it with channels like MMS or RCS when rich media or higher security matters.

What does SMS stand for

SMS stands for Short Message Service. It is a communication protocol standardized as part of the GSM (Global System for Mobile Communications) specification, which defined how mobile networks handle voice and data across Europe and eventually the world. The first SMS was sent on December 3, 1992, when engineer Neil Papworth sent "Merry Christmas" from a computer to a colleague's Orbitel 901 handset on Vodafone's UK network.

The famous 160-character limit was not arbitrary. Friedhelm Hillebrand, one of the protocol's architects, analyzed postcards and telex messages and found that most fit comfortably within 160 characters. That constraint also fit neatly into the spare signaling capacity of GSM networks, which is why SMS could be deployed without new infrastructure.

Three facts define SMS at a technical level:

• Protocol layer: SMS rides on the signaling channels of cellular networks (originally SS7), not on dedicated data channels.
• Message size: 140 bytes per message, which equals 160 characters in GSM-7 encoding or 70 characters in UCS-2.
• Universality: Every mobile phone sold since the mid-1990s supports SMS natively, with no app installation required.

The short message service standard

SMS is part of the GSM standard, defined by European telecom engineers in the 1980s as they built the framework for second-generation mobile networks. The specification was formalized in GSM 03.40, and the first commercial message was sent in 1992.

The 160-character limit comes from the network itself. SMS messages travel over the signaling channels that GSM networks use to manage calls, not over dedicated data channels. Those signaling frames carry a 140-byte payload. Encoded with the GSM 7-bit alphabet, 140 bytes yields exactly 160 characters. The limit was a hardware constraint, not a design preference.

Every SMS passes through a Short Message Service Center, or SMSC. The SMSC uses a store-and-forward model. When you send a message, it goes to the SMSC first. The SMSC holds it, queries the network for the recipient's location, and delivers it when the destination handset is reachable. If the phone is off or out of coverage, the SMSC retries on a schedule until the message expires. The sender never needs the recipient to be online at the moment of sending.

This architecture explains why SMS works when data networks fail. Signaling channels are the control plane of the mobile network. They stay active as long as a phone can register with a tower, even when data throughput drops to zero. During network congestion or outages, a text often gets through when apps cannot connect.

The GSM 03.40 specification has remained functionally stable since 1992. That stability is the point. Every mobile device on every carrier in every country implements the same standard, which gives SMS a level of interoperability no messaging app has matched.

A brief history of SMS

The concept of SMS dates to 1984, when Friedhelm Hillebrand and Bernard Ghillebaert drafted the idea within the Franco-German GSM cooperation. The protocol was formalized in the GSM standard by 1987, but it took five more years before networks and handsets could actually send a message.

The milestones that shaped SMS into a global channel:

Consumer person-to-person texting peaked in the early 2010s as apps like WhatsApp and iMessage absorbed casual conversation. Business messaging moved in the opposite direction. A2P SMS traffic has grown steadily because SMS remains the only channel that reaches every phone number on earth, and analysts project the A2P SMS market will exceed $90 billion by the late 2020s.

How SMS works

SMS uses a store-and-forward architecture. When you send a message, it does not travel directly to the recipient's phone. It goes first to an SMS Center (SMSC), a network element that stores the message and attempts delivery. If the recipient's phone is off or out of coverage, the SMSC holds the message and retries until delivery succeeds or a validity period expires, typically 24 to 72 hours.

The underlying transport is signaling infrastructure. In traditional networks, SMS travels over SS7 (Signaling System No. 7), the same protocol suite that sets up voice calls. This is why SMS works without a data connection. The message hitches a ride on control channels that exist for network housekeeping.

A standard SMS delivery flow looks like this:

1. The sender's device submits the message to the SMSC over the cellular signaling channel.
2. The SMSC stores the message and queries the network's Home Location Register (HLR) to find the recipient's current serving switch.
3. The SMSC forwards the message to the Mobile Switching Center (MSC) serving the recipient.
4. The MSC pages the recipient's device and delivers the message over the signaling channel.
5. The recipient's device acknowledges receipt, and the SMSC generates a delivery report if one was requested.
6. If delivery fails, the SMSC queues the message and retries on a schedule until the validity period expires.

SMS character encoding: GSM-7 vs UCS-2

Every SMS segment carries 140 bytes of payload. How many characters fit in those bytes depends on the encoding. GSM-7 packs each character into 7 bits, which yields 160 characters per segment. It covers the basic Latin alphabet, digits, and common punctuation. Some characters, including the euro sign, square brackets, and curly braces, count as two characters because they live in an extension table.

UCS-2 uses 16 bits per character and supports the full range of scripts, including Chinese, Arabic, Cyrillic, and emoji. The cost is capacity. A UCS-2 segment holds only 70 characters. A single emoji in an otherwise plain English message forces the entire message into UCS-2, which can silently double or triple your segment count and your bill.

Concatenated SMS and UDH

Messages longer than one segment are split and reassembled using a User Data Header (UDH). The UDH consumes 6 bytes of each segment's payload, which reduces capacity to 153 characters per segment in GSM-7 or 67 in UCS-2. The header carries a reference number, the total segment count, and each segment's position, so the receiving handset can stitch the message back together in order.

Each segment is billed as a separate message. A 320-character GSM-7 message costs three segments, not two, because the UDH overhead applies to every part. Carriers also deliver segments independently, so long messages have slightly higher failure risk than single-segment messages.

Segment math at a glance:

SMS delivery reports

Delivery reports (DLRs) confirm what happened to a message after the SMSC accepted it. A DLR tells you whether the message was delivered to the handset, is still queued for retry, expired, or failed with a specific error code. For businesses, DLRs are the difference between guessing and knowing. They power retry logic, number validation, and channel failover.

DLR reliability varies by carrier and route. Some international routes return handset-level confirmations, while others only confirm that a downstream carrier accepted the message. The Telnyx SMS API returns real-time delivery receipts over its owned carrier-grade network, which removes the intermediate hops where DLR fidelity usually degrades. For a deeper look at what affects delivery, read the deliverability guide.

Start sending SMS today

A2P vs P2P messaging

P2P (person-to-person) messaging is one human texting another from a mobile handset. A2P (application-to-person) messaging is software sending texts to people. Every appointment reminder, verification code, delivery notification, and marketing text is A2P traffic. The distinction matters because carriers treat the two categories differently.

P2P traffic is low-volume and conversational, and carriers apply light filtering to it. A2P traffic is high-volume and one-directional, so carriers require it to run on registered routes with vetted senders. Sending A2P traffic over P2P routes, sometimes called gray routing, results in filtering, blocked numbers, and carrier penalties.

In the United States, businesses have three sanctioned A2P sending options:

• 10DLC (10-digit long codes): Standard local numbers registered for business messaging through The Campaign Registry. Best for conversational messaging and local presence. Registration requirements are covered in what is 10DLC.
• Toll-free numbers: 8XX numbers verified for messaging, with higher default throughput than unregistered long codes and nationwide recognizability.
• Short codes: 5 or 6-digit numbers with the highest throughput, typically 100+ messages per second. Best for high-volume alerts and large marketing programs, at a higher monthly cost.

Choosing between them comes down to volume, use case, and budget. A dental office sending 200 reminders a day fits 10DLC. A bank pushing millions of fraud alerts needs a short code. Telnyx supports all three routes through a single SMS API with built-in compliance tooling, so you can register campaigns and provision numbers without juggling separate vendors.

SMS vs MMS vs RCS

SMS is one of three native messaging protocols on mobile networks. MMS (Multimedia Messaging Service) extends SMS with media support. RCS (Rich Communication Services) is the modern successor designed to bring app-like features to native messaging.

SMS vs MMS

MMS supports images, GIFs, video, and audio, with payloads up to several hundred kilobytes depending on the carrier. It also allows longer text, typically up to 1,600 characters, without segmentation. The trade-offs are cost and speed. MMS messages cost roughly two to three times more than SMS, and media transcoding adds delivery latency.

Use SMS when the message is time-sensitive and text is enough, such as verification codes and appointment reminders. Use MMS when visuals drive the outcome, such as product promotions or damage documentation in insurance workflows. For a full breakdown, see SMS vs MMS or read more about MMS messaging.

SMS vs RCS

RCS adds branded sender profiles, read receipts, typing indicators, suggested replies, carousels, and high-resolution media, all inside the phone's native messaging app. Google's Messages app supports RCS across Android, and Apple added RCS support in iOS 18, which pushed the addressable base past 2.5 billion devices.

The catch is reach. RCS requires a compatible device, carrier support, and a data connection. When any of those is missing, messages must fall back to SMS. That fallback requirement is exactly why SMS is not going anywhere. It is the floor that every richer channel stands on. The differences are detailed in SMS vs RCS.

Advantages of SMS

SMS has outlasted pagers, fax, and a dozen messaging apps because its strengths compound. No other channel combines its reach, immediacy, and simplicity.

The reliability argument deserves emphasis for businesses. An email that lands in spam or a push notification on a logged-out device simply disappears. An SMS reaches a phone number, and phone numbers are the most stable digital identity most people have. Customers keep numbers for decades, across carriers and devices, especially with number porting making transitions seamless.

Limitations of SMS

SMS is a 1980s protocol, and its constraints show. Knowing them helps you decide when to use SMS alone and when to pair it with another channel.

None of these limitations has slowed A2P growth, because most business messages are short, urgent, and text-native by design. A verification code does not need a carousel. The right response to SMS limitations is channel pairing: SMS for reach and urgency, richer channels for engagement, and dedicated security tooling where encryption matters.

SMS compliance and regulations

Business SMS is regulated messaging, and the penalties for getting it wrong are significant. In the US, the Telephone Consumer Protection Act (TCPA) allows statutory damages of $500 to $1,500 per unsolicited message, and class actions routinely reach eight figures. In the EU and UK, GDPR treats phone numbers as personal data and requires a lawful basis, usually explicit consent, before marketing texts.

The core compliance requirements for US business messaging:

1. Get express written consent before sending marketing messages. Transactional messages require prior consent too, though the standard is lower.
2. Honor opt-outs immediately. Support STOP, and confirm the opt-out with a single final message. CTIA guidelines also recommend supporting HELP.
3. Identify your business in every message so recipients know who is texting them.
4. Register 10DLC campaigns through The Campaign Registry before sending A2P traffic on local numbers. Unregistered traffic faces heavy filtering and per-message surcharges. The process is explained in the 10DLC guide.
5. Respect quiet hours. TCPA restricts calls and texts to 8 a.m. to 9 p.m. in the recipient's local time, and some states impose tighter windows.

CTIA guidelines are industry standards rather than law, but carriers enforce them through filtering, so treat them as mandatory. Content categories like cannabis, gambling, and third-party lead generation face outright carrier prohibitions on most routes regardless of consent.

SMS for business

Businesses send SMS because it gets read. The 98% open rate and sub-three-minute read time make it the channel of choice for any message where timing determines value. The highest-impact use cases share a pattern: short, expected, and actionable.

The most common business SMS applications:

Two operational details separate successful programs from filtered ones. First, match the number type to the use case: 10DLC for conversational and local traffic, toll-free for support and mid-volume notifications, short codes for high-volume alerts. Second, monitor delivery rates per carrier and per campaign. A sudden drop on one carrier usually signals filtering, and catching it early prevents number reputation damage.

Sourcing numbers is straightforward with the right provider. Telnyx Phone Numbers activate instantly across 140+ countries, so you can stand up local sending identities in new markets without carrier negotiations.

SMS integration

Businesses do not send SMS from handsets. They integrate an SMS API, a programmable interface that connects applications to carrier networks. Your application makes an HTTP request with a destination number and message body, and the API provider handles routing, carrier connections, encoding, segmentation, and delivery reporting. The full architecture is covered in SMS API explained.

Sending an SMS with the Telnyx SMS API takes one request. You will need a Telnyx API key, which you can generate in the Mission Control Portal.

curl -X POST https://api.telnyx.com/v2/messages \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "+13125550100",
    "to": "+13125550101",
    "text": "Hello from Telnyx!"
  }'

The API returns a message ID you can use to track delivery status via webhooks.

For Python applications, the Telnyx SDK handles authentication, retries, and response parsing:

Receive SMS with a webhook (Node.js)

Inbound SMS arrives as a signed webhook event. This Express server verifies the Telnyx Ed25519 signature and processes the message:

const express = require("express");
const crypto = require("crypto");

const app = express();

app.post("/webhooks/sms", express.raw({ type: "*/*" }), (req, res) => {
  const sig = req.headers["telnyx-signature-ed25519"];
  const ts = req.headers["telnyx-timestamp"];
  const pub = process.env.TELNYX_PUBLIC_KEY;

  // Verify signature
  const der = Buffer.concat([
    Buffer.from("302a300506032b6570032100", "hex"),
    Buffer.from(pub, "base64")
  ]);
  const key = crypto.createPublicKey({ key: der, format: "der", type: "spki" });
  const valid = crypto.verify(null, Buffer.from(`${ts}|${req.body}`), key, Buffer.from(sig, "base64"));

  if (!valid) return res.status(401).send("Invalid signature");

  const event = JSON.parse(req.body);
  const message = event.data.payload;
  console.log(`From: ${message.from}, Text: ${message.text}`);

  res.status(200).send("OK");
});

app.listen(3000);

Full example: receive-sms-webhook-nodejs on GitHub.

Send OTP via SMS (Python)

Two-factor authentication with SMS. Generate a one-time code and send it through the Telnyx SDK:

import telnyx
import random

telnyx.api_key = "YOUR_API_KEY"

def send_otp_sms(phone_number, otp_code):
    from_number = os.getenv("TELNYX_PHONE_NUMBER")
    message_text = f"Your verification code is: {otp_code}. Valid for 5 minutes."

    response = telnyx.Message.create(
        from_=from_number,
        to=phone_number,
        text=message_text,
    )
    return response.data.id

# Generate 6-digit OTP
otp = f"{random.randint(0, 999999):06d}"
message_id = send_otp_sms("+14155550142", otp)

Full example: sms-two-factor-auth-python on GitHub.

Track delivery receipts (Node.js)

Delivery status arrives as a signed message.finalized webhook. This snippet sends a message and logs the delivery result:

const Telnyx = require("telnyx");
const client = new Telnyx({ apiKey: process.env.TELNYX_API_KEY });

// Send a message
const response = await client.messages.send({
  from: process.env.TELNYX_PHONE_NUMBER,
  to: "+14155550142",
  text: "Your order has shipped. Track at example.com/track",
});

// Webhook handler for delivery receipt
app.post("/webhooks/dlr", express.raw({ type: "*/*" }), (req, res) => {
  const event = JSON.parse(req.body);
  if (event.data.event_type === "message.finalized") {
    const status = event.data.payload.to[0].status;
    console.log(`Delivery status: ${status}`);
  }
  res.status(200).send("OK");
});

Full example: sms-delivery-receipts-nodejs on GitHub.

Sending a message through the Telnyx SMS API takes a few lines of Python:

Sending a message through the Telnyx SMS API takes a few lines of Python:

import telnyx

telnyx.api_key = "YOUR_API_KEY"

message = telnyx.Message.create(
    from_="+13125550100",       # Your Telnyx number
    to="+14155550142",
    text="Your verification code is 482913. It expires in 10 minutes.",
    webhook_url="https://example.com/webhooks/status"
)

print(f"Message queued: {message.id}")

Delivery status arrives asynchronously at your webhook URL, with events for sent, delivered, and failure states including carrier error codes. Full request and response schemas are in the developers center.

When evaluating an SMS provider, weigh these factors:

• Network ownership. Providers that resell aggregator routes add hops, latency, and DLR ambiguity. Telnyx operates its own carrier-grade network with direct operator connections, which is a core difference in the Telnyx vs Twilio comparison.
• International routing. Sending to 190+ countries means navigating sender ID rules, local registration requirements, and per-country encoding quirks. Look for a provider with documented country-specific guidance and smart routing that picks the best path per destination.
• Throughput and scaling. Confirm the provider supports your peak send rate across 10DLC, toll-free, and short code routes without queuing delays.
• Compliance tooling. 10DLC registration, opt-out management, and toll-free verification should be handled in-platform, not left to you.
• Transparent pricing. Per-segment pricing with published carrier surcharges beats opaque bundles. Volume discounts should be automatic.

International SMS deserves specific attention. A message to Germany may require a registered alphanumeric sender ID, a message to India must route through registered DLT templates, and a message to Brazil bills differently by carrier. A provider with smart routing evaluates these rules per message and selects the compliant, highest-quality path automatically, which is the difference between 95% and 70% delivery rates abroad.

FAQ

Start sending SMS today