A handset receipt is a delivery receipt generated when the recipient's phone acknowledges the message, the strongest confirmation SMS can give that a text arrived on the device.
When a phone receives an SMS, it acknowledges it to the network as part of the delivery itself. The network reports that acknowledgement to the message centre (SMSC), which turns it into a receipt and sends it back along the route to the gateway. This is the only receipt that proves arrival on the device, and it is unavailable on routes or operators that stop at acceptance.
It proves less than people assume. It does not show that the message was read: SMS has no read receipts. It does not even show that the message was displayed prominently, since some phones file texts from unknown senders in a separate folder. And it is only trustworthy on an honest route, because grey routes fabricate receipts.
Within those limits, handset receipts make list hygiene easy. An unknown number fails at the first send with a clear reason; an absent subscriber, whose phone is off or out of coverage, is retried until the validity period expires; a number that delivers is live. Consider a hypothetical login code with created_at 09:00:00, sent_at 09:00:01 and delivered_at 09:00:04. The code was on the phone within four seconds of the request, so if the user says it never came, the phone itself, with a blocked sender or a filtered folder, is the more likely place to look.
Two mistakes follow from overreading it:
- Treating delivered as read, and drawing engagement conclusions from it.
- Comparing delivery rates across countries without checking which of them return handset receipts at all.
At SMSMeteor: delivered means a handset receipt came back. Most destinations return them; countries that give carrier acknowledgement only are marked on their coverage page, and sent is the final positive state there. The message object records sent_at and delivered_at.
