MCP, A2A, and Functional Calling

 1. Model-Context Protocol (MCP)

MCP manages dynamic context windows across enterprise LLM infrastructure. It retrieves prior memory, history, and metadata to personalize every response without hardcoding logic into prompts.

2. Agent-to-Agent Protocol (A2A)

In A2A, agents talk to each other directly using shared protocols. Think of it as collaborative problem-solving between specialized local agents, especially useful in multi-agent ecosystems.

3. Functional Calling

Here, an LLM acts like a planner. It decomposes a task (e.g., comparing market caps), generates a Directed Acyclic Graph (DAG) of subtasks, and then sends each task to appropriate tools (math, search, APIs) for execution.

Conclusion

-  MCP is about managing context,

-  A2A is about agent collaboration,

-  Functional Calling is about task execution.

Agentforce metadata types for deployment

 The following are key metadata types to consider when deploying Prompt Templates, Topics, Agent Actions, and Agents in Salesforce.

<!--Agents-->

<types>

    <members>*</members>

    <name>Bot</name>

 </types>

 <types>

   <members>*</members>

    <name>GenAiPlanner</name>

  </types>

<!--Agent Actions-->

 <types>

       <members>*</members>

      <name>GenAiFunction</name>

 </types>

  <!--Agent Topic-->

  <types>

       <members>*</members>

       <name>GenAiPlugin</name>

  </types>

  <!--PromptTemplate-->

  <types>

    <members>*</members>

    <name>GenAiPromptTemplate</name>

  </types>

  <!--Messaging Channel-->

<types>

   <members>*</members>

   <name>MessagingChannel</name>

</types>

Pre-chat Fields in AI Agent

 How to collect essential customer information before they start a conversation with the agent?

Using Pre-chat Fields in Embedded Service Deployments(ESD).

—> Visible pre-chat fields are displayed to the user and require direct input.

—> Hidden pre-chat fields are not displayed to your end-user.

Pre-chat forms for Agentforce :

1.Setting context for the agent.

2.Establishing user identity.

3.Advanced routing.

Dynamic Revenue Orchestrator (DRO) in Revenue Cloud

 

DRO bridges front-office sales with back-office operations, ensuring that every sold product or service is fulfilled accurately and smoothly.

Decomposition : Break down complex orders into manageable tasks.

Fulfillment : Streamlines and automates fulfillment workflows.

Transaction Management in Revenue Cloud Advanced

Transaction Management :

Transaction management has CPQ and Contract.

Create Quote with the right products and Prices. Close deals faster.

Customize the Transaction Line Editor to ensure sales teams have the right information at their fingertips for faster, smarter selling.

Extend SalesTransaction Context to map Custom Fields : 

1.Extend the OOTB SalesTransaction Context directly to create your own custom definition,Add necessary custom mappings and then Activate your definition.

2.Sync your Context Definition on Upgrades.

Note : Avoid cloning and then extending SalesTransaction_Context.

Price Waterfall :

Tip: Use Price waterfall to visualize price breakdowns.

Using Waterfall, view price breakups - taxes, discounts and adjustments at each step, with reasons for every addition or deduction.

Product Catalog management Best Practices in Revenue Cloud Advanced

 Structure Products for Scalability and Reusability.

Note : Product catalog impacts every step of the revenue lifecycle.

1.Organize products into Catalogs and Categories for easy product discovery.

Use qualification rules to help sales person to quickly discover the right product.

2.Use Bundles to structure products hierarchically to simplify configuration, enable flexible customization and streamline the sale experience.

3.Leverage Attributes and Attribute categories, Use configurator to help sales person configure the right product.

4.Performance and scalability considerations, Number of Attributes,Bundle Nesting and number of products in a Bundle.

Features of Configurator in Revenue Cloud Advanced

Configurator : 

Composable Design Templates - powered by Flow Builder.

Configurator Template Assignment - Assign Product or a product Classification to a template.

Preview the config template.

Configuration Rules - Offer an intuitive configuration experience with validation, inclusion and exclusion rules to apply business logic at the time of sale.