Add Strategic Context and Control to Your Account Model

Learning Objectives

After completing this unit, you’ll be able to:

• Identify how Agentforce Life Sciences adds strategic signals and compliance controls to account data.
  
• Describe how these features help teams prioritize engagement, maintain data accuracy, and protect privacy.
  
• Explain how to connect these controls to downstream planning and orchestration activities.
  

From Structure to Strategy

Once you’ve established relationships between accounts, territories, and products, the next step is putting that structure to work. Commercial teams need ways to interpret records, organize large books of business, and keep provider data reliable as it changes.

This unit focuses on four capabilities that build on the account model:

• Ratings, which express strategic signals such as importance or potential
  
• Lists and Filters, which create focused sets of accounts
  
• Segmentation, which gives admins reusable, rule-driven groupings
  
• Data Change Requests, which safeguard data quality
  

Together, these capabilities turn structural data into an operational layer that supports prioritization, planning, and governance across commercial teams.

Add Strategic Meaning with Ratings

A well-modeled account structure establishes who a provider is and how they connect to products, territories, and teams. But planning also depends on how to interpret that structure. Ratings add that strategic layer by turning relationship data into consistent signals teams can use to prioritize, segment, and coordinate outreach.

A rating is applied where the context lives. This could be the account as a whole, a territory assignment, a product relationship, a practice location, or a team alignment. By storing ratings on these specific relationship objects, Agentforce Life Sciences preserves meaning without forcing one-size-fits-all labels.

Let's explore how ratings apply to some of the objects you've already learned about, including those that cover account and territory information.

On an account record, the Ratings tab consolidates the signals teams rely on for planning—provider-level tiers and segments, plus context-specific ratings that can vary by product or other relationships. This gives users a quick, shared “read” of the account without collapsing everything into a single label.

Admins control which rating fields appear and can tailor layouts by profile so each role sees the signals that matter for their work. With ratings anchored to the right objects, Agentforce Life Sciences turns account relationships into shared, actionable insight, with planning and execution staying consistent across teams.

Organize and Act with Lists and Filters

Account structures become most useful when users can shape them into focused working sets. Territories are large, priorities shift quickly, and teams need flexible ways to zero in on the right accounts for the task at hand.

Lists and filters support two complementary approaches:

• Dynamic filters, which automatically assemble accounts based on defined criteria
  
• Static lists, including routes, which users curate manually
  

Together, they help reps and other commercial users focus on the accounts that matter most to their work.

Let’s go over the objects for lists and filters.

Users move between dynamic and static lists to plan outreach, build routines, or work from targeted account sets. Dynamic filters adjust automatically as data changes, while static lists support repeatable workflows.

Bulk actions let users update supported fields or launch visits and emails across multiple accounts, turning lists into practical tools for daily execution.

Next, let’s learn about segmentation.

Segment at Scale with Admin-Defined Logic

Lists and filters help users assemble accounts for day-to-day work, but many groupings need to be standardized across teams, reused by multiple features, or enforced through business rules. Segmentation provides this administrative layer.

A segmentation groups accounts (or account-related records) based on defined criteria and makes that grouping available for other functions such as eligibility checks or sample limit logic. Unlike personal lists, segmentations are centrally defined and governed, ensuring consistency across territories, brands, and workflows.

Segmentation is built on the Actionable List framework, which provides a flexible way to define a dataset, capture the criteria that shape it, and link it to downstream use cases.

Here’s an overview of segmentation objects.

Once defined, a segmentation becomes a reusable building block for rules and planning. For example, teams can use segmentations to set up sampling limits.

Centralized criteria ensure everyone operates from a consistent interpretation of which accounts meet specific strategic or regulatory conditions.

The last layer of the data model deals with data quality and change requests.

Maintain Data Quality with Data Change Requests

Provider data changes constantly, and giving everyone the ability to edit it creates risk. Data Change Requests (DCRs) provide a controlled way to keep data accurate by allowing users to submit corrections while admins decide which changes require review or validation.

DCR uses configuration objects to define which fields are governed and which profiles and record types are allowed to update them. A transaction object stores each request and its review status.

Here are the key objects of the Data Change request model.

DCR preserves data quality without limiting visibility. Users surface corrections as they see them, while administrators maintain oversight. Downstream processes—segmentation, sampling, territory operations—benefit from clean, trusted records.

Build a Trusted Commercial Foundation

Across this badge, you explored how Agentforce Life Sciences establishes a structured, unified account model that supports the entire commercial lifecycle.

You learned how:

• Accounts and Healthcare Providers form the anchor for commercial data.
  
• Contact Points, Specialties, and Licenses give dimension to each provider.
  
• Affiliations and Alignments tie providers to organizations, territories, and users.
  
• Products and Territories extend the model into brand and regional strategy.
  
• Ratings, Lists and Filters, Segmentation, and DCR add strategic insight, organization, and governance on top of that foundation.
  

Together, these elements help teams work from a shared, accurate view of their customers and ensure downstream execution is grounded in clean, consistent data.

For organizations like Cumulus Pharma, this means engagement with providers like Dr. Aaron Morita is guided by clear relationships, aligned teams, and defined product and territory constraints, all resolved directly from structured data.

For deeper implementation detail, explore the Resources section for setup guides, detailed object reference materials, and administrator documentation.

Resources

• Salesforce Help: Lists and Filters
• Salesforce Help: Segmentation
• Salesforce Help: Data Change Requests
• Salesforce Help: Account Management