Verify RCS Upgrade
RCS is an enhancement of the SMS channel, delivering messages over Wi-Fi and cellular to the default SMS messaging app on Android, Messages by Google. RCS messages are more secure, because they are encrypted between Twilio and Google's servers and between Google's servers and the end-user's device. They can also have lower delivery latency. RCS functionality is limited to compatible devices and is initially available in a select number of countries, starting with Italy, with plans to expand over time.
Twilio Verify will automatically upgrade delivery of your OTP messages via RCS instead of SMS whenever possible; and if we determine that it exhibits the same or better performance, as measured by Verification Success Rate and Messaging Cost Per Successful Verification.
Your end-user receives the RCS message from Verify on the default SMS messaging app on Android, Messages by Google. They do not need to know in advance that they are receiving an RCS instead of an SMS message, because it appears in the same app and looks similar.
channel=rcs, instead of channel=sms. Note that this does not mean that the RCS message was actually delivered. If it turns out that the message recipient does not have an RCS-compatible device, then the RCS message delivery will fail, and an SMS message will be automatically sent. Both RCS and SMS messages would be included in a single Verification Attempt identified by the same Attempt SID.How do I know if an RCS message was successfully delivered?
In the Verify Console Logs, for a given Verification Attempt, the last message delivery attempt will be displayed. For example, if an RCS message was sent and delivered, then the Outcome would show "Code sent via RCS" and Delivery Status would show "Delivered". However, if there was a failover to SMS, then the Outcome would show "Code sent via SMS".