Real-Time SMS, Text & WhatsApp Delivery Status Inside Salesforce
Your rep sends a WhatsApp to a hot prospect Friday afternoon. Delivered at 4:22pm. Read at 4:24pm. No reply. Monday morning, the rep sees it was read and follows up with a different angle. Without delivery status, they’d have guessed.
What delivery status actually tells you
Your message goes through four states on its way to the customer:
- Created, your app has accepted the message and queued it
- Sent, the message has left your system and hit the carrier or WhatsApp’s network
- Delivered, the recipient’s phone has received it
- Read, the recipient has opened it (WhatsApp only, for most practical purposes)
Your each state is a different signal. “Sent but not Delivered” suggests the number is wrong or the phone is off. “Delivered but not Read” on WhatsApp means the customer saw it in notifications but hasn’t opened the thread. “Read but no reply” is a genuine follow-up signal.
Why the data has to live on the record
Your delivery status in an external dashboard is useless when your rep is looking at a Salesforce Contact. Delivery status on the Contact record, updating in real time, is the difference between reactive follow-up and guessing whether the message got through.
Your every outbound SMS, text or WhatsApp in the messenger app stamps its current state on the activity record attached to the Salesforce Lead, Contact or Case. As the status changes, the record updates. Your rep refreshes the page and sees what happened.
How delivery failures turn into actionable work
Your failed delivery isn’t an error to ignore, it’s a signal. When a bulk campaign fires and 12 of 340 messages fail, those 12 recipients need a different treatment. Your reports can filter for Failed status and surface the list. Your rep updates the phone numbers, calls the customers, or removes the records from the next send.
Your error logs capture exactly why each failure happened, invalid number, opt-out, template rejection, carrier block. Your admin team sees patterns and fixes the root cause instead of chasing individual failures.
What changes for the Agentforce AI agent
Your Agentforce AI agent uses delivery status in its own logic. If the AI sends an SMS and it doesn’t deliver within 60 seconds, the AI can escalate by trying WhatsApp. If a WhatsApp is Read but not replied to within 24 hours, the AI can send a follow-up on a different channel. If the Read status fires but no reply comes, the AI can update the Salesforce record’s last-engagement field.
Your delivery status isn’t just a dashboard value. It’s an input your AI uses to decide what to do next. That’s what turns raw tracking data into useful automation.
Reports that sales leaders actually read
Your standard Salesforce reports roll up delivery status across channels and across time periods. Your sales leader sees “last week’s outbound: 2,400 messages, 98% delivered, 71% read (WhatsApp), 34% replied”. They compare against last month. They spot which templates convert and which don’t. They identify which channel, SMS, text or WhatsApp, gets the best reply rate for different audience segments.
Your delivery tracking isn’t an operational detail. Your delivery tracking is the measurement that lets you know what works and refine from there.