Cert++
Close

Capturing HCP consent during an in-person visit

Key Takeaway

To make the HCP's signature mandatory proof for consent captured in the mobile app, an admin sets "Signature Requirement" to Required in "Mobile App Consent Proof Settings", under Admin Console > "Consent Administration".

During an in-person visit, a field rep often records whether a healthcare professional (HCP) agrees to receive future communications. In Life Sciences Cloud for Customer Engagement, the rep sets each channel to Opt In or Opt Out on the Consent page and adds proof, such as the HCP's signature. Admins decide in Consent Administration which proof reps must add. The saved consent controls which follow-up communications are permitted later, so it shapes outreach to that HCP after the visit.

What a rep records

Consent is recorded for each communication subscription and its channels, such as email or phone. On the Consent page, the rep uses radio buttons to set each channel's status to Opt In or Opt Out. Saving writes the update back to the HCP's subscriptions and channel preferences, so the captured consent controls which follow-up communications are permitted later.

Whether a rep can leave a channel as Not Asked depends on the "Allow users to select 'Not Asked' as the consent status" setting.

If the setting is off...

Reps must set every applicable channel to Opt In or Opt Out before they save.

If the setting is on...

Reps can leave individual channels as Not Asked. Salesforce doesn't save a consent record when every channel is Not Asked.

Agentforce Life Sciences Consultant Study Guide

Checklist progress

0/279Learned

Manage the end-to-end visit lifecycle

0/24

Visit and Provider Visit data model

Learn this concept

Surveys launched during HCP visits

Learn this concept

Capturing next visit objectives

Learn this concept

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Agentforce Life Sciences Consultant studiers.