A messaging app is a place to write and read messages. It may use several different delivery systems. Knowing which system a particular conversation uses makes it easier to explain failed texts, changed photo quality, missing group replies, and privacy differences.
Identify the service before changing settings
SMS is the basic carrier text service; MMS adds media and commonly supports older-style group messaging. RCS adds richer messaging through compatible apps and carrier support. iMessage is Apple's messaging service. A phone can switch between available services, so successful delivery yesterday does not prove that today's message follows the same route.
Scroll sideways on a small screen to compare all columns.
| System | Typical role | Connection and support | Privacy check |
|---|---|---|---|
| SMS | Plain carrier texts. | Carrier texting service; supported Wi-Fi Calling can also carry SMS. | No end-to-end encryption. |
| MMS | Carrier media and group messages. | Carrier provisioning and a supported data connection; attachment limits vary. | No end-to-end encryption. |
| RCS | Richer media, delivery indicators, and group features. | Compatible participants, apps, carrier support, and data or Wi-Fi. | Check the actual conversation's encryption indicator. |
| iMessage | Messaging between Apple devices. | Apple service registration and data or Wi-Fi. | End-to-end encrypted delivery; review stored copies separately. |
Apple's explanation of message types distinguishes iMessage from carrier RCS and SMS/MMS. Message color can identify some differences within an app, but it is not a universal system across Android and iPhone. Read the label in the composing area or conversation details.
Do not confuse read receipts with agreement. A delivery indicator is not confirmation that the intended person understood a request, and an absent read receipt does not prove they ignored it. For an important change of plans, ask for a reply that confirms the details.
RCS encryption is a conversation-level check
Checked September 6, 2026: Apple says end-to-end encrypted RCS is available in beta from iOS 26.5 with supported carriers and a gradual rollout. All participants' carriers must support it. An encrypted RCS conversation shows an “Encrypted” label and lock at the top. A green bubble alone does not tell you whether that protection is present. See Apple's current RCS requirements and indicators.
For eligible RCS chats between Google Messages users, Google describes automatic end-to-end encryption and lock indicators, including a lock on the send button. Google also explains that SMS/MMS does not provide that protection. Cross-platform support continues to evolve; inspect the current conversation rather than assuming that every RCS chat has identical capabilities.
If a failed rich message is resent as SMS, the delivery method changes and so does its protection. Decide whether to wait, switch to a mutually supported encrypted service, or send non-sensitive information by another route. Delivery convenience should be a conscious choice.
Encryption in transit does not prevent screenshots, recipient sharing, notification exposure, or every form of backup access. The Cell Phone Privacy guide covers those separate boundaries.
Diagnose the smallest failing part
A message will not send
Check the intended recipient, active phone line, signal or data connection, and the displayed message type. Try one short, non-sensitive message to a consenting contact. If only one conversation fails, compare its address and participants before changing the whole phone.
Google's Messages troubleshooting guide starts with items such as the default SMS app, SIM, plan, balance, and connection. On iPhone, Apple's send-and-receive troubleshooting covers retrying a failed message, checking the selected number, and carrier support. Follow the branch matching the failure; avoid deleting conversations as your first experiment.
A photo or video arrives blurry
Compare the original file with the received copy and note whether the message used MMS, RCS, or iMessage. Apple notes that carrier attachment limits can lead to compression. Also check whether a low-quality or preview option is enabled. “Rich messaging” does not promise that every app setting preserves an original file unchanged.
When the exact original matters, use an agreed file-sharing method that preserves the file and allows you to control access. Verify the recipient can open it and check its dimensions or file size. A publicly accessible link is not a privacy improvement merely because the attachment looks sharper.
A group splits or a participant disappears
Check whether everyone is addressing the same numbers or account addresses, whether someone left the group, and which system the group uses. A mixed group may behave differently from a one-to-one chat. After confirming addresses, start a small test group rather than repeatedly resending the important announcement to a possibly broken thread.
Messages go missing after a phone or carrier change
First confirm that the number transfer has completed using Number Portability. Then check which number the messaging app has registered. Apple documents checking Send & Receive and deactivating iMessage when moving to a non-Apple phone; Google provides its own guidance for RCS registration and message reception after switching. Use those official flows rather than assuming the old device should keep receiving indefinitely.
Keep a short troubleshooting record
Download the message test log (CSV). It records the app, connection, message type, result, and one change made. Use contact labels rather than telephone numbers and omit message contents. Record what you observed instead of guessing what the network did internally.
If you involve an AI assistant in troubleshooting, describe the error and settings using fictional contact details. Its role is to help organize checks, not to certify that a private conversation is encrypted. When generating a reply, review names, dates, quantities, and commitments before sending; polished wording can still say something you did not intend.
Once you find a repeatable failure, give support the smallest useful record: device and app versions, service type, approximate time, and the exact error. This is more actionable than changing several settings at once and losing track of which one mattered.