For the complete documentation index, see llms.txt. This page is also available as Markdown.

🚫 Error: RCS is not enabled for this user

Error: RCS is not enabled for this user

When sending an RCS message, you may occasionally encounter the error “RCS is not enabled for this user.”

This error indicates that the recipient cannot currently receive RCS messages.

What Does This Error Mean?

This error occurs when RCS is not available for the recipient. The recipient's device may not support RCS, RCS may be disabled on the device, or RCS traffic may not be available for the recipient's mobile network.

RCS for Business checks whether a recipient can be reached through RCS before delivering the message. Google documents that users who cannot be reached through RCS may include users whose device does not support RCS or whose RCS is disabled.

Why This Error Happens

The error can occur in the following situations:

Reason

Explanation

RCS is disabled

RCS is disabled on the recipient's device.

RCS is not supported

The recipient's device does not support RCS.

RCS is unavailable on the network

RCS traffic is not available for the recipient's mobile network.

How to Handle This Error

This issue cannot be resolved from QuickReply because RCS availability depends on the recipient's device and network.

If Delivery Optimization is enabled for the RCS Broadcast, configure a fallback channel such as WhatsApp or SMS. When RCS delivery fails, QuickReply can continue the delivery through the configured fallback channel.

For more information, see How to Use RCS Broadcast Delivery Optimization.

Final Note

RCS messages can only be delivered to recipients who are reachable through RCS. If RCS is unavailable for a recipient, configure a fallback channel to continue delivery through another supported messaging channel.

Last updated

Was this helpful?