Cert++

Practice
Certle
Review
Tracks
Checklist
Guides
Upgrade

Home
Agentforce Life Sciences Consultant

Agentforce Life Sciences Consultant

Checklist progress

0/189Learned

Agentforce Life Sciences Consultant

Study Checklist

Platform Administrator
Platform App Builder
Platform Foundations
Platform Developer
Platform Administrator II
Agentforce Sales Consultant
Agentforce Service Consultant
Platform Data Architect
Platform Development Lifecycle and Deployment Architect
Platform Identity and Access Management Architect
Platform Integration Architect
Platform Sharing and Visibility Architect
Heroku Architect
B2C Solution Architect
Experience Cloud Consultant
Agentforce Field Service and Operations Consultant
Agentforce Nonprofit Consultant
Data 360 Consultant
Omnistudio Consultant
CRM Analytics and Einstein Discovery Consultant
Platform User Experience Designer
Platform Strategy Designer
B2C Commerce Developer
JavaScript Developer
Omnistudio Developer
Platform Developer II
Marketing Cloud Engagement Administrator
Marketing Cloud Engagement Specialist
Marketing Cloud Engagement Consultant
Agentforce Sales Foundations
Business Analyst
Marketing Cloud Engagement Developer
Marketing Cloud Engagement Foundations
Agentforce Specialist
Agentforce Life Sciences Consultant
B2B Commerce Administrator AP
B2B Commerce Developer AP
Agentforce Consumer Goods AP
Agentforce Financial Services AP
Agentforce Health AP
Agentforce Manufacturing AP
MuleSoft Integration Foundations
MuleSoft Developer
MuleSoft Developer II
MuleSoft Platform Integration Architect
MuleSoft Platform Architect
Tableau Desktop Foundations
Tableau Data Analyst
Tableau Consultant
Tableau Server Administrator
Tableau Architect

Checklist progress

0/189Learned

