What Happens When a Non-RCS User Scans a QR Code for an RCS Welcome Message?

Question

What Happens When a Non-RCS User Scans a QR Code for an RCS Welcome Message?

Applies To

• Rich Communication Services
• Messaging

Answer

The experience for users who do not have RCS support (for example, iPhone users) and scan a QR code aimed at launching an RCS conversation depends on the type of deeplink associated with the QR code. There are two common types of deeplinks:

SMS Deeplink

• On iPhones: There is no supported fallback. If an iPhone user tries to open the SMS deeplink intended for RCS, they will encounter an error page stating the action is unsupported.
• On Google Messages: If a user on Google Messages but without RCS enabled scans the code, the system may revert to sending a standard SMS to the designated phone number, provided as part of the SMS deeplink.
• User experience: On supported Android devices, a fallback to SMS may occur; on unsupported devices (iPhones), the user simply sees an error message.

Google-Branded Deeplink

• For non-RCS-capable users: Instead of attempting to start an RCS chat, these users are redirected to a fallback URL. This is a web address that you—the agent creator—have set up in advance. The fallback URL can point users to informational content, a landing page, or an alternate contact method.
• User experience: The transition to a fallback URL generally provides a smooth, alternative path without errors.

Summary

Key Takeaways

• The fallback depends entirely on how the QR code's deeplink is configured.
• Google-branded deeplinks allow for a custom fallback URL, providing a better alternative for non-RCS users.
• SMS deeplinks do not offer a fallback for iPhone users; they will see an error instead.
• Planning for both RCS and non-RCS users ensures a smoother experience across all device types.