Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/ConsentCapture/CreateManageConsent/ConsentConfirmationEmails.htm

## Using Approved Email for Consent Confirmation

End users can send consent confirmation emails to HCPs when using double opt-in or when capturing consent using confirmation emails for any channel. Using consent confirmation emails allows users to capture consent for HCPs even when meeting remotely.

**Who can use this feature?**

* Business Admin Users - Browser
* [Set up consent confirmation emails](#SetUp)
* [Expire pending consent records](#Expiring)
* End Users - Browser, iPad, iPhone, Windows
* [Resend consent confirmation emails](#Resending)
* HCPs - Browser, iPad, iPhone
* [Confirm consent via confirmation emails](#Confirming)
* Users require an Approved Email license

### Configuring Consent Confirmation Emails for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)All Users](#)

Ensure [Configuring Consent Capture](../CCConfiguration.htm) is complete.

### Setting Up Consent Confirmation Emails as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

Business admins can customize the email template of the confirmation email used for double opt-in and consent via confirmation email. The email contains the list of channels for which the HCP is opting in and a link which displays a confirmation message when selected.

To properly set up a consent confirmation email, business admins must perform the following steps:

1. Ensure one of the following features is configured:
   * [Using Double Opt-In](../CaptureConsent/DoubleOptIn.htm)
   * [Capturing Consent Using Confirmation Emails for All Channels](../CaptureConsent/ConfirmationEmailAllChannels.htm)
2. Define the confirmation message.
3. Create the email content.
4. Link the email template to the appropriate consent header.

#### Defining the Confirmation Message

1. Navigate to **Business Admin > Objects > Multichannel Messages**.
2. Select **Create**.
3. Select the **double\_opt\_in\_\_v** object type.
4. Populate at least the following fields:

* name\_\_v
* message\_identifier\_\_v
* consent\_confirm\_html\_file\_\_v — Defines the HTML for a confirmation step before confirming consent. This prevents the recipient’s systems from unintentionally confirming opt-in consent for an HCP. Include the following tokens:
  + {{confirmConsent}} — Displays a confirmation button. Must use the following format:

    [Copy](javascript:void(0);)

    Confirmation button example

    ```
    <form method="post">
                                            <input type="submit" name="{{confirmConsent}}" value="Confirm Consent">
                        </form>
    ```

    Selecting this button redirects users to the confirmation message, which displays the content defined in the html\_message\_file\_\_v field.

    ![](../../../../Resources/Images/Multichannel/ConsentCapture/ConfEmails/AddStepMarked.png)
  + {{consentList}} — Displays the list of consent types and lines to opt-in
* html\_message\_file\_\_v — Defines the HTML for the confirmation message

Populating the consent\_confirm\_html\_file\_\_v field is optional. If the field is empty, selecting the link in the email automatically opts the user in and redirects them to the page rendering the confirmation message defined in the html\_message\_file\_\_v field.

#### Creating the Email Content

Next, create an email template in PromoMats/MedComms with the Email Receipt email template type. The HTML of the email template must reference the message\_identifier\_\_v of the appropriate multichannel\_message\_\_v record using the {{approvedEmailAction}} token. See [Tracking Multichannel Activities from Approved Emails](../../ApprovedEmail/ReportAE/TrackMCActivitesAE.htm) for more information about using the token. Admins can also use the {{insertConsentLines}} token to display all opted in consent lines and their consent types in the email. Syncing the email template to CRM creates an approved\_document\_\_v record with the **email\_receipt\_\_v** object type and the email\_html\_\_v field populated.

To host the additional confirmation step and the confirmation message in a custom landing page, admins can include a landing page URL in the {{approvedEmailAction}} token in the email template.

#### Linking the Email Template and Consent Header

Finally, create a multichannel\_route\_\_v record with the appropriate object type to link the email template to the consent lines.

For double opt-in:

1. Navigate to **Business Admin > Objects > Multichannel Routing**.
2. Select **Create**.
3. Select the **double\_opt\_in\_confirmation\_\_v** object type.
4. Enter the following information:

* approved\_document\_\_v = approved\_document\_\_v record for the confirmation email template
* country\_\_v = country\_\_v on appropriate consent\_header\_\_v record
* language\_\_v = language\_\_v on appropriate consent\_header\_\_v record
* object\_\_v = multichannel\_consent\_\_v
* record\_type\_name\_\_v = object\_type\_\_v name of the appropriate consent\_type\_\_v record

For capturing consent for all channels:

1. Navigate to **Business Admin > Objects > Multichannel Routing**.
2. Select **Create**.
3. Select the **consent\_confirmation\_\_v** object type.
4. Enter the following information:

* approved\_document\_\_v = approved\_document\_\_v record for the confirmation email template
* country\_\_v = country\_\_v on appropriate consent\_header\_\_v record
* language\_\_v = automatically populated with the language\_\_v value from the approved\_document\_\_v record
* object\_\_v = multichannel\_consent\_\_v
* record\_type\_name\_\_v = Empty

Additionally, to define a multichannel\_route\_\_v record to use when a consent\_header\_\_v record does not have a multichannel\_route\_\_v record with a matching language\_\_v field, select the **Default** checkbox.

#### Using the Appropriate Multichannel Route Record for Double Opt-In

The following logic determines which multichannel\_route\_\_v record with the double\_opt\_in\_confirmation\_\_v object type is used:

* The multichannel\_route\_\_v record matching the consent header’s language
* If one does not exist, the record matching the account’s language is used
* If one does not exist, the record matching the user’s language is used
* If one does not exist, the default record is used

#### Using the Appropriate Multichannel Route Record for Consent Using Confirmation Emails

If there are multiple multichannel\_route\_\_v records with the consent\_confirmation\_\_v object type for the same country, the following logic determines which record is used:

* The multichannel\_route\_\_v record matching the consent header’s language
* If one does not exist, the record matching the account’s language is used
* If one does not exist, the record matching the user’s language is used
* If one does not exist, the default record is used
* If no default record is set, the first record returned is used

Admins can enable custom sharing rules on the multichannel\_route\_\_v object for Vaults with end users in different countries using the same language. This allows users to sync only the records for their respective countries and prevents the selection of a record with the matching language but the incorrect country.

### Confirming Consent via Confirmation Emails as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)HCPs](#)

After an HCP selects the link from the confirmation email, they must select the confirmation button to confirm their consent. Opt-in consent is confirmed only after the HCP selects the button and the confirmation message displays.

![](../../../../Resources/Images/Multichannel/ConsentCapture/ConfEmails/ConfirmationEmail.png)

![](../../../../Resources/Images/Multichannel/ConsentCapture/ConfEmails/AddStepFull.png)

![](../../../../Resources/Images/Multichannel/ConsentCapture/ConfEmails/ConfirmationMsg.png)

### Resending Consent Confirmation Emails as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

End users can review and resend confirmation emails from the Consent Capture screen.

To view a sent confirmation email, select the **View Email** button beside the consent channel on the Consent Capture screen.

To resend a confirmation email, select the **Resend Confirmation** button beside the consent channel on the Consent Capture screen.

The View Email and Resend Confirmation buttons only display after an HCP opts into a consent line and receives a confirmation email.

### Expiring Pending Consent Records as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Business Admin Users](#)

Capturing consent with confirmation emails creates Opt In Pending multichannel\_consent\_\_v records. To update the consent status to Opt In, the HCP must confirm the consent via the confirmation email. If the HCP never confirms consent, the consent status remains Opt In Pending. While the consent status is Opt In Pending, the end user can resend the confirmation email but cannot capture consent for the HCP from the Consent Capture screen.

To allow end users to capture consent again, business admins can manually expire Opt In Pending multichannel\_consent\_\_v records, which reverts the consent status to the last confirmed status (Opt Out or default consent). Veeva recommends expiring Opt In Pending multichannel\_consent\_\_v records after five to seven days, since HCPs are unlikely to access the confirmation email after that time frame.

To expire a pending consent record:

1. Navigate to **Business Admin > Objects > Multichannel Consents**.
2. Select a multichannel\_consent\_\_v record with the Opt Type field set to **Opt\_In\_Pending**.
3. Select **Edit**.
4. Populate the **Expiration Date** field with the appropriate date. To immediately expire the record, populate the field with today's date.
5. Select **Save**.

### Related Topics

[Using Double Opt-In](../CaptureConsent/DoubleOptIn.htm)

[Capturing Consent Using Confirmation Emails for All Channels](../CaptureConsent/ConfirmationEmailAllChannels.htm)

[Tracking Multichannel Activities from Approved Emails](../../ApprovedEmail/ReportAE/TrackMCActivitesAE.htm)