Key Takeaways
- For schools, text messages are public records. Regardless of protocol, staff messages on district devices are subject to retention requirements, FOIA requests, and ediscovery. Archiving gaps are compliance gaps.
- Carrier archiving only captures SMS. iMessage and RCS, which are now default on most smartphones, bypass the carrier gateway entirely and are invisible to these solutions.
- Disabling RCS to force SMS fallback is unreliable. Fallback behavior on external senders’ devices isn’t guaranteed, especially in group threads, and your IT team can’t control it.
- Device-level archiving captures everything. iMessage, RCS, SMS, and MMS, without disabling modern messaging features or disrupting how anyone communicates.
- More complete coverage comes at a higher cost. Native iMessage and SMS archiving is typically more expensive because it captures more data and preserves more context. Carrier archiving coverage is much narrower. Make sure you understand the gap.
Introduction
There’s a scenario playing out in school districts across the country that doesn’t show up in audit reports, at least not yet.
A district has done everything right: staff devices managed through an MDM platform, carrier-level SMS archiving active and configured per vendor instructions, and compliance boxes checked. Then, quietly, teachers start missing messages from parents. No error, no alert, no bounce-back to tip anyone off. The parent’s phone shows the message was sent, but the teacher never received it.
This isn’t hypothetical, and it isn’t rare. It’s a real architectural gap quietly surfacing in districts that rely on traditional carrier archiving solutions. The culprit is RCS, the messaging standard that has replaced SMS as the default on most smartphones, and the protocol those solutions were never designed to capture.
If your district relies on AT&T Network SMS/MMS Archiving, or any carrier SMS archiving solution used in education, this is worth your full attention.
This article covers:
- Why carrier-based SMS archiving can’t capture RCS or iMessage, and what that means for compliance
- How disabling RCS creates silent message delivery failures your IT team can’t control
- What K-12 districts should do right now to identify and close archiving gaps
- How device-level archiving captures all three protocols without disrupting staff communication
How Carrier SMS Archiving Works in Schools
Carrier-based archiving solutions capture messages at the network level as they pass through the carrier’s SMS gateway.
When a text message is sent to a staff member’s work number, the carrier intercepts it, routes a copy to the archiving platform (via SMTP), and delivers it to the device. It’s a clean, passive approach that requires no app installation and no end-user action.
For years, this worked well. SMS was SMS, MMS was MMS, and the infrastructure was predictable.
That’s no longer the case.
RCS Changed the Default, Quietly
RCS (Rich Communication Services) is the successor to SMS. It supports read receipts, typing indicators, high-res media, and group messaging features that feel closer to iMessage or WhatsApp than traditional texting.
Google pushed it hard on Android for years. Apple adopted it in iOS 18, released in September 2024, and all three major US carriers, AT&T, T-Mobile, and Verizon, support it on iPhone. iOS 18.4 closed most of the remaining MVNO holdouts.
The key detail for IT and compliance teams is that RCS is now the default messaging protocol on most modern smartphones. When an Android user texts someone, their device will attempt RCS first. When an iPhone running iOS 18 or later messages another iPhone or an Android device, it may also route through RCS.
Most users have no idea this is happening. From their perspective, they’re just sending a text.
iMessage has always traveled over Apple’s servers, outside the carrier gateway. RCS now does the same when both devices and carriers support it, which in 2026 is the common case.
The RCS Compliance Problem
Carrier-level SMS/MMS archiving solutions are built around the carrier’s SMS gateway. RCS doesn’t pass through that gateway. It travels over IP-based infrastructure (essentially the internet), which means it’s architecturally invisible to traditional carrier archiving tools.
This isn’t something that can be fixed with a configuration change or a software update. It’s a fundamental design boundary built into how carrier archiving works
Archiving vendors who operate within this model, including solutions deployed through providers like Smarsh on AT&T’s network, require RCS to be disabled on managed devices in order to ensure all messages route through SMS/MMS and are capturable. This is the compliant path, and it’s the right call from a records retention standpoint.
The problem starts the moment you flip that switch.
| Related: Education Email Archiving: Must-Have Features for K-12 |
The RCS Fallback Failure That Carrier SMS Archiving Can’t Fix
When RCS is disabled on a managed work device, the expectation is that incoming senders will fall back to SMS. In theory, this should be automatic. In practice, it frequently isn’t.
When a parent sends a message to a teacher’s work number from an iPhone or Android device, their device attempts RCS delivery first. If that fails, because RCS has been blocked at the device or network level, the sender’s device should recognize the failure and retry via SMS.
But this fallback isn’t guaranteed, as it depends on the sender’s device, OS version, carrier, and the type of message thread involved.
Group message threads are especially problematic. In many cases, RCS delivery failures in group threads are completely silent — no error, no notification, no retry prompt. The sender’s phone shows the message as sent. The recipient never gets it.
Your IT team can control everything on the managed device side. You cannot control what happens on a parent’s personal iPhone.
Asking parents to go into their settings and disable RCS, or enable “Send as Text Message,” isn’t a realistic solution at any scale. And even when individual senders do enable that option, device software can revert the behavior after an update.
Why This Matters for K-12 Compliance Specifically
When it comes to SMS archiving for school districts, the compliance environment is more layered than most people realize. State public records laws govern staff communications that touch district business, including messages received on district-managed devices or numbers.
Depending on the state, those records may be subject to retention requirements ranging from one to several years, and potentially subject to public records requests.
Parent-staff communication gaps can lead to complaints, grievances, or documentation requests that put a spotlight on exactly how your messaging infrastructure works. “We didn’t receive that message” is a harder position to defend when the parent has a sent confirmation on their end.
The intent behind text message archiving for schools is sound: preserve staff communications relevant to district business, student matters, or legal proceedings. But if the archiving solution is creating communication failures in the process, you now have a different kind of exposure.
Compliance and operational reliability have to work together. When they conflict, something needs to change.
| Check your school’s FERPA Compliance status in under 10 minutes |
What K-12 IT Teams Should Do Right Now
Getting SMS archiving for school districts right requires more than initial setup. If your configuration hasn’t been reviewed since it was first deployed, here are the steps to take::
- Audit what your archiving solution is actually capturing — Ask your vendor directly: Does your solution capture RCS messages? If not, what’s the recommended configuration, and what are the trade-offs? Get this in writing.
- Review your MDM policies around RCS and iMessage — If RCS or iMessage has been disabled on managed devices to satisfy archiving requirements, document that decision and verify that the network-level block is confirmed by your carrier, not just applied at the device level.
- Test your fallback behavior — Have someone on a personal iPhone or Android device send a message to a managed work number. Confirm it arrives, then try a group message thread and document the results. This should be a routine check, not a one-time setup task.
- Evaluate whether carrier archiving is the right architecture for your environment — Carrier-based archiving was designed for a world where SMS was the universal standard. In 2026, it isn’t. If your staff receives significant communication volume from parents and external contacts via personal smartphones, which is the norm in K-12, you should be asking whether an app-based or platform-level archiving solution provides more complete and reliable coverage.
- Loop in your compliance officer — This is not purely an IT problem. If your archiving solution has a structural gap that prevents capture of a messaging protocol that’s now the default on most consumer devices, that’s a compliance posture issue, not just a technical one. Document the gap, steps taken, and vendor guidance.
The Bigger Question: Is Carrier Archiving Still the Right Fit?
It’s worth stepping back and looking at what carrier-based SMS archiving was actually built to do.
Carrier archiving captures messages as they pass through the carrier’s SMS gateway. That means it was designed for one protocol: SMS. Depending on the solution and configuration, MMS capture is often partial or excluded entirely.
iMessage never touches the carrier gateway, and RCS doesn’t either. Carrier archiving may appear to be a text messaging solution, but in practice, it covers a fraction of the channels your staff actually uses to communicate, and that fraction is shrinking as SMS becomes the fallback option rather than the default.
The cost difference between carrier archiving and a full-coverage solution is real, and for budget-constrained districts, it’s an understandable reason to choose the carrier route. But that lower price reflects a narrower scope, and many districts that chose carrier archiving on cost didn’t fully account for what they were leaving uncaptured in the process.
The deeper problem is what compliance through carrier archiving actually requires.
To ensure messages route through the SMS gateway and are therefore archivable, RCS has to be disabled at the device and network level, and iMessage has to be turned off. In other words, the only way to make carrier archiving work as a complete solution is to strip modern messaging functionality from your managed devices, and even then, you can’t control what happens on the sender’s side.
The result is an archiving setup that creates the communication failure: staff missing messages from parents, with no alert and no fallback guarantee.
That’s not a configuration problem but an architectural one. When your compliance solution requires you to disable the features that make your devices functional, the solution is no longer fit for the environment it’s operating in.
A device-level archiving approach, one that captures at the application layer rather than the carrier gateway, doesn’t require any of that.
iMessage is captured natively, including encrypted messages, edits, deletions, and attachments. RCS and SMS, including MMS, are captured alongside it. Staff keep full use of their devices, parents and external contacts communicate the way they normally would, and your archive reflects the full picture of what was actually sent and received, not just the portion that happened to route through a channel your vendor was designed to handle.
Cost is a legitimate factor in any procurement decision, but it shouldn’t be the only one. The more important questions are whether your current solution is actually capturing what your district is legally required to retain, and whether the trade-offs required to make it work are ones you can sustain long-term.
How Jatheon Handles What Carrier Archiving Can’t
Jatheon’s iMessage archiving solution takes a fundamentally different approach from carrier-based tools. Rather than relying on the carrier’s SMS gateway, which iMessage never touches, Jatheon captures communications at the source.
Once users complete a one-time Apple credential sign-in to approve forwarding, iMessage data flows directly into the archive automatically. There’s no app to install, no hardware to configure, and no change to how staff communicate day-to-day.
For districts that need to separate staff business conversations from personal ones, Jatheon’s whitelist and blacklist controls let you capture only the communications you’re actually required to retain, without pulling in unrelated personal messages.
The capture itself is comprehensive: edits, deletions, reactions, attachments, voice notes, and complete metadata are all retained, giving you a full, audit-ready record. When a public records or ediscovery request comes in, legal hold, advanced search, and export tools are built in.
For K-12 districts operating under FOIA and state Sunshine Laws, that combination of complete capture, retention controls, and fast retrieval is exactly what compliance requires. There are no communication disruptions that come with disabling modern messaging protocols to satisfy a carrier-level archiving requirement.
If your district’s archiving solution was set up before RCS and iMessage became the default, there’s a good chance your coverage has gaps you haven’t accounted for. To see how Jatheon helps K-12 districts capture the full range of staff communications, including iMessage, without disrupting operations or creating compliance blind spots, book a demo or reach out at sales@jatheon.com.
FAQ
Our archiving vendor says we’re compliant. Does that mean we’re actually capturing everything?
Not necessarily. Compliance certification from a vendor typically means their solution meets the requirements for the channels it was designed to capture. It does not mean every channel your staff uses is covered. If your staff receives iMessages or RCS messages on work devices or numbers, you should ask your vendor directly whether those protocols are in scope, and get the answer in writing.
Are SMS and iMessage the same thing from a records retention standpoint?
No, and the distinction matters. SMS travels through your carrier’s network and can be captured by carrier-level archiving tools. iMessage travels over Apple’s servers via an internet connection and bypasses the carrier gateway entirely. Most state public records laws and FERPA-adjacent retention requirements don’t distinguish between the two. If it’s a business communication on a district-managed device, it’s likely a record regardless of how it was transmitted.
RCS is the default on most phones now. Does that mean our carrier archiving solution has a gap we don’t know about?
Possibly. If your district uses carrier-level SMS/MMS archiving and your staff communicates with parents or external contacts via work phone numbers, RCS messages sent to those numbers may not be captured at all. The only way to know for certain is to ask your carrier and archiving vendor whether RCS is in scope, and to test what actually arrives in your archive when an RCS message is sent to a managed number.
If we disable RCS to force SMS fallback, how do we know the fallback is actually working?
You don’t, automatically. Fallback behavior depends on the sender’s device, OS version, and carrier, none of which you control. The only reliable way to verify is to test it regularly using different device types and operating systems. Even then, fallback is not guaranteed in group message threads, where failures can be completely silent on both ends.
Under state public records law, how long do school districts need to retain staff text messages?
School district text message retention requirements vary by state. Most states classify text messages sent or received by public school employees on district-managed devices as public records subject to retention requirements, typically ranging from one to several years depending on the content and classification of the record. Some states have issued specific guidance on electronic communications; others apply general records schedules. Your district’s records officer or legal counsel should be the primary reference here, as requirements are updated periodically and vary in specificity.
What’s the risk if a parent files a public records request and we can’t produce text messages that should have been archived?
The exposure depends on your state’s public records law, but the consequences can include formal complaints to your state’s records management authority, civil penalties, court orders requiring production, and reputational damage if the gap becomes public. In some states, intentional destruction or failure to preserve public records carries additional penalties. The safer position is to document the gap, document the steps taken to address it, and demonstrate good-faith compliance efforts.
Should staff be using personal phone numbers to communicate with parents at all?
This is a policy question as much as a technology one, and it’s worth revisiting if your district doesn’t have a clear answer. Communications sent from personal devices on personal numbers are generally outside the reach of your archiving solution entirely, which creates both a records retention gap and a potential compliance exposure. Many districts are moving toward requiring all parent-staff communication to occur through district-managed channels, whether that’s a managed phone number, a communication platform, or a supervised messaging app.
Is this only a problem for K-12, or do other regulated industries face the same issue?
The same architectural gap exists across any industry that relies on carrier-level SMS archiving while staff or clients communicate via iMessage or RCS. Financial services firms subject to FINRA and SEC recordkeeping rules, healthcare organizations with HIPAA obligations, and government agencies under FOIA and Sunshine Laws all face the same underlying problem. The K-12 context makes it particularly visible because staff routinely receive messages from members of the public on personal devices outside the district’s control.
We’re mid-contract with our current archiving vendor. What should we do in the meantime?
Start by documenting what your current solution captures and what it doesn’t. If there’s a known gap, RCS, iMessage, or both, document the steps you’ve taken to address it and any guidance received from your vendor. This creates a defensible record that demonstrates good-faith compliance efforts while a longer-term solution is evaluated. In parallel, review whether your district’s communication policies need to be updated to reflect current messaging realities.
Read Next:iMessage Compliance in Business: Challenges, Risks, and Solutions SMS vs. iMessage: Pros, Cons, and Key Differences Can You Archive iMessages? How iMessage Compliance Recording Works |
