AWS adds RCS: why SMS fallback still needs a plan
A short editorial review of channel compatibility and duplicate-message risk following the 31 March 2026 announcement.
What the announcement covers
On 31 March 2026, AWS announced RCS for Business support in End User Messaging, including automatic SMS fallback for recipients without RCS support. These are AWS product details; they do not establish availability across every Turkish operator and device.
MyVoip editorial perspective
A multi-channel design needs an order of attempts, a waiting period and a clear trigger for switching channels. A delayed first message arriving beside its fallback can confuse a user. For OTP, the code lifecycle for the same action should remain consistent across any channel change.
The question to take into procurement
How will destination availability be established, and exactly when will fallback be triggered? Agree outcome measurement and charging assumptions as well. This news item does not announce a MyVoip RCS or automatic-fallback product, or claim that AWS is our customer or partner.