🌟 Describe the Feature
Expose detailed SMS bounce information via API or web-hook. Instead of only returning high-level statuses like failed or undelivered, the API/web-hook should include raw error codes and carrier descriptions.
🚀 Justification
For compliance, analytics, and user experience, we need to know the exact reason why a message failed (e.g., landline, invalid number, carrier rejection, etc.). The current high-level statuses are too generic.
📝 Suggestions
Suggested payload fields:
- messageId
- bounceCode
- carrierDescription
Product Area
lc-phone-sms
📋 Use Case
- Identify and categorize failed SMS messages more accurately
- Improve compliance reporting and analytics
- Provide users with better feedback on delivery issues
🚨 Why Should This Be Prioritized?
- Without this, developers have no way to properly track or act on failed SMS via API, even though the UI already shows raw status codes
- Accurate bounce data is essential for improving user experience and maintaining phone reputation (avoiding carriers flagging numbers)
- It would reduce support overhead by letting developers programmatically handle errors instead of troubleshooting blindly
🧠 Additional Context
No response
🌟 Describe the Feature
Expose detailed SMS bounce information via API or web-hook. Instead of only returning high-level statuses like failed or undelivered, the API/web-hook should include raw error codes and carrier descriptions.
🚀 Justification
For compliance, analytics, and user experience, we need to know the exact reason why a message failed (e.g., landline, invalid number, carrier rejection, etc.). The current high-level statuses are too generic.
📝 Suggestions
Suggested payload fields:
Product Area
lc-phone-sms
📋 Use Case
🚨 Why Should This Be Prioritized?
🧠 Additional Context
No response