Introduction
You open Google Messages, enable Chat features, and the status sits on ‘Waiting for activation’. Your messages fall back to SMS or MMS. You lose read receipts, typing indicators, and high quality media. You want a clear fix that does not waste your time.
This guide explains what that status means and how RCS activation actually works. You will move from quick checks to step by step fixes, then tackle advanced cases. You will also see tips for dual SIM and eSIM, U.S. carrier notes, and a preventive checklist for phone or SIM swaps. If nothing works, you will know how to escalate with useful proof. First, let us decode the status so you can target the right solution.
What ‘Waiting for activation’ means in RCS
Waiting for activation’ means Google Messages has not finished verifying your phone number with the RCS service your carrier uses. Until verification completes, Chat features will not connect. The app continues to send and receive SMS or MMS, which hides the problem in plain sight. You still exchange texts, but not over RCS.
Several root causes trigger this stall. Your number may not match the SIM line the app tries to verify. The SMS one time code may not arrive. The carrier may not have provisioned RCS for your account. A VPN, Private DNS, firewall, or strict battery rules may block activation traffic or background tasks. Knowing the handshake behind the scenes helps you pick the fastest fix.
That brings us to how activation works. With a basic mental model, you can remove the specific blocker in your setup.
How RCS activation works on your phone (OTP, servers, number verification)
RCS activation is a short handshake between your phone, the Messages app, and the RCS platform (often Google Jibe) that your carrier relies on. Here is the simple flow:
- Messages registers your line and asks the RCS backend to enable Chat features.
- The service verifies your number. It may send a one time SMS, a silent SMS, or perform a token exchange tied to your SIM and IMS registration.
- If verification succeeds, Messages flips to ‘Connected’ and turns on Chat features for that number on this device.
- If verification fails, the app keeps showing ‘Setting up’ or ‘Waiting for activation’.
This process needs a working SIM with SMS capability, a stable network path, correct date and time, and permission for Messages and Carrier Services to run in the background. Any break in that chain stalls activation. With this model in mind, start with quick checks to eliminate common blockers.
Quick checks: compatibility, network, default SMS app, permissions
You can fix many cases in minutes by confirming the basics:
- Make Google Messages the default SMS app.
- Confirm your carrier and region support RCS for your line.
- In Messages settings, open Chat features and confirm the phone number matches your SIM line.
- Turn on mobile data. If you use Wi‑Fi, allow background data for Messages and Carrier Services.
- Set date and time to Automatic.
- Grant Messages, Carrier Services, and Google Play services the required permissions: SMS, Phone, Contacts, and Notifications.
- Temporarily exempt Messages and Carrier Services from battery optimization and data saver.
If the status still sticks, move into a clean, ordered fix flow. The next section walks you through it.
Step-by-step fixes: update apps, toggle Chat features, clear cache and data, reboot
Follow these steps in sequence. Test after each step:
1) Update core components
– Update Google Messages, Carrier Services, Google Play services, and the Phone app in Google Play.
– Restart the phone after updates.
2) Toggle Chat features
– In Messages: open Settings, then Chat features, and turn Chat features off. Wait 30 seconds. Turn them on again.
– Check your number and tap Verify if prompted.
3) Confirm default app and re-verify
– Set Messages as the default SMS app. Leave it as default until activation completes.
4) Force stop and clear cache and data
– Go to Settings > Apps > Messages > Force stop. Then Storage > Clear cache and Clear data.
– Repeat for Carrier Services.
– Reopen Messages, accept prompts, enable Chat features, and verify your number.
5) Reboot with SIM inserted
– Power off the phone completely. Wait 30 seconds.
– Reseat the SIM if it is removable. Power back on, then check Chat features.
6) Disable VPN and Private DNS
– Turn off any VPN. Set Private DNS to Off or Automatic.
– Try activation on both Wi‑Fi and mobile data.
7) Refresh network
– Toggle Airplane mode on for 30 seconds, then off.
– If needed, reset network settings. This clears Wi‑Fi, Bluetooth, and APNs.
8) Check beta channels
– If you are on Messages or Carrier Services beta, leave the beta and update from the stable channel. If you are on stable, consider joining beta, update, and try again.
9) Check for outages
– Search for carrier or Messages outages. If reports show an outage, wait and try again later.
If nothing changes after this list, your number or account may be stuck on the backend. Use the advanced fixes next.
Advanced fixes: deregister RCS, confirm provisioning, reinstall components
When routine steps do not work, free your number and verify account setup:
- Deregister your number
- On an old phone, open Messages > Settings > Chat features and turn Chat features off.
- If you no longer have the old phone, use the Google disable chat portal at messages.google.com/disable-chat to release your number.
-
Wait a few minutes, then re-enable Chat features on the current phone and re-verify.
-
Confirm carrier provisioning
- Contact your carrier and ask them to check RCS or Advanced Messaging provisioning for your line.
-
Request a refresh or re-provision if they see a stuck profile.
-
Reinstall or roll back key components
- Uninstall updates for Carrier Services and Google Messages, reboot, then update them fresh from Google Play.
-
Clear data for both once more and retry activation.
-
Review battery and data policies
- Allow background data for Messages and Carrier Services.
-
Exempt them from battery optimizations, data saver, and any third party app cleaners or firewalls.
-
Last resort: factory reset
- Back up your data. Perform a factory reset. Insert and activate the SIM during setup. Install Messages and activate Chat features before restoring other apps.
If you use more than one line, take a quick detour. Dual SIM and eSIM setups need a specific flow.
Dual SIM and eSIM tips to resolve activation
RCS binds to a single active line. Multiple lines can confuse verification. Use this flow to keep the process simple:
- Pick one line for RCS
-
Set a single default line for Calls and SMS. Use that same line for Messages.
-
Disable or remove the other line during activation
-
Turn off the secondary SIM or eSIM, or remove the extra nano SIM. Reboot. Enable Chat features, finish activation, then re-enable the second line.
-
Reorder lines if needed
-
Some devices treat the first slot or primary eSIM as the priority line. Make the intended RCS line primary during activation.
-
Avoid number masking
- Turn off call forwarding, dual SIM masking, or any app that alters caller ID.
Once the app and network can see one stable number, activation usually completes. Next, check for carrier specific notes that can save time.
Carrier specifics in the United States: AT&T, T-Mobile, Verizon, Google Fi
Backends and policies differ by carrier. These notes can guide your call with support and avoid guesswork:
- AT&T
-
Ensure Advanced Messaging or RCS is enabled on your account. Ask support to confirm IMS and RCS flags if Messages stays on ‘Waiting for activation’.
-
T-Mobile
-
T-Mobile relies on the Google Jibe platform for most lines. Updating Carrier Services and re-verifying the number often fixes stalls. Ask support to refresh your RCS profile if needed.
-
Verizon
-
Verizon supports RCS with Google Messages. Make Messages your default SMS app. Check that no legacy Message Plus setting or profile blocks activation.
-
Google Fi
- RCS works well on Fi, but VPNs or strict Private DNS settings can block the verification step. Turn them off, clear data for Messages and Carrier Services, and retry.
If a support agent needs context, say that Messages cannot verify your number for Chat features and ask them to confirm provisioning for your line.
Special cases blocking activation: number ports, VOIP numbers, work profiles, roaming
A few edge cases require patience or a different approach:
- Recently ported numbers
-
After you move a number to a new carrier, SMS routing and RCS provisioning take time to settle. RCS may fail until the port completes. Try daily and ask both carriers to confirm completion.
-
VOIP or app based numbers
-
RCS expects a mobile number with SMS capability. Services like Google Voice or app based VOIP numbers often fail to verify.
-
Corporate devices or work profiles
-
Company policies can restrict background services, Private DNS, or VPN, or block SMS access in the work profile. Activate RCS in the personal profile with policies relaxed during setup.
-
International roaming
-
Roaming may block the verification SMS or data token. Try activation on your home network. If traveling, use a local SIM or wait until you return.
-
Region mismatch
- If your Play Store country, carrier, and SIM region do not align, RCS can hold. Make sure your account and SIM match your current region, then try again.
If one of these applies, resolve it first. Then run the earlier steps again. Once you connect, keep it stable by planning ahead for changes.
Preventive checklist before switching phones or SIMs
You can avoid the activation loop by preparing before you switch devices or lines:
- Turn off Chat features on the old phone before you move the SIM or wipe the device.
- Remove the old device from your account if you synced SMS across devices.
- Keep Messages as the default SMS app during migration.
- Insert and activate the new SIM before you restore apps and settings.
- Leave VPN and Private DNS off until Chat features shows ‘Connected’.
- Verify your number promptly when Messages prompts you.
- If you use dual SIM, activate with only the primary line enabled. Add the second line after RCS connects.
If you still hit a wall, escalate with the right evidence so support can fix provisioning fast.
When to escalate: what to collect and how to contact carrier or Google support
Before you call or chat with support, gather proof that pinpoints the issue:
- Screenshots of Messages settings showing Chat features status and your number.
- Confirmation that Messages is the default SMS app.
- A short timeline of steps you tried, including updates, toggles, cache and data clears, reboots, and network resets.
- Your carrier, plan type, and whether you recently ported a number or swapped SIMs or eSIMs.
- Whether you use a VPN, Private DNS, a firewall, or a work profile.
Contact your carrier first and ask them to confirm RCS or Advanced Messaging provisioning. If they refresh your profile, wait a few minutes. Then toggle Chat features off and on and check again. If the carrier sees no issue, send the same details to Google Messages support through the app under Help and feedback. After any backend change, give it a little time, then retry verification.
Conclusion
Waiting for activation’ means your phone and the RCS backend have not finished verifying your number. Most fixes target one of four areas: mismatched numbers or default app settings, out of date components, blocked activation traffic, or aggressive battery and data policies. You learned how to update core services, re-verify your number, clear app data, and reboot. You also saw advanced steps: deregistering old devices, confirming carrier provisioning, handling dual SIM and eSIM, and navigating edge cases like number ports, work profiles, and roaming.
Work through the quick checks first. Then follow the step by step and advanced lists. Keep one active line during activation and keep VPN and Private DNS off until you see ‘Connected’. If the status will not budge, escalate with screenshots and a clean timeline so support can re-provision your line. With a careful sequence and the right evidence, you can move from ‘Waiting for activation’ to a stable RCS connection.
Frequently Asked Questions
How long should RCS activation take on my phone?
Most activations finish within a few minutes after you enable Chat features. If it takes more than 30 minutes, update Messages and Carrier Services, toggle Chat features off and on, and turn off VPN and Private DNS. After a number port, it may take 24 to 72 hours for routing to settle. Try once or twice a day and ask your carrier to confirm provisioning.
Can RCS activate over Wi‑Fi, or do I need mobile data?
RCS can activate over Wi‑Fi or mobile data, but keep the SIM inserted and allow mobile data during activation. Some carriers tie verification to SIM and IMS. If your Wi‑Fi uses strict DNS or a firewall, switch to mobile data. Turn off VPN and Private DNS until you see Connected, then turn them back on.
Why does RCS keep deactivating after it connects?
Frequent drops usually mean multiple devices or SIMs use the same number, a battery or data policy kills background services, or a VPN or firewall interrupts the session. Keep Messages as the default SMS app on one active line, exempt Messages and Carrier Services from battery optimization and data saver, avoid aggressive cleaners, and keep Messages, Carrier Services, and Play services up to date. If your carrier changes your profile or you swap SIMs, toggle Chat features off, wait, then turn them on again.