# How a recipient receives an EviSMS This guide explains what recipients typically see when they receive an EviSMS and how they read the certified communication on their mobile device. Exact wording, sender details, mobile appearance, and supported features can vary by issuer configuration, device, carrier, and whether the communication is delivered through SMS or RCS. This guide describes the standard EviSMS recipient flow, where the certified content is delivered directly in the mobile message. ## What an EviSMS looks like for a recipient In standard EviSMS integrations, the certified content is delivered directly in the SMS or RCS message. Depending on configuration, you may receive the communication as: - an SMS message - an RCS message - a channel selected based on configuration, delivery path, and device or network conditions Depending on the selected channel, the message may show: - the sender or issuer identification - the message text itself as the certified content - a visual indicator that identifies the communication as certified, where the selected channel supports it ![Example EviSMS notification displayed in a mobile messaging app with a link to the certified content](/assets/recipient-evisms-message.352ad67e2c5e22ea3b5b32e335b3f56c30e94aec1ee422c3ad1fe38e5f07f172.6fd6141d.png) ## Before you start Before using this guide, make sure that: - you have access to the mobile number where the communication was sent - your device can receive SMS messages, or RCS messages if that channel is supported on your device and network - you can open the messaging app or client where the communication arrived - if you have questions about the message content, you know who the issuer or sender is ## Open the message 1. Open the messaging app on your mobile device. 2. Open the EviSMS or RCS conversation you received. 3. Review the sender identification and message text. 4. Confirm that the communication is the one you expect. ## Read the message content In the standard flow, the certified content is the SMS or RCS text itself. 1. Read the message directly in the SMS or RCS conversation. 2. Review the full text if the communication is split across multiple SMS segments. 3. Keep the message available in your device if you need to refer to it later. If the issuer configured multiple delivery channels, the communication may arrive as RCS on some devices and as SMS on others. This can change the visual appearance of the message without changing the communication purpose. ## What to expect from EviSMS EviSMS is designed for mobile delivery. In common recipient flows: - you receive the communication on your phone by SMS or RCS - the certified content is delivered in the message itself - you do not normally complete an accept or reject workflow as part of standard EviSMS If your process requires formal acceptance or rejection by the recipient, the issuer typically needs to use another service, such as [EviMail](/products/namirialnotify/services/evimail) or [EviNotice](/products/namirialnotify/services/evinotice). ## Expected result You receive the certified communication on your mobile device and read the content directly in the SMS or RCS channel. Namirial Notify can record that the message was sent, delivered, and, where supported, read. ## What can be recorded as evidence For EviSMS, Namirial Notify can record evidence for: - message sending - delivery to the recipient's device - message opening or reading, where the selected channel and configuration support that event EviSMS does not generally use the same formal acceptance or rejection workflow as EviMail or EviNotice. In legacy configurations where the mobile message contains a link to a hosted page, the interaction model can resemble EviNotice. In those cases, follow [How a recipient receives an EviNotice](/products/namirialnotify/recipient/receive-evinotice) for the hosted-page steps. ![EviSMS evidence timeline](/assets/evisms_timeline.997e0aa43a983d456a28ddcb49214bbc55a6a9435c6b42b8e40f814930bf1c69.6fd6141d.png) For more detail on affidavit kinds and evidence interpretation, see [Evidence and affidavits](/products/namirialnotify/user-guides/evidences-affidavits) and [States and outcomes](/products/namirialnotify/user-guides/states-outcomes). ## Troubleshooting ### I did not receive the message **Problem:** You expected an EviSMS, but no message arrived on your phone. **Cause:** Delivery may still be in progress, the message may have been sent to another number, or the selected mobile channel may not have completed delivery. **Solution:** 1. Confirm that you are checking the correct mobile number and device. 2. Wait a moment and check again. 3. Confirm that your device can receive normal SMS messages. 4. Contact the issuer if the message still does not arrive. ### I expected an RCS message but received SMS instead **Problem:** You expected a richer RCS message, but the communication arrived as a standard SMS. **Cause:** RCS may not be available for your device, carrier, or delivery path, and the process may have fallen back to SMS. **Solution:** 1. Read the message normally in SMS format. 2. Do not assume the communication is incorrect only because the appearance is simpler. 3. Contact the issuer only if the message content appears incomplete or inconsistent. ### The message looks incomplete or split **Problem:** The communication appears in several SMS parts or does not look like a single message. **Cause:** Longer SMS content can be delivered as concatenated message segments, and the final appearance depends on the messaging app and device. **Solution:** 1. Open the full conversation thread. 2. Read all message segments in order. 3. Contact the issuer if part of the message appears to be missing. ### I expected accept or reject options but I do not see them **Problem:** You expected a formal response workflow, but the message contains only text. **Cause:** Standard EviSMS does not generally include the formal acceptance or rejection flow used by other services. **Solution:** 1. Read the communication as a direct mobile message. 2. Contact the issuer if you need to confirm whether another response step is expected. ### I have a question about the message content **Problem:** You need clarification about the communication or requested action. **Cause:** Namirial Notify delivers and records the EviSMS, but the business content comes from the issuer. **Solution:** 1. Identify the issuer or sender information shown in the message. 2. Contact the issuer directly for clarification or next steps. ## Related - [Recipient User Manual](/products/namirialnotify/recipient) - [EviSMS](/products/namirialnotify/services/evisms) - [EviMail](/products/namirialnotify/services/evimail) - [EviNotice](/products/namirialnotify/services/evinotice) - [Services](/products/namirialnotify/services) - [States and outcomes](/products/namirialnotify/user-guides/states-outcomes) - [Evidence and affidavits](/products/namirialnotify/user-guides/evidences-affidavits)