Know whether a device can work
Liveness, carrier, network, and battery context answer the operational question before a message is assigned.
Third-party services rent numbers, meter every message, and place the most important parts of delivery behind infrastructure the operator cannot inspect or control.
Pigeon takes a different position. The phone remains the carrier endpoint. The number stays owned. Messaging becomes an operating channel whose state, devices, routing, and events are visible.
The value is not one feature. It is that the seams between device, network, and operation hold.
Liveness, carrier, network, and battery context answer the operational question before a message is assigned.
Queued, assigned, sending, sent, delivered, failed, and received are real states with clear ownership.
Inbound, queued, sent, delivered, and failed events can trigger the next part of an external workflow.
Devices hold work through tunnels, dropped towers, and stale sessions, then continue safely when connectivity returns.
The number is yours. The hardware is yours. The automation runs on your terms.
That is a different relationship to a communication channel than renting one. Pigeon makes ownership operational rather than philosophical.
The hard problem is not sending one text. It is keeping distributed state legible while mobile hardware, carrier networks, and operating systems each fail differently.
Explicit states make failures diagnosable instead of mysterious.
Retries preserve intent without creating duplicate work.
Fleet visibility turns device availability into an operating fact.
Routing can use the devices that are actually ready, not merely registered.
Pigeon sends and receives SMS across managed devices, maintains message history and operational state, and exposes device, key, and event controls through an administrative surface. The next frontier is richer media and routing informed by live device conditions.
Loading published notes…