To configure this feature:

1. Ensure Configuring Approved Email is complete.

2. Grant the following permissions:

To enable this feature:

1. Ensure Configuring Approved Email is complete.
2. Enable Tracking Multichannel Activities from Approved Emails.

3. Grant the following permissions:

4. Ensure all appropriate VMOCs for the sent_email__v object do not have a WHERE clause referencing the sent_datetime__v field. This is because rejected emails do not have a sent datetime. Customers who want to use datetime in VMOCs should reference the capture_datetime__v field.

5. Add the {{requiresReview}} token to all appropriate Approved Email templates.

   This token does not render to end users in Edit or Preview mode of an Approved Email and does not render to recipients.

To enable this feature:

1. Ensure Configuring Approved Email is complete.
2. Grant the following permissions:

When an end user selects Send for an Approved Email including the {{requiresReview}} token, the email does not immediately send to recipients. Instead, the following process occurs automatically:

• The Sent Email’s status is set to Pending, indicating the email must be approved by an enabled reviewer
• The following sent_email_v fields stamp with the following information:
• email_content__v and email_content2__v fields – Stamp with the final HTML content of the email
• subject__v – Stamps with the subject of the sent email

• user_input_text__v – Stamps with any free text or rich text entered by the end user using the following format:

  [{“TOKEN NAME”: “User Input Text},{“TOKEN NAME”: “User Input Text”}]

  For example, [{"customText": "Example"},{"customRichText": "<b>Bold Example</b>"}]

• The Sent Email’s status updates to Pending Approval

End users are notified of rejected emails via a Multichannel Alert. End users can view approved emails on the account’s timeline.

Sent Emails with a status of Pending Approval can be reviewed by users via a customer-defined process and can be either accepted or rejected by updating the status__v field to approved__v or rejected__v.

If the end user does not schedule the email and sends it immediately, the email must be approved by the reviewer within 14 days or else the email will not send even if approved.

When an email is approved or rejected, the following information stamps on the Sent Email:

• review_datetime__v – The datetime of the approval or rejection of the email
• reviewer__v – References the Vault CRM user who approved or rejected the email

If the reviewer approves the email, the email is sent to the recipient when the email is next processed by the integration.

If the reviewer rejects the email, they may enter a reason for doing so in the rejected_reason__v field. Rejected emails are not processed and do not send to recipients.

When a Sent Email is rejected, the Approved Email end user who sent the email is notified of the rejection via an urgent-level Multichannel Alert. This informs end users the email was not sent and also provides an opportunity to learn why the email was rejected to prevent future rejections.

This alert displays the following information to the end user:

• The reviewed datetime as defined in the record’s review_datetime__v field
• The name of the Approved Email template used
• The reason for the rejection as defined in the record’s rejected_reason__v field