The first text message ever sent was not a love note, a meeting reminder, or a meme. It was a Christmas greeting. On December 3, 1992, a 22-year-old engineer named Neil Papworth sat at a desktop computer, typed two words, and sent the world's first SMS to a mobile phone: "Merry Christmas." More than thirty years later, that humble two-word message has grown into one of the most quietly important protocols in connected technology, and it still shows up in the IoT devices we build today.
The engineer who sent the first SMS
Neil Papworth was working for the Anglo-French firm Sema Group Telecoms, part of a team building a Short Message Service Centre (SMSC) for the British carrier Vodafone. The SMSC was the piece of infrastructure that would store and forward text messages across the cellular network. To prove it worked, Papworth sent a test message from a computer terminal to the Orbitel 901 handset of Richard Jarvis, a Vodafone director who was at a company Christmas party.
The message arrived. Jarvis read it. But he could not reply, because mobile phones at the time had no way to compose a text. There was no keypad-driven messaging app, no T9, no touchscreen. SMS started life as a one-way novelty riding on a spare slice of the network's signalling channel, and almost nobody involved thought it would matter very much.
Why SMS was designed the way it was
The technical detail that makes this story relevant to anyone building connected hardware is how SMS was engineered. Text messages were squeezed into the control channel that phones already used to talk to cell towers, the same channel that handles things like call setup. That is why a single SMS is capped at 160 characters: it had to fit inside a small, fixed-size signalling packet.
This constraint turned out to be a feature. SMS is lightweight, store-and-forward, and works even when a data connection is weak or absent. The message waits in the SMSC until the device is reachable, then gets delivered. No persistent connection, no handshake-heavy protocol, no assumption of broadband. For a 1992 phone network, that was a clever workaround. For an IoT device sitting in a field, on a utility pole, or inside a shipping container, it is close to ideal.
From a Christmas greeting to cellular IoT
This is where a thirty-year-old text message meets modern embedded engineering. Plenty of IoT deployments cannot rely on Wi-Fi or stable mobile data. A water-level sensor on a river, a GPS tracker on a delivery truck, an agricultural monitor in a remote barangay: these devices often live where coverage is thin and power is scarce.
SMS remains a dependable fallback for exactly these situations. A microcontroller paired with a 2G or LTE-M cellular module can send a short status message or receive a command over SMS using simple AT commands, with far less complexity and power draw than maintaining a full data session. Many embedded designs use SMS as a low-bandwidth control and alerting layer: send a threshold alert, trigger a reboot, confirm a device is alive. The same store-and-forward resilience that let Papworth's greeting wait for Jarvis's phone now lets a sensor's reading wait for a network window.
For builders here in the Philippines, where connectivity varies sharply between a Metro Manila office and a provincial site, that resilience is not academic. Designing a device that degrades gracefully to SMS when data drops is often the difference between a prototype that demos well and a product that survives in the real world.
The lesson in a two-word message
The first SMS is a reminder that durable technology rarely arrives looking important. SMS was a side feature built on borrowed bandwidth, tested with a throwaway holiday message, and underestimated by nearly everyone who touched it. It endured because it was simple, frugal, and tolerant of bad conditions, the same qualities that make for good embedded design.
At Fluidwire we build IoT and web systems from silicon to cloud, including cellular-connected devices that have to keep working when the network does not cooperate. If you have a connected-hardware idea or a thesis prototype that needs to talk to the world reliably, get in touch and let's build it.
