This option is available only with the Pro or Multi-account monthly billing plans and with the Pay As You Go plan.

The mandatory content setting allows you to differentiate between opt-in emails and mandatory or regulatory messages that contacts shouldn’t be allowed to unsubscribe from.

Any email designated as "mandatory" will be sent to all contacts on the target list, even if they are unsubscribed from optional communications. An exception is for contacts that have reported the emails as spam either internally on the Envoke email preferences page or externally to their email provider.

This is to accommodate situations where a recipient is obligated to receive messages from you - often as a result of an internal contract. Examples of this are students of a university, members of a professional body or other contacts who need to receive information pertaining to their safety, membership or enrolment.

The mandatory email option doesn't mean that the unsubscribe link is removed from emails, instead it's a way to differentiate between mandatory and optional communications. Read more about customizing the unsubscribe process.

This functionality is enabled upon request by Envoke support. Start a support ticket using the support chat while you're logged into your account.

It's recommended to add custom text to the Email Preferences Page to explain to your contacts what types of mandatory emails you send and how recipients can contact you for further information about these messages.

Account administrators and subaccount administrators can designate emails as mandatory on the email editor page.

When you designate a message as mandatory, you need to provide a reason for this. This is shown to contacts in the footer of emails.

If you're using a custom footer then you need to add the following merge field to your email manually to show the reason for sending the mandatory message:

{@msg-mandatory_reason}

You can add it anywhere in the message. The most common placement is in the footer.

Tip: Consider adding this macro to your template(s) so messages created from these templates will automatically include the merge field and eliminate the need to add it manually to each message.

When the message is sent, this macro will be replaced with the mandatory message reason you provided.