How Account records model Healthcare Professionals (HCPs) as person accounts versus Healthcare Organizations (HCOs) as business accounts in Agentforce Life Sciences
When Person Accounts should be enabled to represent individual HCPs in Agentforce Life Sciences
How enabling Person Accounts affects relationship modeling between HCPs and HCO business accounts
How to use Affiliations to capture the relationship between an HCP and the HCOs where they practice, including primary affiliation designation
The difference between Account-to-Account affiliations (HCO-to-HCO) and Account-to-Contact/Person affiliations (HCP-to-HCO) and when each is used
How Account Hierarchy is used to represent parent/child HCO structures such as a health system with member hospitals and clinics
Which configuration maintains accurate HCP credential, specialty, and license data on the account for compliant targeting
How to manage duplicate HCP/HCO records using matching and duplicate rules to keep master data clean
The role of address and place-of-business data on accounts for visit planning and sampling shipment compliance
How a single HCP can hold multiple addresses or places of business in Agentforce Life Sciences
How the active or shippable address is designated for sampling shipments and visit logistics
How affiliation role and influence attributes (e.g., decision maker, prescriber, KOL status) are captured to support targeting and engagement strategy
How to maintain data stewardship workflows for change requests to HCP/HCO master data, including approval before updates take effect
How third-party reference/master data (e.g., HCP/HCO reference data feeds) is ingested and reconciled with internal account records to keep master data authoritative
Which steps are required to set up and deploy the Agentforce Life Sciences mobile application for field reps
How offline access is configured so reps can execute visits and capture data without connectivity
Which permission sets and permission set licenses are prerequisites for a rep to use the Agentforce Life Sciences mobile application
How mobile configuration controls which objects, layouts, and actions are available offline to reps
Common causes when a rep cannot see assigned accounts or visits in the mobile app and how to resolve them
How initial and incremental data download scope (briefcase/priming) is sized so reps get the right data without exceeding mobile storage or sync limits
Supported device, OS, and app version requirements for the Agentforce Life Sciences mobile application
How mobile app upgrades and version compatibility are managed for the field workforce
How to diagnose and resolve sync conflicts when the same record was edited offline by a rep and online in the org
Which connected app settings are prerequisites for a rep to use the Agentforce Life Sciences mobile application
How to troubleshoot data not syncing from the mobile app back to the org after a rep regains connectivity
How to troubleshoot a rep who cannot log in or whose session/authentication fails on the mobile application
How org-wide defaults and sharing rules should be configured to control visibility of HCP/HCO accounts across territories
How field-level security is used to restrict sensitive HCP data such as compliance or sampling fields
How role hierarchy governs rep and manager access to engagement data in Agentforce Life Sciences
How territory-based sharing governs rep and manager access to engagement data in Agentforce Life Sciences
How licensing prerequisites are validated as part of Agentforce Life Sciences system configuration
How Agentforce Life Sciences managed package and feature dependencies are validated during system configuration
How audit trail and field history tracking are configured to support compliance and security oversight in a regulated org
Which permission sets and permission set licenses grant access to Agentforce Life Sciences objects and features
How the consent management data model captures an HCP's permission to be contacted by channel (email, phone, in-person)
Which configuration enforces that a rep cannot send Field Email to an HCP who has not consented to email communication
How subscription management lets HCPs opt in/out of specific content topics or communication types for GDPR/HIPAA-aligned compliance
The relationship between Individual, Contact Point, and consent records used to track data privacy preferences
How to handle a data privacy request such as restricting processing or capturing withdrawal of consent for an HCP
How proof-of-consent capture (timestamp, source, channel) is configured to evidence compliant HCP consent collection
How regional consent rules are configured to keep HCP contactability compliant by geography
How Enterprise Territory Management models territories, territory types, and territory hierarchy for field sales alignment
How assignment rules automatically align HCP/HCO accounts to territories based on criteria such as geography or specialty
How product alignment (territory-to-product) restricts which products a rep can detail or sample within a territory
The difference between manual and rule-based account assignment to territories and when to run assignment rules
How a territory model is activated in Enterprise Territory Management
The impact of changing assignment rules on existing account-to-territory alignments
How users are assigned to territories and how that drives access to aligned accounts and visit planning
How territory model states (Planning, Active, Archived) are used to test a new alignment in parallel before activating it in production
How an alignment realignment (territory boundary or rep change) is executed and its downstream impact on in-flight visits, plans, and sample allocations
How territory model default access settings for accounts, opportunities, and cases are configured for Life Sciences field teams
Which setup steps and feature toggles enable core Agentforce Life Sciences for Customer Engagement capabilities
How to configure visit, call, and engagement objects and page layouts to match a customer's field process
Which configuration objects must be set up before reps can plan and execute compliant HCP visits
How to enable and configure data integration with Data 360 for unified HCP/HCO insights
How products and product catalogs are set up in Agentforce Life Sciences
How product-to-call configuration is set up so reps can detail and sample the right products
How the Lightning app and navigation are configured to deliver the Life Sciences rep and manager experience
How home and record pages are configured to deliver the Life Sciences rep and manager experience
How business rules, validation rules, and call/visit compliance settings are configured to enforce process integrity during engagement capture
Which administrative settings/custom settings or custom metadata control org-wide Agentforce Life Sciences behavior (e.g., signature requirements, sampling toggles)
How Intelligent Content is set up to manage approved, compliant content that reps present to HCPs
How Presentations (CLM-style content delivery) are configured for reps to show approved visual aids during a visit
How Field Email templates are created and approved so reps send compliant, pre-approved emails to HCPs
How content approval workflows ensure only MLR-approved materials are available to field reps
How presentation tracking captures which slides/content an HCP viewed during an engagement
How content expiration and versioning are managed so out-of-date materials are removed from rep access
How content withdrawal is managed so unapproved materials are removed from rep access
How content is targeted/restricted by product, territory, audience, or consent so reps only see content they are entitled to share
How Field Email merge fields and dynamic content are configured in templates
How content/presentation files are distributed and made available offline so reps can present without connectivity
How required compliance elements such as unsubscribe links and fair balance are configured in Field Email templates
How to build standard reports on visits, calls, and engagement activity for sales managers
What TabNext industry metrics provide for Life Sciences engagement KPIs
How report and dashboard folder sharing controls which territory data each manager sees
How report and dashboard running-user settings control which territory data each manager sees
How dynamic dashboards control which territory data each manager sees
How dashboards are assembled to give field managers a view of territory performance and rep activity
How TabNext industry metrics surface Life Sciences engagement KPIs to users
How TabNext industry metrics are enabled and configured
Which report type is required to report across HCP accounts, affiliations, and visits together
How TabNext industry metrics are bound to underlying engagement data sources

