> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/latest-news/ios-26-whats-actually-changing-and-what-you-should-do.md).

# iOS 26: What’s Actually Changing (and What You Should Do)

Explains what iOS 26 really changes for SMS marketing, apart from the headlines, and how Recart is adapting.

As Apple rolls out **iOS 26**, many headlines are overstating the impact on SMS marketing. Here’s a quick, clear breakdown of what’s changing — and how Recart is helping you stay ahead of the curve.

### What’s Actually Changing

* **Unknown Sender Filtering:** Opt-in only. Adoption remains low. Minimal impact expected.
* **Notification Summaries:** Apple may remove brand names from message previews. Minor copy adjustments can preserve visibility.
* **UTM Stripping:** No effect on SMS links — only applies to Safari browsing.
* **Full-Screen Popups on Safari:** Apple’s new “Liquid Glass” design breaks full-screen modals. Recart has already shipped an update.

### What You Should Do

* **Test Notification Copy:** Start experimenting with your first-line messaging to help maintain visibility in Notification Summaries.
* **Add a Contact Card:** Include a Contact Card in your welcome and checkout flows to help your messages appear as trusted — not unknown. This improves deliverability and helps future-proof your program.
* **Monitor Performance:** Continue sending as usual — just keep an eye on open and click metrics to flag any unusual shifts early.

**For more detail on the iOS26 Update:** [Read the Full Guide Here](https://blog.recart.com/ios-26/)

*Last updated: September 2025*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.recart.com/latest-news/ios-26-whats-actually-changing-and-what-you-should-do.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.