Messaging & SMS

How to tell if a message was delivered

Understand delivery status for your messages and what to do when one doesn’t land.

Updated June 9, 2026 3 min read

Rezi tracks the delivery status of outbound messages so you can see whether they reached the guest.

Delivery status answers a question that comes up more than you’d expect: “did they actually get it?” A guest claims they never received the checkout reminder; another says the door code never arrived. Instead of a shrug, you have a record, the message, the timestamp, and what the carrier reported happened to it. That’s useful operationally and occasionally invaluable in a dispute.

StatusMeaning
SentHanded off to the carrier
DeliveredConfirmed delivered to the device
Failed / undeliveredCarrier couldn’t deliver, bad number, opt-out, or filtering

Reading the statuses

Sent means the message left Rezi and entered the carrier network, normal as a brief transitional state, suspicious if it lingers for hours, which usually points to a number that can’t receive SMS (a landline) or a network handling delay. Delivered is the gold standard: the recipient’s carrier confirmed the handset received it. It doesn’t prove the human read it, SMS has no read receipts, but the message is on their phone. Failed is the actionable one, and the cause is almost always one of three things: a bad or non-mobile number, an opt-out, or carrier content filtering.

Triaging a failed message

Work the likely causes in order. Check the number first, landlines and disconnected numbers can’t receive SMS, and a typo in a guest’s saved number produces exactly this symptom. Check opt-out status in the Guests table next; opted-out recipients are excluded by design, not by error. If the number is good and not opted out, look at content, link-heavy or spam-patterned messages get filtered by carriers, the full checklist lives in messages aren’t sending. Failures clustered across many recipients at once point to content or filtering; isolated failures point to that specific number.

No read receipts on SMS

SMS doesn’t support read receipts, so “delivered” is the strongest confirmation available. If a message failed, see messages aren’t sending.

When delivery really matters

For routine messages, glance at status only when something seems off. For critical sends, door codes, legal notices, shutoff warnings, make checking part of the send: confirm Delivered, and for the truly important ones, ask for a reply (“text YES to confirm you got this”), since a human acknowledgment beats any carrier receipt. For international numbers, where delivery is less uniform, that confirmation habit should be the default.

Can I see delivery status for every recipient of a broadcast?
Yes, broadcasts track per-recipient status, which is how you spot the three dead numbers in an otherwise successful 100-recipient send.
A guest says they didn’t get a message that shows Delivered, who’s right?
Delivered means their carrier confirmed receipt by the handset. The usual explanations: it’s in a filtered/junk area of their messages app, they have the building number blocked, or they overlooked it. The record supports you.
Do delivery receipts work for the AI’s conversational replies?
Status tracking applies to outbound messages across the board, though in live conversation the guest’s next reply is usually all the confirmation anyone needs.
Why would a message fail only sometimes to the same number?
Intermittent failures are usually carrier-side, congestion or aggressive filtering on that route. If it persists with one guest, have them check blocked senders, and loop in support if it continues.

Was this article helpful?

Related articles