iOS 27 Shipped Without the Messages Feature Everyone Wrote About

What Apple released today#

Apple released iOS 27 on Monday 14 September 2026, at roughly 10am Pacific, through Settings then General then Software Update (macrumors.com, read 14 September 2026).

The headline is Siri AI. For anyone running outbound, the headline is wrong twice over: the Messages item most coverage led with is not in the build, and the item that moves a sales number got almost no coverage at all.

Both facts are checkable against Apple's own site today. Neither is a reason to change a sequence, and both are a reason to change a report.

• iOS 27 runs on the iPhone 11 series and newer, plus the second-generation iPhone SE and later (macrumors.com, read 14 September 2026).
• Siri AI needs an iPhone 15 Pro or newer, launches in English only, carries daily usage limits, and is not available in the EU at release (macrumors.com, read 14 September 2026).
• Apple also quotes app launches up to 30 percent faster, photo library loads up to 70 percent faster and AirDrop transfers up to 80 percent faster.
• Nothing in the release touches how a business conversation starts, how consent works, or what a carrier requires.

The Messages feature that did not ship#

Apple removed two features from iOS 27 three days before release: suggestions in Messages, and automatic password changes. Apple updated its own website to say both arrive in a future software update.

Suggestions in Messages read the context of a conversation and offered a one-tap way to push something into Reminders, Notes or Calendar. It was demonstrated in June and it was in the betas.

Apple gave no date at the time. The removal also applies to iPadOS 27 and macOS 27, so it is not an iPhone-only delay.

• Reported 11 September 2026: suggestions in Messages and automatic password changes are pulled from iOS 27 and land in a future software update (9to5mac.com, read 14 September 2026).
• Beta testers had already noticed the password feature disappear in beta 5, and Apple's site now confirms both.
• Practical read: any plan built on Apple summarizing or acting inside a prospect's Messages thread this autumn is built on something with no ship date.
• Update, 14 October 2026: suggestions are back in the iOS 27.2 beta, which has no release date yet (9to5mac.com, 30 Sep 2026). What that means for a sales text: The iOS 27.2 Beta Puts an Action Button Under Your Sales Texts.
• The half of the announcement that did ship is the personalized writing-style work in the keyboard suggestion row, which is a different feature from the one that was pulled.

Green bubbles quietly got the change that counts#

The change that reaches a sales number is the RCS one, and it arrived with almost no attention. iOS 27 adopts GSMA RCS Universal Profile 3.0.

Two things follow from that. A reply to a specific green-bubble message now arrives at the other end as a real threaded reply, and a reaction renders as the emoji on the message instead of a separate line of text.

Universal Profile 2.4 shipped in iOS 18 in September 2024 and did not support threaded replies. Two years later that gap is closed (macrumors.com, read 14 September 2026).

• Before today, a prospect on Android who reacted to your message produced a text line in the thread reading something like 'Ryan loved an image'. That line was an inbound message and your tooling counted it.
• After the update, on a supported conversation, the same gesture attaches a reaction to your message and produces no inbound row at all.
• Both ends need carrier support. A recipient can check Settings, then Apps, then Messages, then RCS Messaging to see whether their carrier has enabled it (macrumors.com, read 14 September 2026).
• Blue-bubble iMessage threads already rendered reactions natively, so none of this changes the iMessage half of a list.

Your reply rate can fall while engagement holds#

Most reply counting is row counting. A number lands in the inbox, a rule sees an inbound message, a reply gets recorded and a sequence stops.

Take away the text line a reaction used to generate and that chain breaks at the first link. Somebody engaged, your system saw nothing, and the next scheduled message goes out to a person who already answered.

The direction of the error matters more than its size. A falling reply rate reads as a copy problem, and the team spends two weeks rewriting an opener that was never the cause.

