What Text Messaging Actually Is
SMS stands for Short Message Service. It is a protocol that lets you send plain text between mobile phones over cellular networks. Each message is capped at 160 characters using the GSM-7 encoding, or 70 characters if you are sending Unicode (emojis, non-Latin scripts). If you go over the limit, the message gets chunked into multiple parts and reassembled by the recipient's device. That usually works fine, but not always. I learned that the hard way when someone in my logistics team sent a 310-character shipping update via a vendor platform, and it arrived split across three bubbles on the client's iPhone. Half the team thought it was two separate messages and responded to both. The other half saw one fragmented note and ignored it. We stopped using long SMS for anything time-sensitive after that. People use text messaging for pretty much everything that requires a quick, reliable push notification to a phone number. Transactional alerts come first — banking alerts, delivery notifications, OTP codes, appointment reminders. These work because cell carriers have a dedicated signaling channel for SMS. It goes through even when voice coverage is spotty. Then there is marketing and outreach. Brands use it for flash sales, event reminders, and abandoned-cart nudges. Personal communication is the obvious third bucket. But the definition gets blurry when you mix in what people casually call "texting" — WhatsApp messages, iMessage, Telegram. Those are data apps, not SMS. They need internet. They do not travel the same network path. Carriers can throttle or block them differently. When you are building a system that sends bulk SMS, you need to know which one you are actually using. Here is how you send one the old-school way. Open your phone's messaging app. Type a number. Type a message. Hit send. On modern smartphones, that message leaves through the SMSC — Short Message Service Center. That is a server operated by your carrier. It routes the message to the recipient's device. If delivery confirmation is supported (some phones show that checkmark or delivered label), the SMSC sends back a delivery receipt called a DLR, or Delivery Status Report. That is all standard SMS. No app required.
If you are sending at scale, you are not using your phone. You are using an SMS API from a provider like Twilio, Vonage, AWS SNS, or a local carrier aggregator depending on where your recipients are. You create an account, get API credentials, and start making POST requests to their endpoint. The API takes your message content, the destination number in E.164 format, and sometimes a sender ID. It returns a message SID or reference ID. That ID lets you check status later via a callback or a polling request. Most providers also support webhooks for delivery receipts so you do not have to poll. The typical integration takes a few hours for someone who knows basic HTTP. First-time setup might take longer if your provider requires number verification or sender ID registration, which varies by country. I set up an SMS API integration for a healthcare compliance tool a while back. The requirement was to send appointment reminders 24 hours before scheduled visits. The catch was that we had to avoid hitting any character limits because the message included a short cancellation link. Google URL shortener was unreliable at the time and often got flagged as spam by filters. I switched to a provider-specific long link feature and kept the message under 91 characters per segment to stay within a single billing unit where possible. It cut our costs by about forty percent compared to the initial setup. Also, the carrier filters on one of the major US networks were rejecting messages with shortened links even when they pointed to legitimate domains. I had to switch to a vanity domain on our own infrastructure to get through consistently. There are a few things that beginners miss. One is the difference between long code, short code, and Toll-Free Verification. Long code is a standard 10-digit phone number. It is cheap and easy to set up but has low throughput — usually around one to three messages per second depending on the carrier and country. Short code is a five or six-digit number used for high-volume campaigns. It can handle hundreds or thousands per second but costs more and often requires a application process with the carriers. In the US, you now need to register your brand and campaign through the Campaign Registry before a short code will work. Without that registration, messages get blocked before they ever reach anyone. Toll-Free Verification is a newer option that lets you use a regular toll-free number for A2P (application-to-person) messaging. It has higher limits than long code but lower than short code. It sits in the middle for volume and cost.
Another thing people overlook is carrier filtering. Not all messages make it to the recipient. Carriers scan content for spam signals. Words like "free," "win," "act now," and certain punctuation patterns trigger blocks. Even legitimate messages get caught in these filters sometimes. There is no universal whitelist. Some carriers are stricter than others. If you are sending transactional messages, using keywords like "opt out" or "stop" in your message body actually helps — it signals to the filter that this is compliant. That sounds backwards but it is real. Encoding matters too. If your message contains any character outside the GSM-7 alphabet — Greek letters, Chinese characters, special symbols — it switches to UCS-2 encoding. That drops your character limit from 160 to 70 per segment. The billing still counts in 160-character GSM chunks though, so a 71-character Unicode message costs two segments. This is a common reason costs blow up faster than people expect. I once had a team send multilingual messages to a European customer base without adjusting the segment calculation. Their bill was triple what they projected because they assumed every message was one segment regardless of encoding. If you need to send a text right now and do not want any API setup, open your phone's native messaging app. Find the contact or enter the number. Type your message. Send it. That is a text message. If you are on an iPhone and the recipient is also on iPhone, you might see blue bubbles instead of green. That is iMessage, not SMS. It uses data, not the cellular signaling channel. It supports rich media and read receipts. But it only works between Apple devices with iMessage enabled. If either side turns it off or loses data, the message falls back to SMS automatically, which is fine for plain text but not for attachments.
Get the Full Details
For bulk or automated sending, pick a provider based on your target region. US and Canada have decent options with A2P 10DLC registration. Europe and Asia often have different compliance rules. Some countries block international SMS entirely or require local sender IDs. Nigeria, for example, mandates that all commercial SMS go through registered local numbers. Sending from a foreign short code will get blocked. You need a local partner or a provider with direct carrier connections in that region. The main downsides to SMS are deliverability uncertainty, lack of rich media support in standard SMS, and the increasing friction from carrier spam policies. MMS adds images and videos but uses more data and costs more. RCS is the modern replacement being pushed by Google and some carriers. It looks and behaves like WhatsApp — read receipts, typing indicators, image sharing — but it runs over cellular data or Wi-Fi and is not yet universally supported. Until RCS becomes standard, SMS remains the most reliable fallback because every mobile phone can receive it, regardless of brand, OS, or data plan. If your use case is simple notifications, SMS is fine. If you need conversation threads, media, or group chats at scale, look at WhatsApp Business API or similar platform options instead. They are not free, but they give you more control over formatting and engagement tracking. SMS is still useful as a backup channel when data networks are down or the recipient does not have the app installed. I keep SMS as a fallback in every system I build because cell coverage outlasts internet reliability in most places.
