To configure this feature:

1. Ensure Configuring Consent Capture is complete.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the appropriate permission set.
4. Select the Objects tab.
5. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   consent_type__v	CRE	messaging__v	channel_label__v channel_source__v consent_custom_duration__v consent_expires_in__v consent_header__v created_by__v created_date__v default_consent_type__v disclaimer_text_file__v display_order__v legacy_consent_channel__v (optional) modified_by__v modified_date__v name__v product_preference__v subscribe_keyword__v unsubscribe_keyword__v zvod_consent_default_consent_text_file__v	Edit
   multichannel_consent__v	CRE	messaging__v	account__v capture_datetime__v consent_header__v consent_type__v created_by__v created_date__v default_consent_text_file__v last_device__v legacy_consent_channel__v (optional) mobile_id__v modified_by__v modified_date__v object_type__v opt_expiration_date__v opt_method__v opt_type__v optout_event_type__v signature__v signature_datetime__v signature_id__v	Edit

1. Ensure Configuring Consent Capture is complete.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the appropriate permission set.
4. Select the Objects tab.
5. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   consent_type__v	R	messaging__v	channel_label__v channel_source__v consent_custom_duration__v consent_expires_in__v consent_header__v created_by__v created_date__v default_consent_type__v disclaimer_text_file__v display_order__v legacy_consent_channel__v (optional) modified_by__v modified_date__v name__v product_preference__v subscribe_keyword__v unsubscribe_keyword__v zvod_consent_default_consent_text_file__v	Read
   multichannel_consent__v	CRE	messaging__v	account__v capture_datetime__v consent_header__v consent_type__v created_by__v created_date__v default_consent_text_file__v last_device__v legacy_consent_channel__v (optional) mobile_id__v modified_by__v modified_date__v object_type__v opt_expiration_date__v opt_method__v opt_type__v optout_event_type__v signature__v signature_datetime__v signature_id__v	Edit

6. Navigate to Admin > Configuration > Objects > User > Layouts.
7. Ensure a User Territory Related Object section is placed on the appropriate layout.
8. Navigate to Business Admin > Objects > User Territories.
9. Create a user_territory__v record for the Engage System User.
10. Populate the Territory field with the root territory.

1. Ensure Configuring Consent Capture is complete.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the appropriate permission set.
4. Select the Objects tab.
5. Grant the following permissions:

   Object	Object Permission	Object Types	Fields	Field Permission
   consent_type__v	R	messaging__v	channel_label__v channel_source__v consent_custom_duration__v consent_expires_in__v consent_header__v created_by__v created_date__v default_consent_type__v disclaimer_text_file__v display_order__v legacy_consent_channel__v (optional) modified_by__v modified_date__v name__v product_preference__v subscribe_keyword__v unsubscribe_keyword__v zvod_consent_default_consent_text_file__v	Read
   multichannel_consent__v	CRE	messaging__v	account__v capture_datetime__v consent_header__v consent_type__v created_by__v created_date__v default_consent_text_file__v last_device__v legacy_consent_channel__v (optional) mobile_id__v modified_by__v modified_date__v object_type__v opt_expiration_date__v opt_method__v opt_type__v optout_event_type__v signature__v signature_datetime__v signature_id__v	Edit

Optional Configuration

When capturing consent for the Messaging consent channel, end users can receive confirmation from HCPs in person or via confirmation emails. To use confirmation emails, ensure the Approved Email integration user has CRE object permission to the Messaging object type on the Multichannel Consent object. See Capturing Consent Using Confirmation Emails for All Channels for more information.

Business admin users must set up consent for Messaging by creating a Consent Type (consent_type__v) record with the Messaging (messaging__v) object type. See Creating Consent Types for more information.

Additionally, business admin users can data load Multichannel Consent (multichannel_consent__v) records for opt-in consent in bulk using the Vault Loader or an integration with an external system. The following fields must be populated on each record:

• Object Type - Must be messaging__v
• Account
• Capture Datetime
• Opt Type

Business admin users can set up legacy consent to reuse consent captured for a custom consent channel as consent for Messaging. When reusing consent for a custom consent channel, the most recently captured consent record is used. For example, an end user captures opt-in consent for a custom SMS channel. The custom SMS channel is then updated to the Messaging consent channel, and the same opt-in consent is used for Messaging.

To set up legacy consent:

1. Navigate to Business Admin > Objects > Consent Types.
2. Select the Consent Type record for the appropriate custom consent channel.
3. Update the object type to Messaging.
4. Populate the Legacy Consent Channel field with the API name of the object type for the custom channel, for example, sms__c.

If the custom consent channel was previously configured for a Channel Value, Product, Detail Group, or Content Type, those values on Multichannel Consent records are ignored when evaluating consent for the Messaging channel.

When using WhatsApp Business Messaging, business admin users can define keywords allowing HCPs to grant or withdraw consent for WhatsApp Business Messaging, for example, START or STOP. This grants HCPs more control over their consent preferences for messaging. To define subscribe and unsubscribe keywords for messaging:

1. Navigate to Business Admin > Objects > Consent Types.
2. Select the appropriate Consent Type (consent_type__v) record with the Messaging (messaging__v) object type.
3. Select Edit.
4. Populate the Subscribe Keyword (subscribe_keyword__v) and Unsubscribe Keyword (unsubscribe_keyword__v) fields. Examples include the following:
   • Subscribe – START
   • Unsubscribe – STOP

When an HCP sends a WhatsApp message containing one of these keywords, the following occurs:

• A Multichannel Consent (multichannel_consent__v) record is created for the account and previously captured consent records are expired
• A consent confirmation message is sent, if configured. See Defining Automated Consent Confirmation WhatsApp Messages for more information.

Business admins can define consent confirmation messages sent to HCPs automatically via WhatsApp after end users capture opt-in or opt-out consent. To define a consent confirmation message:

1. Create the message template in Meta. For example, a consent confirmation message for opt-in consent can include the text: You’re now opted-in to receive messages, reply with STOP to opt out.
2. Data load the Meta message template into Vault CRM and associate it with the appropriate Multichannel Routing records. See Managing Message Templates in Vault CRM for more information.

To send chat messages to HCPs, end users can capture consent for the Messaging consent channel. See Granting Consent for more information.

If legacy consent is set up, for example, SMS, the legacy consent is automatically used as consent for Messaging.