Skip to content
Last updated

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.
  • For definitions of evidence, affidavits, and lifecycle states, start from the User Guides.

Service overview

ServiceChannelChoose whenWhat it recordsLearn more
EviNoticeEmail / 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-platformEvidence of notice publication, access, and recipient actions on the platform, including acceptance, rejection, and — depending on configuration — identity verificationEviNotice
EviMailEmailYou need to deliver certified content directly to an email inboxEvidence of processing, sending, delivery to the provider or device, and optionally opening and acceptance/rejection, with timestamps for each relevant eventEviMail
EviSMSSMS / RCSYou need to deliver certified content to a phone via SMS/RCS — best for short, time-sensitive messagesEvidence of processing, sending, delivery to the provider or device, and, for supported RCS flows, optionally opening/read evidence, with timestamps for each relevant eventEviSMS
EviSignElectronic signature workflowYou need to collect an electronic signature on a documentEvidence of signature workflow events, including access, acceptance, rejection, and the signed outputEviSign
EviPostPhysical mailYou need to send certified content via physical mailEvidence of printing, dispatch, and postal delivery outcomesEviPost

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.
AspectEviNoticeEviMail / EviSMS
Certified content isA hosted notice on the platformThe delivered message
Recipient accessSecure link to the platform (may require authentication)Inbox or messaging app
What you mainly proveAccess and recorded actions on a hosted noticeSending and delivery of a specific message
Recipient actions with probative valueAcceptance, rejection, or — notably — refusal without opening, each generating a separate affidavitOpening, 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 for details.


How to choose

ScenarioRecommended service
Deliver a formal notice that recipients must access and interact with on-platformEviNotice
Send a certified email with delivery evidenceEviMail
Send a short certified SMS alert or notificationEviSMS
Collect an electronic signature on a documentEviSign
Send a certified physical letterEviPost