# Services

This page compares the Namirial Notify services and explains when to use each one.

- For the product-level overview and role-based entry points, see the [Namirial Notify homepage](/products/namirialnotify/homepage).
- For definitions of evidence, affidavits, and lifecycle states, start from the [User Guides](/products/namirialnotify/user-guides).


## Service overview

| Service | Channel | Choose when | What it records | Learn more |
|  --- | --- | --- | --- | --- |
| **EviNotice** | Email / SMS / RCS / WhatsApp (notification) + platform (content) | You need recipients to access certified content inside Namirial Notify — especially when they must identify themselves or interact with the content on-platform | Evidence of notice publication, access, and recipient actions on the platform, including acceptance, rejection, and — depending on configuration — identity verification | [EviNotice](/products/namirialnotify/services/evinotice) |
| **EviMail** | Email | You need to deliver certified content directly to an email inbox | Evidence of processing, sending, delivery to the provider or device, and optionally opening and acceptance/rejection, with timestamps for each relevant event | [EviMail](/products/namirialnotify/services/evimail) |
| **EviSMS** | SMS / RCS | You need to deliver certified content to a phone via SMS/RCS — best for short, time-sensitive messages | Evidence of processing, sending, delivery to the provider or device, and, for supported RCS flows, optionally opening/read evidence, with timestamps for each relevant event | [EviSMS](/products/namirialnotify/services/evisms) |
| **EviSign** | Electronic signature workflow | You need to collect an electronic signature on a document | Evidence of signature workflow events, including access, acceptance, rejection, and the signed output | [EviSign](/products/namirialnotify/services/evisign) |
| **EviPost** | Physical mail | You need to send certified content via physical mail | Evidence of printing, dispatch, and postal delivery outcomes | [EviPost](/products/namirialnotify/services/evipost) |


## EviNotice vs EviMail and EviSMS

These services can look similar because all of them contact recipients. The key difference is **where the certified content lives** and what recipient actions can be recorded with probative value.

**Where does the certified content live?**

- **EviNotice**: the certified content is hosted on the Namirial Notify platform; email/SMS/RCS/WhatsApp are used to notify the recipient and provide access; evidence focuses on access and on-platform actions.
- **EviMail / EviSMS**: the certified content is the message delivered to the inbox/app; evidence focuses on delivery events for that message.


| Aspect | EviNotice | EviMail / EviSMS |
|  --- | --- | --- |
| Certified content is | A hosted notice on the platform | The delivered message |
| Recipient access | Secure link to the platform (may require authentication) | Inbox or messaging app |
| What you mainly prove | Access and recorded actions on a hosted notice | Sending and delivery of a specific message |
| Recipient actions with probative value | Acceptance, rejection, or — notably — refusal *without opening*, each generating a separate affidavit | Opening, acceptance, rejection (only available for EviMail when configured) |


In practice:

- Use **EviNotice** when you need to prove that the recipient accessed a notice and took a recorded action on it — or explicitly refused it without opening it — inside the platform.
- Use **EviMail** or **EviSMS** when the message body itself is the certified content, and you need to prove that Namirial Notify sent and delivered it to the recipient's inbox or messaging app.
- Avoid EviMail or EviSMS if you need detailed evidence of what the recipient does *after* receiving the message — these services do not track on-platform interaction.
- Avoid EviNotice if the certified content needs to reach the recipient's inbox or messaging app directly, with no platform login or access step required.


**Note**: With EviNotice, a recipient can refuse a notice without opening it. This action generates its own affidavit, providing evidence of explicit refusal. See [EviNotice](/products/namirialnotify/services/evinotice) for details.

## How to choose

| Scenario | Recommended service |
|  --- | --- |
| Deliver a formal notice that recipients must access and interact with on-platform | EviNotice |
| Send a certified email with delivery evidence | EviMail |
| Send a short certified SMS alert or notification | EviSMS |
| Collect an electronic signature on a document | EviSign |
| Send a certified physical letter | EviPost |


## Related concepts

- [States and outcomes](/products/namirialnotify/user-guides/states-outcomes)
- [Evidence and affidavits](/products/namirialnotify/user-guides/evidences-affidavits)
- [Archiving](/products/namirialnotify/user-guides/archiving)