• Audit every automation with an inbound-message trigger and decide explicitly whether a reaction should count as engagement or as a stop condition.
• Split your reply rate by blue bubble and green bubble this week, before the update spreads, so you own a clean baseline to compare against.
• A sequence that keeps sending after a thumbs up is the expensive version of this bug, because the prospect experiences it as being ignored.
• On a Blue Reacher line the conversation is a blue-bubble iMessage thread, so reactions have always rendered natively and this counting change does not reach it.

Nobody is on iOS 27 yet, and some never get all of it#

Release day is the start of a curve, not a switch. Installation runs for weeks, and the features inside the release do not all reach the same people.

Three separate gates apply. Device age decides whether iOS 27 installs at all, Apple Intelligence hardware decides whether the AI features appear, and carrier support on both ends decides whether the RCS changes work.

So any September-to-October comparison you run is measuring adoption as much as it is measuring your messaging. Say that out loud in the report before somebody draws a conclusion from it.

• Device gate: iPhone 11 and newer, plus the second-generation iPhone SE and later, can install iOS 27.
• Intelligence gate: Siri AI and the newer Apple Intelligence features need an iPhone 15 Pro or newer, in English, outside the EU at launch.
• Carrier gate: threaded replies and rendered reactions on green-bubble conversations need RCS enabled by the carrier at both ends.
• For a B2B list, handset age tends to track seniority and budget, so the segment that gets the new behaviour first is not a random sample of your pipeline.

A correction to what we published on 29 August#

Our earlier piece on this release named the standard behind the RCS changes as Universal Profile 2.7. The version Apple adopted is Universal Profile 3.0, which is what our RCS pages have said all along.

We have corrected that page today. The substance of it holds: reactions stop arriving as text, and that moves what an inbox counts.

Saying so plainly is cheaper than leaving it. A dated source on every fact is only worth something if the date survives contact with the release.

• Corrected: iOS 27 Changes What Counts as a Reply now reads Universal Profile 3.0, and flags that suggestions in Messages did not ship.
• GSMA published Universal Profile 3.0 in March 2025, and it is the profile that carries encryption work as well as threaded replies and reactions.
• What remains unannounced by Apple for this release: message editing and message recall on green-bubble conversations. Treat both as unshipped.
• Our RCS coverage is at RCS and SMS fallback if you want the channel-by-channel version.

Two smaller items worth one line each#

Beyond Messages, two release items touch a sales workflow at the edges, and both are smaller than the coverage suggests.

iPhone Handoff lets one phone number be used on two iPhones. It needs carrier support, and T-Mobile in the United States charges five dollars a month for it.

The speed work is the one your prospects will notice without being told. Faster app launches and faster media loading mean a photo or a video in a thread opens rather than stalls.

• At launch, iPhone Handoff is available through T-Mobile in the United States and Deutsche Telekom in Germany, with Verizon and EE named for later this year (macrumors.com, read 14 September 2026).
• A paid, carrier-gated feature spreads slowly, so treat a prospect answering from a second device as rare rather than as a new normal.
• Faster media handling is a quiet argument for using a real image in message three, where a stalled attachment used to cost the thread its momentum.
• Neither item changes consent, registration or pacing.

What to do this week#

None of this justifies rewriting a sequence. The work is in measurement, and the window for doing it cleanly is short because adoption climbs fast in the first two weeks.

Four jobs, in order of what they save you. Baseline first, because a baseline you did not take is the one thing you cannot recover later.

Then fix the triggers, then change the report, then check again in November when the segment data means something.

• Snapshot reply rate by bubble color today, with the date attached, and keep it somewhere a dashboard refresh cannot overwrite.
• List every automation that fires on an inbound message and decide what a reaction means in each one.
• Stop reporting a single blended reply rate this autumn. Report blue bubble and green bubble separately until adoption settles.
• Add one qualifying question to message two that has to be answered in the prospect's own words, because a one-tap response cannot carry it.
• Re-check in November and compare like for like, against the baseline you took today rather than against last quarter.

Frequently asked questions