Telstra’s support page says carrier Rich Communication Services, or RCS, will start rolling out on compatible devices from 16 November 2026. Checked on 23 October, the page describes a messaging upgrade that can add richer conversations to eligible services, with support still depending on the phones and carriers involved.
Treat 16 November as the start of a rollout, rather than a promise that every phone will gain every feature that day. Telstra’s current page does not give a separate iPhone launch date. Check your own service and device before relying on availability.
What RCS Adds
Telstra lists higher-quality photo and video sharing, read receipts, typing indicators and group messaging among the features. RCS uses Wi-Fi or mobile data. It is included on eligible Telstra services, but data charges can apply, including applicable roaming charges overseas. Unsupported conversations can fall back to SMS or MMS.
Apple’s Australian guide confirms that RCS messages still use green bubbles on iPhone. A green bubble therefore does not tell you whether a conversation is using basic SMS or richer RCS. The underlying messaging service and the features shown in the conversation are more useful things to check.
For someone mainly interested in sending clearer family photos, our advice is to test that specific conversation once both participants have support. Keep the comparison practical: did the attachment arrive, are the expected indicators present and which delivery method does the app show? A launch date alone cannot answer those questions.
What iPhone Owners Should Check
Apple says iPhone RCS requires supported software and a carrier that offers the service. Its general instructions are Settings, Apps, Messages, then RCS Messaging. If the setting is absent, RCS may not be available. These are Apple’s general requirements; they do not establish a Telstra-specific activation date.
That distinction matters when reading rollout coverage. An operating system supporting a feature and a particular mobile service enabling it are separate conditions. Before changing providers for RCS, ask the provider to confirm support for your exact service and handset. Treat an unconfirmed future date as a reason to wait for clarification.
Check Encryption in the Conversation
Avoid assuming every RCS message has the same privacy protection. Google explains that eligible conversations between Google Messages users have end-to-end encryption, and describes a lock on the send button as an indicator. Its guidance also says SMS and MMS do not have that end-to-end protection.
Apple separately describes end-to-end encrypted RCS as a beta feature available with supported providers and rolling out over time. For sensitive information, check the actual conversation’s encryption status. Neither a green bubble nor the RCS label alone is a substitute for the app’s security indicators.
Before You Rely on the Upgrade
The useful outcome is a conversation that works better for the people in it. Recheck Telstra’s support page as the rollout approaches, and confirm device-specific details before spending money or changing a plan solely to obtain the feature.
Sources and How This Was Checked
This article is based on the official pages below, read on 23 October 2026. Telstra, Apple Australia and Google support pages were compared. The November rollout was not available to test; no device, conversation or carrier compatibility test was performed. The practical recommendations are editorial guidance. No hands-on test was performed.
Official Pages Used
Telstra: Rich Communication ServicesRollout from 16 November 2026; eligible services, data use, fallback, Android settings and security caveats.www.telstra.com.auApple Australia: Turn on RCS messaging on iPhoneCarrier requirements, green bubbles, iPhone settings and supported-provider encryption beta.support.apple.com
Google: End-to-end encryption in MessagesGoogle Messages eligibility, lock indicator and absence of end-to-end encryption for SMS/MMS.support.google.com
Spotted something wrong? Corrections are recorded in the open. Report a correction






