ARM Extension: Context Service Architecture

An AI agent cannot orchestrate revenue if it cannot read the environment. Context Service acts as a generic bridge between your business processes and applications. For Agentforce Revenue Management (ARM), Context Service is the neural pathway that feeds real-time customer, product, and transaction data into the pricing and configuration engines.

1. The Role of Context Service in ARM

Context Service acts as a layer between the application and the rules or procedures, providing the requested data during both the configuration (design-time) and execution (run-time) stages. Context definitions are the key component of the Context Service. By utilizing this layer, ARM agents do not need to perform expensive, repeated database queries; instead, they consume a unified JSON payload of contextual data.

Context definitions eliminate silos by enabling applications like Transaction Management, Product Discovery, and Billing to communicate consistently.

Core Components:

Context Definition: Provides a common canonical layer to connect various pricing elements and data sources. At their core, these definitions are structured metadata blueprints that contain all the necessary information to run the revenue process, defining the relationships between data nodes, their attributes, and the mappings to your Salesforce objects.
Context Mapping: Context mapping in Salesforce involves defining the data sources for specific nodes and attributes within a context definition. For example, the Place Sales Transaction API relies on context mapping for custom objects, where the parentReference maps to the custom object's immediate parent field (e.g., quote_line_item_c).

2. Sales Transaction Context (API Integration)

When an AI agent initiates a quoting or ordering sequence, it utilizes the Place Sales Transaction (POST) API to create a sales transaction with integrated pricing and configuration. The API manages the transaction state via the SalesTransactionContext.

// Output representation of context details associated with a sales transaction { "contextDetails": { "contextId": "e055bb18-d4e8-41c3-881e-0132b9561708", "isBuiltInTransaction": true } }

3. Predefined Context Definitions for Revenue Management

Salesforce provides standard predefined context definitions that work out-of-the-box, though you can also extend or clone them to meet your unique use cases. These ensure data flows seamlessly across your entire revenue lifecycle.

Property Name	Type	Technical Function
`contextId`	String	ID of the context that's created for a session of the sales transaction. If the property isn't specified, the Place Sales Transaction API generates it autonomously.
`isBuiltInTransaction`	Boolean	Indicates whether a new context ID is created for the sales transaction (`true`) or not (`false`).

Primary Context Engines:

Salesforce Pricing Context: Defines the inputs used for pricing. When an agent calculates a quote, the Context Definition passes mapped variables (like Account SLA, Partner Tier, and Order Quantity) into the pricing waterfall to calculate net prices dynamically.
Product Discovery Context: Maps user variables and intent to the product catalog, allowing the agent to filter out incompatible products before displaying them to the user or generating a bundle.
Transaction Management Context: Unifies the header and line-item data for quotes and orders to ensure delta processing and grouping (e.g., grouping by location or work type) execute accurately during API calls.

4. Agentic Execution of Context