The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Agent Optimizer guides Agentforce agents through build, test, fix and improve stages (opens in a new tab)

You will see how Agent Optimizer moves an Agentforce agent from first build through production monitoring, root-cause fixes and A/B testing.

Why read this

You will also learn which of these features are still in beta or coming soon.

  1. Forming: Build the agent and pass custom-scored tests
  2. Storming: Rank production problems across real sessions
  3. Norming: Trace root cause and draft a fix
  4. Performing: Prove the fix with A/B tests and keep it
Agent Optimizer moves an agent through four repeating stages, not a single launch

The post borrows Bruce Tuckman’s model of forming, storming, norming and performing to describe how an AI agent matures. Forming covers building the agent and proving it is ready before it meets customers. Agent Optimizer drafts the agent in Agent Script from a plain-language description, combining deterministic business rules with Atlas Reasoning Engine planning, and builds on existing Salesforce data, Flows, Apex and permissions. Testing with custom scorers is described as coming soon.

Storming is the period after launch, when real customers expose gaps. Agent Optimizer reads production sessions one by one and ranks recurring problems behind escalations, abandonment and low satisfaction. With session tracing enabled, it reads the reasoning trace for each response, showing the topic chosen, actions called, knowledge retrieved and citations. The post says Agent Optimizer is included at no extra cost for standard use cases.

Norming means finding and fixing the cause. Agent Optimizer traces each issue to the exact step where it failed, classifies it as a broken action, knowledge gap or off-topic request, and recommends a fix such as a clearer instruction, a new topic or a knowledge article. It can build and, once testing arrives, test the fix, with the team choosing how much it acts on its own.

Performing covers proving improvements. A/B experimentation, also coming soon, runs a change on a slice of live traffic against the current agent, judged by the same custom scorers, before a winning version ramps to all traffic. Each proven fix stays in the agent’s configuration, and the post says the cycle restarts whenever something changes. The post notes Agent Optimizer is in beta and points readers to their account executive and the help documentation.

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

Worth reading?

Recommended

AIforce exposes Salesforce configuration to outside agents through MCP and the Headless Toolkit (opens in a new tab)

You will learn what AIforce and the Headless Toolkit expose from your org, the five tools that make it up, and how the security model applies to agents acting as users.

Why read this

You will also see what admins should review before opening the org to external agents.

Headless Toolkit

  • MCP servers
  • APIs
  • Skills
  • Plugins
  • Developer tools
The Headless Toolkit has five parts that expose org configuration outward

Salesforce’s AIforce strategy lets people work with Salesforce from the tools they already use, such as Slack, Claude and other AI clients, rather than only from the Salesforce UI. The article places AIforce as the interface layer above Data 360, Customer 360 and Agentforce. It stresses that the Lightning UI, Reports and Dashboards are not going away.

The Headless Toolkit, formerly called Headless 360, is the set of technologies that makes this work. It has five parts: MCP servers, which use OAuth and may be Salesforce-hosted or custom; APIs, including the Agent API and the platform data APIs; skills, which are instruction folders that AI clients load for a task; plugins, which package skills with commands and MCP connections; and developer tools such as the Salesforce CLI, Agentforce Vibes and the declarative Agent Script format. The article says this is an umbrella over existing capabilities rather than a new product, citing 60+ MCP tools, 4,000+ APIs and 220+ CLI commands.

For developers building external applications, there are two routes: the Headless Experience Layer, which renders workflows natively in channels such as Slack, WhatsApp, voice or mobile, or direct calls to the APIs and MCP tools with a custom UI. Either way, the flows, data models and guardrails configured in the org are what they build on.

On security, the article says Sharing Rules, field-level security and Permission Sets are respected however data is accessed, and that calls pass through the Trust Layer. Every call carries identity, access, capability and governance controls, so Validation Rules, triggers and governor limits still apply. Because an agent can do anything the acting user can do, the article advises reviewing profiles and Permission Sets before exposing the org. Agentic Identity, where agents have their own permissions and credentials, is described as planned for the near future.

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

