[ 25.11.06 ] SMS/LMS/MMS sending rebuilt

Overview

The SMS/LMS/MMS message engine was replaced outright, from MT Agent to Omni Agent, unifying the send architecture into a shared SDK-based module.
Delivery quality, scalability, and cross-channel integration all improve, and MMS was added to the failover path for Kakao channels, Brand Message, and RCS.

Key changes

Send agent migration (MT → Omni)

• The send architecture was redesigned on the SDK, which strengthens speed, stability, and failure resilience
• Every messaging channel (RCS, Alimtalk, Brand Message, SMS/LMS/MMS) now shares a single send engine
• Adding a new channel or send policy later will integrate faster

Wider MMS send paths

• MMS is now supported on the failover path for Kakao channels (Alimtalk / Brand Message)
• MMS failover is available when RCS fails
• Failover options used to center on SMS/LMS; the wider set minimizes content loss

Consistent sending and a tidied SDK structure

• Message composition rules, request parameters, error codes, and other send conventions are unified on the SDK standard

What you get

💡 For customers

• MMS becomes an option when a message fails, so information carries through and content is preserved
• Fewer policy differences between channels make send results more predictable
• Rich content should drive higher customer response

⚙️ For operations

• A unified agent simplifies the send architecture → faster incident response and root-cause analysis
• Rebuilding on the SDK brings structure to Kakao and RCS operations and quality management

Notes

• Your existing send method switches to Omni Agent automatically,
  and works immediately with no configuration change on your side.
• MMS failover is available according to each channel's policy;
  check the option on the settings screen.