The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Agentforce Service offerings explained for configuration and rollout planning (opens in a new tab)

Readers will learn how to configure and deploy Agentforce Service agents, understand the prerequisites for Omni-Channel routing and Knowledge grounding, and see which legacy channels are being retired.

Why read this

The piece also outlines practical rollout strategies to avoid common implementation pitfalls.

The piece is a guide to Agentforce Service, Salesforce’s AI customer service platform, which was renamed from Service Cloud in October 2025. It covers seven offerings: AI agents, case management, omnichannel contact center, an AI knowledge base, field service, analytics and integrations. For each, it explains what the offering does, what it depends on and where teams tend to run into trouble. The AI agents come in two forms. Help Agent is prepackaged and set up from one screen, and it is grounded on Salesforce Knowledge, uploaded files or a website sync. It needs Enterprise or Unlimited Edition with Agentforce enabled. Service Agent is configurable, with topics, instructions and actions defined by the team, and suits work that touches the company’s own systems, such as order lookups or appointment changes. Agentic features such as Agentic Milestones, MCP support and multi-agent setups are also described. Omni-Channel routing depends on Enhanced Omni-Channel, which the article calls the foundation for Agentforce Service and a requirement for Agentforce Voice and Contact Center.

On the contact center and channels, the article notes that Salesforce is retiring Standard Facebook Messenger and Standard SMS channels in mid-2026, so teams still on them should move to Enhanced channels. It also points to the knowledge base as a dependency: AI answers are only as good as the Knowledge articles behind them, so the author recommends knowledge-centered service habits. Case management, field service work orders, analytics (with metrics such as autonomous resolution rate, escalation rate and CSAT on AI-handled cases) and MuleSoft-based integrations with ERP and telephony systems are each summarized with their key requirements. Pricing mixes per-user licenses, Flex Credits and a per-resolution charge for Help Agent, and the article advises confirming current India pricing with Salesforce.

The rollout advice is the practical core. The author suggests auditing data and the knowledge base first, setting up Enhanced Omni-Channel, launching one AI agent on a single high-volume, low-risk queue, measuring results for a month and then expanding, with budget kept for ongoing tuning after go-live. The article is written by Cloud Odyssey, a Salesforce partner, and it promotes its own services, so its vendor-supplied performance figures (such as 72% of routine inquiries offloaded and 70% resolution on Salesforce’s own help portal) are presented as numbers to test rather than guaranteed results.

Read the original at Cloud Odyssey (opens in a new tab)

Worth reading?

Salesforce announces Agentic Identity and flex credit adjustments for Model Context Protocol servers (opens in a new tab)

Readers will understand how Model Context Protocol servers connect Salesforce to external systems through natural language prompts.

Why read this

They will also learn about the upcoming November changes to the flex credits model and the new Agentic Identity framework for agent permissions.

The article introduces Model Context Protocol servers as a standardized interface for linking artificial intelligence hosts to enterprise systems like Salesforce. It outlines a three-part architecture comprising a host application, a client, and a server that securely exposes tools and resources. This design aims to replace custom integrations by allowing large language models to automatically discover and execute connected capabilities.

Practical examples demonstrate how sales and support teams can retrieve pipeline data or automate cross-platform workflows using simple natural language commands. These scenarios eliminate the need to manually switch between separate applications and navigate multiple forms to complete routine tasks.

Financial and governance impacts are also addressed, noting that agent-driven calls will begin consuming standard flex credits in November. The piece explains the introduction of Agentic Identity to distinguish between standard user operations and scoped agent permissions. Testing environments including Sandboxes and Scratch Orgs remain exempt from these billing changes, allowing teams to evaluate the technology safely before production deployment.

Read the original at Nebula Consulting (opens in a new tab)

Worth reading?

Recommended

Building a custom Apex tool for Lead conversion with Salesforce Model Context Protocol (opens in a new tab)

You will learn how to configure a Salesforce Model Context Protocol server and write an Invocable Apex class to handle Lead conversion through AI agents.

Why read this

The piece clarifies why generic record mutation tools cannot replace the native conversion process.

Introduces Salesforce Headless 360 and the Model Context Protocol as methods for AI agents to interact with orgs. Explains that basic access is free but may consume Flex Credits.

Walks through creating a custom MCP server in Setup and notes that default tools do not support Lead conversion. Details the architectural reason why generic SObject mutation tools fail for this task, citing atomic execution, field mapping, deduplication, and related record reparenting.

Outlines the requirement to build an Invocable Apex class using Database.convertLead(). Describes the necessary annotations and access modifiers needed to expose the method to the MCP framework.

Read the original at Salesforce Break (opens in a new tab)

Worth reading?