How an Activity Plan defines a set of recommended activities/tasks for reps within a territory over a time period
Which configuration ties an Activity Plan to a specific territory so the right reps receive the right targets
How review processes and approvals are set up so managers can validate and adjust Activity Plans
How progress tracking measures completion of planned activities against actual rep execution
How Activity Plan Templates standardize recurring engagement cadences across territories
How call and visit frequency targets are encoded in an Activity Plan to drive reach and frequency
How HCP segmentation tiers (e.g., A/B/C) are encoded in an Activity Plan to drive the right engagement cadence
How Activity Plan target attainment and gaps surface in reports/dashboards so managers can coach reps mid-cycle
How calendar setup enables reps to schedule and visualize HCP/HCO visits for efficient planning
What Time Off Territory (TOT) represents and how it is recorded so visit planning accounts for rep unavailability
How TOT conflicting rules prevent a rep from scheduling visits during recorded time off territory
Which calendar configuration optimizes visit routing and reduces travel while respecting territory alignment
How calendar and TOT settings interact when a rep tries to book a visit that overlaps approved time off
How a TOT request is submitted, approved, and reflected on the calendar so managers control rep availability
How HCO and HCP availability and business hours are configured so the calendar reflects realistic plannable time
How visit duration settings are configured so the calendar reflects realistic plannable time
How recurring visits are set up so reps can plan a repeating engagement cadence across the calendar
How bulk scheduling is set up so reps can plan multiple visits efficiently across the calendar
What a Key Account Management (KAM) Plan is and how it captures strategy, objectives, and stakeholders for a key HCO
How KAM Plan objectives and action items are configured and assigned to account team members
How progress against KAM Plan goals is tracked and reported for a strategic key account
How KAM Plans coordinate cross-functional team activity (sales, medical) around a single key account
How stakeholder mapping and influence/relationship analysis are captured within a KAM Plan to prioritize key decision makers
How KAM Plan templates standardize creation of plans across the key-account portfolio
How KAM Plan lifecycle stages standardize periodic review of plans across the key-account portfolio
Which out-of-the-box Agentforce features are available to support Life Sciences rep guidance and how they are enabled
How Next Best Action strategies and recommendations are configured to give reps weekly guidance on which HCPs to engage
How recommendations and action strategies surface Next Best Action on a record page or in the rep's planning view
How an Agentforce agent/topic and actions are configured to assist reps with planning and engagement tasks in Life Sciences
How Next Best Action strategy logic (branch, load, filter, recommendation) is built to rank recommendations based on engagement data
How recommendation acceptance/rejection feedback is captured and reported to refine Next Best Action guidance over time
The setup prerequisites (recommendations, strategies, deployment) for delivering Next Best Action to field users

How remote engagement is configured so reps can conduct virtual HCP meetings within Agentforce Life Sciences
Which settings enable compliant content sharing during a remote HCP engagement
Which settings enable consent capture during a remote HCP engagement
How remote meeting attendance and outcomes are recorded against the visit/engagement record
How remote engagement configuration differs from in-person visit configuration in terms of required setup
How web, video conferencing, and screen-sharing integrations are configured for remote HCP details
Which licensing and connected-app prerequisites are required for remote engagement integrations
How remote signature capture for sample acknowledgment and consent is configured for engagements where the HCP is not physically present
The stages of the end-to-end visit lifecycle: pre-call planning, in-person/remote execution, and post-visit follow-up
How pre-call planning configuration prepares reps with account context, objectives, and approved content before a visit
How a rep records call details, attendees, products detailed, and outcomes during visit execution
How post-visit tasks such as follow-ups, samples disbursed, and notes are captured to complete the visit record
How visit status transitions are controlled so a visit cannot be marked complete without required compliance steps
How signature capture for sample acknowledgment is integrated into the visit lifecycle
How group/shared visits and co-visits with managers or multiple attendees are recorded across the visit lifecycle
How edit restrictions after visit submission prevent post-hoc tampering with completed visit records
How offline-created visits are captured, queued, and synced so the visit lifecycle completes correctly when the rep regains connectivity
How visit locking and locking windows prevent premature edits to submitted visit records
How Medical Insights are captured by medical liaisons during engagements with HCPs and HCOs
Which configuration enables Medical Insights to be categorized by therapeutic area or topic
Which configuration enables Medical Insights to be shared with the appropriate teams
How sharing rules and visibility control who can view sensitive medical insights captured from HCP interactions
How captured medical insights feed reporting to surface field intelligence trends to medical affairs
How the separation between commercial and medical (MSL) data is enforced so insights remain firewalled from sales for compliance
How insight escalation/routing notifies the right stakeholders (e.g., safety, medical information) when an insight requires action
How a Medical Inquiry is created and routed when an HCP requests off-label or scientific information
How a Medical Inquiry is tracked through fulfillment when an HCP requests off-label or scientific information
Which configuration ensures Medical Inquiries are handled compliantly with proper audit trail and response tracking
How Medical Inquiry status and follow-up are managed from intake through closure
How queues and assignment rules route Medical Inquiries to the correct medical information team
How adverse event and product complaint signals captured alongside a Medical Inquiry are flagged and escalated to pharmacovigilance per compliance requirements
How approved response content and standard response letters are linked to a Medical Inquiry so fulfillment uses only MLR-approved scientific responses

Given a scenario, configure and manage Sample Limits and Allocations to ensure reps stay within defined quantities.

0/9

