Namirial Notify provides different services for different delivery and interaction models. This page explains the key distinctions between them and helps you choose the right service for your use case.
For a full scenario guide and feature comparison, see Services.
| Service | Where certified content lives | What it mainly certifies | Choose it when |
|---|---|---|---|
| EviNotice | Hosted on the Namirial Notify platform | Access to a hosted notice and recipient actions on the platform, including acceptance, rejection, or rejection without opening | Recipients must access and interact with certified content in a controlled environment |
| EviMail | The email message delivered to the inbox | Sending and delivery of the email to the inbox, and optionally opening or acceptance or rejection | The message itself must arrive in the recipient’s inbox |
| EviSMS | The SMS or RCS message delivered to the device | Sending and delivery of the message to the device, and optionally opening | Short certified content must reach a mobile number directly |
| EviSign | The signing workflow and its outcome | Signer access, acceptance, rejection, and signed documents | The main objective is to collect an electronic signature on a document |
| EviPost | The physical letter delivered through the postal process | Dispatch and postal delivery outcome, with additional postal-processing steps where supported | Certified content must be sent as physical mail |
These services all contact recipients through messaging channels, but they differ in where the certified content lives and what evidence is recorded.
- In EviMail and EviSMS, the certified content is delivered directly in the email, SMS, or RCS message itself. Evidence focuses on what happens to that message during sending, delivery, and, where supported, opening.
- In EviNotice, the email, SMS, or WhatsApp message is only the notification. The certified content is hosted on Namirial Notify and accessed through a secure link. Evidence focuses on what the recipient does on the platform.
- Use EviMail or EviSMS when the communication itself must arrive in the recipient’s inbox or messaging app.
- Use EviNotice when the recipient must access the content in a controlled environment and you need evidence of their interaction with it.
With EviNotice, a recipient can reject a notice without opening it. This action generates its own affidavit, providing evidence of explicit refusal. See EviNotice for details.
- EviSign is a workflow for collecting signatures, approvals, or rejections on documents.
- Use EviSign when signer actions are the main objective.
- Use EviNotice, EviMail, EviSMS, or EviPost when delivering information is the main objective.
- EviPost is the physical-channel option. It depends on postal operations and timelines rather than immediate digital delivery.
- Use EviPost when the process requires postal delivery, paper handling, or postal proof rather than digital access.
- EviNotice — send a confidential notice that the recipient must access through a secure link
- EviMail — send a certified message directly to an inbox
- EviSMS — send a short certified mobile communication
- EviSign — send a contract for signature
- EviPost — send a certified physical letter
- For a detailed comparison table and scenarios, see the Services overview.
- Read the service overview that matches your use case:
- Review States and outcomes to understand status changes and final results.
- Review Evidence and affidavits to understand what each service records and certifies.