Worth reading?

Must-read

Building and testing agents in the new Agentforce Builder (opens in a new tab)

You will learn how to create an agent from a natural-language description, switch between Canvas and Agent Script views, and test with Simulate and Live Test before committing and activating a version.

Why read this

It is a practical walkthrough of the Builder's main workflow.

  1. Describe the agent in natural language
  2. Refine in Canvas or Script view
  3. Test in Preview
  4. Commit Version
  5. Activate the version
The Builder workflow from creating an agent to going live

The new Agentforce Builder, found under Agentforce Studio, is presented as a way to make agent behavior more predictable by combining an upgraded reasoning engine, Agent Script that mixes natural language with programmatic logic, and built-in AI assistance. An agent can be started by describing its role and tasks in natural language, after which Agentforce generates an initial configuration that can be refined through chat or configured manually.

The Builder is organized into an Explorer for navigating settings, subagents, actions, variables and connections, a Canvas for editing configuration in a low-code block view, a Preview panel for testing, and an Agent Optimizer for natural-language changes. Canvas and Script views stay in sync, so changes made in one are written into Agent Script in the other. Typing a slash adds inline logic such as if/else conditionals, and typing an at-sign opens a resource picker for subagents, actions and variables.

Preview offers Simulate, which skips permission checks and does not run actions or touch data, and Live Test, which runs actions and changes data in the org. Both show reasoning explanations, traces, variable values and timing per step. Finally, a version is committed as a locked snapshot and activated; only one version can be live at a time, and activating a new one turns the previous one off.

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

Worth reading?

Skills admins need to build with AIforce's MCPs, Skills and Plugins (opens in a new tab)

You will learn how MCPs, Skills and Plugins fit together in the AIforce extensibility stack and which new admin skills to pick up first.

Why read this

It gives a roadmap and the training trails to follow.

  1. User triggers a Plugin
  2. Skill fires
  3. MCP executes
  4. Output returns to user
How the AIforce building blocks work together when a user acts

The post introduces AIforce as a new layer of the AI extensibility stack and explains three building blocks. MCP, the Model Context Protocol, is a standard bridge between an AI interface and live systems, data and APIs, so admins can expose flows, APIs and Apex without writing custom code for each system. Skills define the exact steps, rules and formatting an AI needs to complete a task consistently, and Plugins package MCP connectors, Skills and interfaces into a single installable product. It describes a flow in which a user triggers a Plugin, a Skill fires, an MCP executes and the output returns to the user.

The author lists the new admin skills to develop: MCP management, including centralised org-wide connections and Agentic Identity; building deterministic agent logic with Super Agents and Subagents; lifecycle management of Plugins mapped to user roles; and using Agentforce Coworker, Agent Script, Builder Central and Agentforce Vibes for AI-assisted building. The roadmap moves from AI Trust, Security and Governance trails through hands-on work with Agentforce Studio to advanced building and packaging, then ongoing change management.

The article is largely an overview with links to trails, workshops and resources rather than technical implementation detail, so practitioners will get orientation more than hands-on specifics.

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

Worth reading?

Must-read

Route real phone calls to your Agentforce Voice agent using Salesforce CLI and Omni-Channel flows (opens in a new tab)

You will learn how to configure an Agentforce Service Agent user, request a phone number, and build a one-element Omni-Channel routing flow to connect callers to your voice enabled script.

Why read this

You will also know how to verify call routing and inspect post call records using the Salesforce CLI.

  1. Verify entitlements and licenses
  2. Create an Agentforce Service Agent user
  3. Build an Omni-Channel routing flow
  4. Activate the flow and PSTN Voice channel
  5. Test the call and query records
This diagram shows the five-step process for routing real phone calls to an Agentforce Voice agent

The article explains that routing live calls requires an active Agentforce Voice agent, a dedicated Einstein Agent User license, and available inbound voice credits. Developers must verify entitlements and create a service agent user through the Salesforce CLI before configuring any routing logic.

