Skip to main content
hamburger menu Created with Sketch.
Veeva Support US Holiday: Nov 28th - Nov 29th - Limited staff, please plan accordingly. Updates were made to the Support and Services ticketing processes. Click the link below the search bar for more information.

Search the Knowledge Base

How to Identify the Certain Types of Consent Capture Confirmation Level Setups in Veeva CRM?

  • Updated

Question:

How to Identify the Certain Types of Consent Capture Confirmation Level Setups in Veeva CRM?

Answer:

The purpose of this article is to focus on these Consent setups particularly, focusing on the levels of consent confirmation:

  1. Consent Capture
  2. Consent Capture With Consent Receipt
  3. Consent Capture With Double Opt-in
  4. Consent Capture With Double Opt-in Instead of Signature
  5. Capturing Consent Using Confirmation Emails for All Channels

Scenario 1. Consent Capture

In the basic Consent Capture functionality, the customer controls the consent options in the CRM instance. A signature may or may not be required. No Multichannel Routing or Multichannel Message setups are required.

Scenario 2. Consent Capture With Consent Receipt

In the event, Consent Receipts are enabled, this can be verified by checking the Request Receipt field on the relevant Consent Header record(s). If it is enabled, and the other related requirements (Such as Multichannel Routing) are configured properly, a Receipt Email is sent out. No confirmation is required from the HCP, consent is immediately captured. A unique Multichannel Routing setup is required. Multichannel Message setup is not required.

The following screenshot presents an example of the presence of the Consent Receipt functionality. Fields - With which the functionality can be recognized - are emphasized.

mceclip1.png

Scenario 3. Consent Capture With Double Opt-in

In case Double Opt-in is enabled, this can be verified on the relevant Consent Type record(s). If the Double Opt-in field is checked, and the other related requirements are configured properly, a Confirmation Email is sent out, via which the HCP confirms the consent. The consent gets captured with this method. A unique Multichannel Routing setup is required. A multichannel Message setup is required. The Confirmation Email Template must contain the reference for the Multichannel Message.

The following screenshot presents an example of the presence of the Double Opt-in functionality. Fields - With which the functionality can be recognized - are emphasized.mceclip2.png

 

Note: The Record Type Name may refer to the Custom Record types of specific Consent Types.

Scenario 4. Consent Capture With Double Opt-in Instead of Signature

This setup is the same as the one described in Point 3, the only difference is that the Double Opt-in Instead of Signature field is checked on the relevant Consent Type record(s). This provides the option for the end user to either use the Double Opt-in Confirmation method or just simply capture consent from the HCP in person via signature.

Scenario 5. Capturing Consent Using Confirmation Emails for All Channels

This functionality overrides Double Opt-in. Its purpose is the following, quoting the CRM Help Documentation Capturing Consent Using Confirmation Emails for All Channels:

To capture consent when users are unable to meet HCPs face-to-face, users can send confirmation emails to confirm opt-in consent for any channel, including custom channels.

For example, during a phone call with Dr. Clinton Ackerman, Sarah Jones requests Dr. Ackerman’s consent for email and SMS communications about Cholecap. Sarah selects the Email method on the Consent Summary screen to capture his consent. Dr. Ackerman receives an email with a link to confirm his consent. He selects the link, which displays a message listing the channels and products he opted in to and a button to confirm consent. He selects the confirmation button, which confirms his consent and displays a confirmation message.

This setup can be recognized by the presence of the Allow Confirmation By Email Checkbox on the Consent Header record(s). If it is enabled, that indicates the intention to use this functionality. It has a special Multichannel Routing setup requirement, which is not the same as the one commonly used by the Double Opt-in functionality. A multichannel Message setup is required. The Confirmation Email Template must contain the reference for the Multichannel Message.

The following screenshot presents an example of the presence of the Capturing Consent Using Confirmation Emails for All Channels functionality. Fields - With which the functionality can be recognized - are emphasized.

mceclip3.png

Notes:
  • There are more combinations, options, and special scenarios possible. Some of these examples and unsupported scenarios are referenced in the knowledgebase section below.
  • Multichannel Routing records may be used for other supported functionalities as well. These are specific Receipts for Signature transactions. This article does not focus on them.
  • The presented data is not customer specific.

Related Documentation:

CRM Help Documentation: 

Knowledgebase:

Powered by Zendesk