New EviNotice
- Pablo Garcia Gonzalez
- Raquel Sedano
- Jose Luis Lozano
EviNotice is an advanced solution that allows the sending of certified electronic notifications with acknowledgement of receipt, in a secure and traceable way through multiple channels, such as: email, SMS and WhatsApp, with full legal validity and in which the content, sender, recipient and each step of the communication process is certified.
Notification received by email: Notification that allows to view the content sent and it can take any action on it if requested.
Notification received by SMS: Notification, sent by SMS, with an informative text for the recipient and a link through which he/she can read the content and respond to it on request.
Notification received by WhatsApp: Notification, sent using WhatsApp messaging application, with an informative text for the recipient and a link through which he/she can read the content and respond to it if requested.
The opening of the link on Evicertia website allowing the receiver of the notification to access the message and its content in an absolutely safe way since at no point there is information that travels unencrypted over the Internet, since in order to access the content, you navigate via HTTPS (or encrypted web traffic).
To send a new EviNotice from Evicertia website, there are two options:
From the main window, select the option Electronic notification, and on the right, Submit now.
From the upper drop-down menu, select New... And then, EviNotice
Video demo
Watch the demo video to learn more about the product. Discover how to create an EviSMS step by step.
Fields to fill in:
The screen where EviNotice is configured is the one shown in the following figure.
Content
In this section you can configure the recipients, the content of your mailing, attachments and other customisable details.
Security level: It specifies the level of certification that will be applied to the message. To see the different levels of certification, consult the following link.
Recipients: Details of the person or company that will appear as the recipient of the notification. The details can be configured in the box that appears when entering the email address or mobile phone number. For multiple sending see the Batch Sending functionality
From : E-mail address with which the FROM of the EviNotice will be configured. The submit will validate that the address is configured in the sending user's account and that the domain is verified.
Disable Sender Header: Disables the display of the Sender in notification emails. It has FALSE value by default; in case of being informed with TRUE value, the display of the Sender in the notification emails will be disabled. It can only be used in case the FROM is being modified.
Note: Disabling this option may affect the traceability of the EviMail, as this sender is used to make status updates by means of the replies made by the recipient's mail server
ReplyTo : E-mail address with which the reply-To and in-Reply-to header of the e-mail sent to the signatory is configured.
Report to: Recipient’s email address or mobile phone number.
Name: Name of the person or company to whom the notification is sent.
Legal Identification: Identification number of the person or company (NIF, CIF, RUC, RUT, Passport etc.)
Signature Method: It is the method that will be used so that the recipient can access the content of the communication:
Click on web through safe link or locator: The recipient will be able to access the content by clicking on the corresponding button.
Challenge question/answer: The recipient will be able to access the content of the communication if he correctly answers the question asked. This question and its correct answer are configured when the notification is issued.
Security code PIN sent to mobile phone: The recipient will be able to access the communication if he knows the secret number that was sent to his mobile phone. This phone number will be specified when the notification is issued.
Enable PIN sending by WhatsApp: Select whether the signer can request the signature pin by WhatsApp
Disabled: The WhatsApp channel is not enabled to send the PIN. Corresponds to the Normal delivery policy (by SMS).
Enable sending by WhatsApp instead of SMS: The WhatsApp channel is enabled to send the PIN as an alternative to SMS.
Enable WhatsApp for sending retries only: The WhatsApp channel is enabled to send the PIN only on retry.
Security code PIN sent to email: The recipient will be able to access the communication if he knows the secret number that was sent to his email address. This address is specified when the notification was issued.
*Note: The PIN code has a life time of 60 minutes, after this time it will be necessary to request another PIN code. The number of 9 attempts to correctly enter the PIN code sent is also established.
In addition, in this icon 
Edit the issuer‘s data: Set of data that identifies the issuer of the EviNotice.
Subject: Short description of what you want to communicate to the notification‘s receiver. This text is the one that will appear as visible when the link is opened and before you log in to read the content.
Content: Field where the sender writes what he wants to tell the receiver.
Attach files: In this section, the files that you want to go along the notification will be attached. In this section, the limits on the size of the files, the files to be attached or the maximum size of the messages are reported.
Configuration
In this section you will find the customisation elements that can be configured when sending EviNotices.
Processing and certification: Date until which the message will be tracked. It is the life time parameter of the message and involves that once this date is reached, delivery attempts will no longer be made, and in case of standard certification, this would be the moment when a summary Affidavit is generated.
Tracking until: Date until which the message will be tracked. It is the message life time parameter of the message and involves that once this date is reached, delivery attempts will no longer be made, and in case of standard certification, this would be the moment when a summary Affidavit is generated.
Language of Affidavits: It allows to choose between the languages of the drop-down and causes the affidavits to be generated in the chosen language.
Affidavit Kind: Choose the Affidavits you want to be generated in your delivery. Depending on the level of certification selected (Advanced, Standard or QERDS) the default Affidavits vary.
Agreement: In this section you can select the options you want the receiver to have (accept, reject, refuse), allow comments, even write the options yourself, and set as a requirement for acceptance or rejection these comments.
Allow notification refusal: This parameter enables the receiver to refuse to see the content of the notification and to record it. When the recipient clicks on the notification link, they will be shown a page with the options to read the message or decline the message.
Chances for agreement: This parameter provides the receiver with the possibility of showing his agreement or disagreement with the content If this parameter is enabled and the receiver makes an option, an affidavit will be generated with the result of his decision. It admits the following values:
Disabled: In this case, there is no possibility for the recipient to accept or reject the content of the communication.
Accept: The receiver is allowed to accept the content of the message or do nothing.
Reject: The receiver is allowed to reject the message or do nothing.
Accept or reject: The receiver is allowed to take one of both options.
Allow comments: This option will appear only if one of the following agreement possibilities has been enabled (accept, reject, accept or reject), it will allow the recipient to add comments when accepting or rejecting. This comments will appear in the corresponding Affidavit.
Language of notifications: It allows you to select the language in which the recipient will receive the notifications.
Advanced
Reminder Options: In this section you can configure the waiting time for the reminder to be sent and the days for it to be sent and even the timetable.
Cost Centre: Code of the centre to which the EviNotice consumption will be allocated.
Templates: It allows to define content templates.
Custody: Configure how you want your delivery to be archived.
Retention Period: Time in years that a recipient can access custody of evidence. Default value is 1 year. This parameter is important for invoicing purposes.
Custody Access Control: It defines the way in which the content under custody can be accessed when the reference URL is known. You can take the following values:
LTA Custody: Allows to activate the custody in Namirial Archive.
Informative texts: Additional information you want to include on the notification web page.
Push Notifications: Events to which the sender can subscribe and receive information on the URL defined in the previous parameter the different events that his sending goes through (processed, sent, dispatched, delivered, received, read, replied, failed, closed and affidavit published). Link.
Push Notification URL: Indicates the url where you want to receive information about the events that occur during the lifetime of the evidence.
*Notarial Deposit: If this check is enabled, the evidence generated will be deposited with a notary public for a period of 5 years.
*Notary: It allows to choose in which notary the evidence will be deposited.
*This functionality is only available in certain territories. Ask your sales contact to check availability.
Preview
This is a rough preview of what your message will look like.