How Sample Limits define the maximum quantity of a product a rep can disburse to an HCP over a period
How sample Allocations grant reps a stock of samples in Agentforce Life Sciences
How sample Allocations relate to territory product alignment
Which configuration prevents a rep from disbursing samples beyond an HCP's defined limit during a visit
How sample limits are defined at product, HCP, and time-period levels to enforce compliant quantities
How territory product quantity allocations cap the total samples available to a territory
How HCP eligibility to receive samples (license/state validation, eligibility rules) gates whether any allocation can be disbursed
How sample limit periods reset using rolling versus fixed calendar windows
How sample limit consumption rolls up across visits to enforce the cap accurately

Apply GxP standards to sampling workflows, ensuring all distribution aligns with regional regulatory requirements.

0/7

What GxP standards require of sampling workflows and how Agentforce Life Sciences supports traceability and accountability

Learn this concept

Unseen

How digital signature and acknowledgment capture supports FDA/PDMA-style sample distribution requirements

Learn this concept

Unseen

How regional regulatory differences are handled in sampling configuration to ensure compliant distribution by geography

Learn this concept

Unseen

How custody management and audit trails ensure GxP-compliant chain of custody for sample stock

Learn this concept

Unseen

How lot/batch and expiration-date tracking is enforced across sampling so distribution and recall handling meet GxP traceability requirements

Learn this concept

Unseen

How discrepancy thresholds support regulatory reporting obligations for sample accountability

Learn this concept

Unseen

How sample reconciliation reporting supports regulatory reporting obligations for sample accountability

Learn this concept

Unseen

Manage the end-to-end Sample Disbursement process.

0/9

The end-to-end sample disbursement process from rep request through delivery, disbursement, and acknowledgment
How a rep records a sample disbursement to an HCP during a visit including product, lot, and quantity
How signature/acknowledgment requirements gate completion of a sample disbursement
How sample disbursement transactions decrement rep inventory
How sample disbursement transactions roll up against sample limits
How a rep replenishes stock by requesting and receiving (acknowledging) sample shipments/transfers before disbursing to HCPs
How sample returns and transfers between reps are processed while preserving accountability and limit integrity
How disbursement corrections and reversals are processed while preserving accountability and limit integrity
How a disbursement is validated against eligibility, consent, limits, and lot/expiry at submission so non-compliant disbursements are blocked

Given a scenario, configure Inventory Counting, Adjustment, and Audits.

0/8

How Inventory Counts are configured so reps periodically reconcile physical sample stock against system records
How Inventory Adjustments correct discrepancies (loss, damage, expiry) found during a count
How inventory audits are set up to detect and investigate variances in rep sample stock
Which configuration determines the cadence of inventory counts and adjustments for compliance
Which configuration determines the approval requirements for inventory counts and adjustments for compliance
How count submissions are locked and how partial/full count types and recount workflows are configured to ensure complete physical reconciliation
How inventory adjustment approval routing is configured to authorize each inventory correction for audit
How inventory adjustment reason codes are configured to document each inventory correction for audit

Given a scenario, configure Sample Reports and Dashboards for monitoring the full lifecycle of sample stock.

0/10

How sample reports are built to monitor allocation, disbursement, and remaining stock across the lifecycle
Which dashboard components give compliance managers visibility into sampling activity and limit adherence
How sample reporting surfaces inventory discrepancies for follow-up
How sample reporting surfaces expired stock for follow-up
How sample reporting surfaces audit exceptions for follow-up
Which report type covers the full sample lifecycle from allocation through disbursement and reconciliation
How signature/acknowledgment completeness and missing-signature exceptions are reported to evidence compliant disbursement
How lot/expiry-aging reports flag soon-to-expire and expired stock so managers can act before it must be destroyed
How sample report and dashboard sharing settings ensure managers see only territory sample data while compliance sees enterprise-wide data
How sample report and dashboard running-user settings ensure managers see only territory sample data while compliance sees enterprise-wide data

Prepare for the Exam

Play Today's Certle

Study Community

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

How digital signature and acknowledgment capture supports FDA/PDMA-style sample distribution requirements

Explainer

Learn More

Practice Question

Keep going

Next conceptHow regional regulatory differences are handled in sampling configuration to ensure compliant distribution by geography

Checklist progress

0/189 (0%)

0 of 189 concepts learned

Learned0Learning0Seen0Unseen189

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle

Study Community

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

Explainer

Digital signature and acknowledgment capture creates an immutable, audit-ready record of sample handoffs to ensure strict regulatory compliance. By binding electronic signatures, mandatory acknowledgments, and visit snapshots directly to the transaction, the system verifies that representatives follow eligibility rules and document healthcare professional receipt before inventory updates.

Core information

Field representatives capture electronic signatures directly on mobile devices during the visit, instantly appending the signature to the visit record to document product handoff.

More details and nuances

The signature capture feature is designed specifically for documenting healthcare professional receipt of prescription samples, placing full legal compliance responsibility on the customer to configure appropriate disclaimers and jurisdiction filters.