Setting Consent at the Email Template Level
Some messages may not require a consent check when users send an approved email. Setting consent at the template level allows content admins to control which messages require a consent check. Each approved email template includes a picklist content admins can use to specify whether a template always checks for consent, never checks for consent, or defaults to the consent behavior of the entry point.
If a consent check is set for a template, end users are prompted to capture consent before sending the email.
Who can use this feature?
- Content Admin Users — Browser
- Setting Consent at the Email Template Level
- End Users — Browser, iPad, iPhone
- Using Consent at the Email Template Level
- Users require an Approved Email license
Configuring Setting of Consent at the Email Template Level for
All Users
To configure this feature, ensure Configuring Approved Email is complete.
Setting Consent at the Email Template Level as
Content Admins
To set consent, check requirements for an email template :
- Navigate to the appropriate email_template__v record.
-
Populate the Check Consent picklist with the appropriate value:
The Check Consent picklist is empty at initial configuration and it behaves as if a Default value is selected.
- Yes – The template always checks for consent regardless of the entry point
- No – The template never checks for consent regardless of the entry point. If the template is sent to an account with an approved_email_opt_type__v field of Never, the template still does not check for consent.
- Default – The template checks for consent based on the behavior of the relevant Approved Email entry point
The following entry points do not check for consent when Default is selected:
- Engage
- Medical Inquiries
- Case
- Receipts
- Double Opt-in
- Select Save.
Receipts and Double Opt-In emails always send to recipients without checking for consent, regardless of the value of the check_consent__v field.
Setting the Check Consent picklist to Yes means the system checks if consent is required to send the email. It does not mean consent is needed to send the email. For example, if a template with the Check Consent picklist set to Yes is sent to an account whose Consent Type is Opt-in Not Required, the email can be sent even though consent was not captured.
Using Consent at the Email Template Level as
End Users
When an end user sends an Approved Email, Vault CRM checks for consent. If the end user did not captured consent from the recipient, the end user is blocked from sending the email and is prompted to capture consent.