A call reaches the agent through three linked components: a purchased phone number, a PSTN Voice channel, and an Omni-Channel flow. The flow requires a single input variable named recordId and one Route Work element that directs the call to the activated service agent, with a voice queue as a fallback.

After activating the flow and channel, administrators can test the connection by dialing the assigned number. Since live sessions do not generate transcripts, the author demonstrates how to query VoiceCall and AgentWork records via SOQL to confirm call duration, vendor type, and successful routing.

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

Worth reading?

Recommended

Using the JSON Path function in AgentScript to extract and filter data (opens in a new tab)

Readers will learn the syntax and practical examples for using the JSON Path function in AgentScript to select, range, and filter data from action responses without writing Apex or Flow.

The article introduces the JSON Path function available in AgentScript, explaining how it extracts data from objects and lists using standard expressions. The function takes three arguments: the source variable, the query path, and an optional default value to return when no match is found. All queries return results as a list.

Several practical examples demonstrate how to navigate nested data structures. The author shows how to retrieve a specific field from a single record, use asterisks to pull the same field from every item in a collection, and apply slice notation to grab a subset of records. Each example includes the exact expression and the resulting output.

Filtering logic allows users to narrow down collections based on conditions before extracting values. The piece illustrates how to combine equality checks and logical operators to isolate records matching multiple criteria. The author warns that while filtering works in sandbox environments, official documentation currently omits these expressions, advising caution before deploying them to production.

Read the original at dev.to (opens in a new tab)

Worth reading?

Recommended

Fixing time zone mismatches in Agentforce agents with proper input types (opens in a new tab)

You will learn how to prevent time zone conversion errors in Agentforce by enabling user profile context, adding explicit LLM instructions, and typing action inputs as ISO 8601 strings.

Why read this

The guide also shows how to structure these elements in an Agent Script that calls a Flow.

The article addresses a common failure mode where Agentforce agents misinterpret local time because Salesforce stores DateTime values in UTC while users communicate in their local time zones. It outlines three required components to fix this: exposing the user profile context, providing explicit reasoning instructions to the large language model, and defining action inputs with the correct data type.

A complete Agent Script example demonstrates an Employee Agent that manages calendar events. The script enables the user profile context to retrieve the current user time zone without asking the user. Reasoning instructions direct the model to apply that time zone for display purposes while omitting offset details from the conversation. Conditional logic gates event actions behind a valid record identifier.

The workflow passes deterministic parameters like account identifiers directly to the Flow, leaving only the start datetime field open for natural language processing. By assigning the lightning__dateTimeStringType complex data type to that input, the agent converts conversational phrases into structured ISO 8601 values before handing them off to the downstream Flow.

Read the original at InfallibleTechie (opens in a new tab)

Worth reading?

Must-read

How to voice-enable an Agent Script agent with proven best practices (opens in a new tab)

Readers will learn the exact configuration blocks needed to enable voice in an Agent Script agent and how to adjust system instructions for spoken delivery.

Why read this

The guide also covers org prerequisites and deployment steps to avoid common speech-to-text pitfalls.

  1. Verify Agentforce Voice is active
  2. Insert language, telephony, and modality blocks
  3. Rewrite instructions for spoken delivery
A streamlined workflow to voice-enable an Agent Script agent

Before modifying any code, administrators must verify that Agentforce Voice is active in the organization. Once enabled, adding voice capability follows a straightforward two-part workflow that keeps the core agent logic intact while routing conversations through a telephony channel.

Developers need to insert three specific configuration blocks into their Agent Script files. These blocks define the supported language, establish the telephony connection, and select the outbound voice model along with its persona. The nested settings ensure the correct speech synthesis engine handles both incoming audio transcription and outgoing responses.

Because listeners cannot reread text, the system prompts require careful rewriting. Replies must be concise, free of markdown or raw code snippets, and formatted so symbols are spoken as words. The guide emphasizes training the agent to silently correct common speech-to-text errors, such as mishearing technical terms, before providing a final response.

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

Worth reading?