RCS Settings
Learn when and how to configure RCS (Rich Communication Services) settings on your Android device for optimal SMS delivery with WhatSnap.
RCS (Rich Communication Services) is an enhanced messaging protocol available on Android devices. This guide explains when you should enable or disable RCS for optimal SMS delivery with WhatSnap.
What is RCS? RCS is Google's upgrade to traditional SMS, offering features like read receipts, typing indicators, high-quality media, and group chats. However, for WhatSnap SMS gateway purposes, RCS should typically be disabled unless you're using specific configurations like eSIMs over WiFi.
When to Disable RCS (Most Common)
Recommended: Turn RCS OFF
For most WhatSnap SMS setups, you should disable RCS.
Why Disable RCS:
✅ Better compatibility with traditional SMS delivery
✅ More reliable message routing through WhatSnap
✅ Avoids potential conflicts with gateway app
✅ Ensures messages send as standard SMS (what most businesses need)
✅ Prevents carrier-specific RCS limitations
When to Disable:
Using local physical SIM card for domestic messaging
Sending standard SMS through WhatSnap
Experiencing message delivery issues
Running database reactivation campaigns
Using multiple devices with different SIM types
Default Recommendation: Disable RCS on your WhatSnap SMS devices unless you have a specific reason to enable it (see below).
When to Enable RCS
Required: Turn RCS ON
RCS must be enabled in these specific scenarios:
1. Using eSIM from Another Country (Over WiFi)
Scenario:
You have an eSIM from a different country (e.g., Australian eSIM while physically in the US)
Sending SMS over WiFi (no local cellular connection)
Need to send SMS internationally using the eSIM number
Why RCS is Required:
eSIMs sending over WiFi need RCS to establish carrier connection
Without RCS, messages will fail to send
RCS enables "SMS over IP" functionality
Example Use Cases:
Australian business using Australian eSIM from overseas
US company using US eSIM while team is international
Multi-country operations with centralized SMS from one location
Setup:
Install eSIM on Android device
Connect to WiFi (may or may not have local SIM)
Enable RCS (instructions below)
Verify eSIM number can send SMS over WiFi
Connect to WhatSnap
2. Dual-SIM Configuration with eSIM
Scenario:
Using both physical SIM and eSIM in same device
Want to send from eSIM but device has local physical SIM
Why Enable:
Ensures eSIM can properly route messages
Allows carrier verification over WiFi/data
3. Carrier Specifically Requires RCS
Scenario:
Some carriers (rare) require RCS for their SMS service
Carrier documentation states RCS mandatory
Check with Carrier:
Review carrier's technical requirements
Contact carrier support if uncertain
How to Turn RCS On or Off
On Google Messages (Most Android Devices)
Toggle RCS On or Off
To Disable RCS (Recommended for most users):
Find the toggle for "Enable chat features" or "RCS chats"
Toggle it OFF (gray/disabled)
Confirmation may appear - confirm you want to turn off
To Enable RCS (Only if required for eSIM/WiFi):
Toggle "Enable chat features" to ON (blue/enabled)
Wait for RCS to activate (may take 30 seconds to a few minutes)
Status should change to "Connected" or "Active"
Alternative Method via Device Settings
If you can't find RCS settings in Messages app:
Open Settings on your Android device
Go to Apps → Messages (or Google Messages)
Tap Mobile data & Wi-Fi
Look for "Chat features" or "RCS" setting
Toggle on or off as needed
Samsung Devices
Samsung Messages app may have slightly different path:
Open Samsung Messages app
Tap three dots menu (⋮) → Settings
Tap Chat settings
Toggle "Rich Communication" on or off
Other Manufacturers
If using manufacturer's custom messaging app (Xiaomi, Huawei, etc.):
Check app settings for "RCS", "Rich messaging", or "Chat features"
If not found, install Google Messages from Play Store
Use Google Messages for WhatSnap (set as default if needed)
Troubleshooting RCS
Issue: RCS Won't Activate (When You Need It Enabled)
Symptoms:
Toggled RCS ON but status shows "Setting up..." indefinitely
Status shows "Connection failed" or "Unable to activate"
Solutions:
1. Check Internet Connection
RCS requires internet (WiFi or mobile data) to activate:
Verify internet connection works (open browser, load website)
Try switching from WiFi to mobile data (or vice versa)
Restart your router if on WiFi
Move to area with better signal if on mobile data
2. Verify Phone Number
RCS needs to verify your phone number:
Ensure SIM card is properly inserted and active
Check you can send/receive regular SMS
Verify carrier supports RCS (not all do)
Contact carrier if verification fails repeatedly
3. Clear Messages App Data
Reset the Messages app to retry RCS activation:
Settings → Apps → Messages
Tap Storage
Tap Clear cache (try this first)
If still not working: Clear data (will reset app - not your messages)
Reopen Messages app
Try enabling RCS again
Note: Clearing app data will reset Messages app preferences but won't delete your actual message history (stored separately by Android).
4. Update Messages App
Ensure you have the latest version:
Open Google Play Store
Search for "Messages" or "Google Messages"
If update available, tap Update
After update, retry enabling RCS
5. Wait 24-48 Hours
Sometimes RCS activation takes time:
Toggle RCS ON
Leave it in "Setting up" state
Keep device connected to internet
Check back in 24-48 hours
May activate automatically
6. Carrier Doesn't Support RCS
Not all carriers support RCS:
Check carrier's website for RCS support
Contact carrier support to verify
If carrier doesn't support RCS:
You can't use RCS
You may not be able to use eSIM over WiFi for SMS
Consider different carrier or use physical SIM locally
Issue: RCS Keeps Turning Back On
Symptoms:
Disabled RCS but it re-enables automatically
Can't keep RCS turned off
Solutions:
1. Disable Auto-Update for Messages
App updates may reset RCS settings:
Open Google Play Store
Search for Messages app
Tap the app
Tap ⋮ (three dots, top right)
Uncheck "Enable auto-update"
2. Use Different Messaging App
If Google Messages forces RCS:
Download alternative SMS app (e.g., Textra, Pulse SMS)
Set as default SMS app
Use that app instead of Google Messages
Configure WhatSnap to work with your chosen app
3. Carrier Auto-Provisioning
Some carriers automatically enable RCS:
Contact carrier support
Ask to disable RCS auto-provisioning on your account
May not be possible with all carriers
Issue: Messages Not Sending After Changing RCS Setting
Symptoms:
Changed RCS setting (on or off)
Now messages fail to send
Solutions:
Restart Device:
Power off completely
Wait 30 seconds
Power on
Wait for network connection
Retry sending
Restart WhatSnap Gateway:
Open WhatSnap Gateway app
Stop the gateway
Wait 10 seconds
Start the gateway
Verify "Connected" status
Test with Native Messages App:
Open native Messages app
Try sending regular SMS
If fails → carrier/SIM issue
If works → WhatSnap Gateway issue (restart app)
Toggle RCS Opposite Direction:
If you disabled RCS and messages stopped:
Try enabling RCS temporarily
Test message sending
If works, you may need RCS for your configuration
If you enabled RCS and messages stopped:
Try disabling RCS
Test message sending
RCS Settings by Use Case
Quick Reference Guide
Local physical SIM, domestic messaging
OFF
Standard SMS, no RCS needed
Local physical SIM, international messaging
OFF
SMS works without RCS
Local eSIM, domestic messaging
OFF (try first)
Usually works without RCS
Foreign eSIM over WiFi
ON (required)
Needs RCS for SMS over IP
Dual-SIM (physical + eSIM)
Try OFF first
Enable only if eSIM won't send
Multiple SIM cards, all local
OFF
Consistency across devices
Database reactivation campaigns
OFF
Most reliable for mass SMS
Having delivery issues
Toggle it
Try opposite setting to debug
Best Practices
For Standard WhatSnap SMS Setup (Most Users)
Recommended Configuration:
✅ Disable RCS in Google Messages
✅ Keep regular SMS/MMS enabled
✅ Use Google Messages as default app (or keep your preferred app)
✅ Configure WhatSnap Gateway with RCS disabled
Why This Works Best:
Maximum compatibility
Fewer variables for troubleshooting
Standard SMS is universally supported
Better for business/CRM messaging
For eSIM Over WiFi Setup (Advanced Users)
Required Configuration:
✅ Enable RCS in Google Messages
✅ Wait for RCS to show "Connected" status
✅ Test SMS sending from eSIM number
✅ Configure WhatSnap Gateway after RCS is active
Why RCS is Required:
eSIM needs carrier verification over internet
RCS provides SMS-over-IP capability
Without RCS, eSIM SMS won't work over WiFi
Testing Your Configuration
After changing RCS settings, test your setup:
Test Checklist
Send Test SMS via Native App:
Open Messages app
Send SMS to your personal number
Verify delivery
✅ If works → Configuration is correct
Send Test SMS via WhatSnap:
Open GoHighLevel
Send message to test contact
Check delivery on recipient device
✅ If works → WhatSnap configured correctly
Receive Test SMS:
Have someone text your device
Check message arrives in Messages app
Check message syncs to GoHighLevel
✅ If syncs → RCS setting is compatible
Monitor for 24 Hours:
Send/receive several messages
Check for any delivery delays or failures
✅ If consistent delivery → Setting is optimal
Additional Resources
Official Google RCS Documentation:
Related WhatSnap Guides:
SMS Installation & Setup - Complete setup guide
SMS Troubleshooting - Resolve delivery issues
SMS Specifications - Device and carrier requirements
Summary
Default Recommendation: RCS OFF
Turn RCS OFF for most WhatSnap SMS setups
Provides best compatibility and reliability
Simplifies troubleshooting
Exception: RCS ON for eSIM Over WiFi
Must enable RCS when using eSIM from another country over WiFi
Required for SMS-over-IP functionality
Test thoroughly after enabling
When in Doubt:
Start with RCS disabled
If messages won't send, try enabling RCS
Test thoroughly after any change
Contact support if issues persist
Quick Win: Most delivery issues related to RCS are resolved by simply disabling it. If you're having problems, turn RCS off first and test.
Need Help? Contact WhatSnap support at support@whatsnap.ai for assistance with RCS configuration for your specific setup.
Last updated
