The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Poor agent context inflates token use and Flex Credit spend (opens in a new tab)

You will learn how weak business context makes Salesforce agents burn far more tokens, and which low-cost habits (documenting objects, defining terms, cleaning records, using Flow where no reasoning is needed) reduce that cost before Headless Platform Interaction metering starts.

  • 43,000: Tokens used without the harness, with a wrong answer
  • 7,000: Tokens used with the configured harness
The same question used far fewer tokens once the agent had proper business context

A Dreamforce demo followed a sales rep asking an agent which customers to focus on to close a Q3 gap. Without a harness, the agent used 43,000 tokens and gave a wrong answer: it recommended a frozen customer, missed a renewal already in the pipeline, and misread fiscal Q3. With a properly configured harness that pulled live pipeline data, used a semantic layer to define Q3, and drew on memories of past customer interactions, the same question took 7,000 tokens and produced a sound answer.

The article argues that Flex Credit burn comes largely from the context an agent must work out for itself. Outcome-based pricing and the planned charge for Headless Platform Interactions make this matter, since the meter runs whether or not the answer is good. No multiplier has been published yet, and Salesforce has promised 30 days’ notice before metering starts. Context packs let a harness supply only the subset of information an agent needs, so the aim is the right context rather than the most context.

The author suggests practical steps for now: fully document the one or two objects agents will rely on most, write down ambiguous definitions such as fiscal quarters, clear stale and duplicate records, use a plain Flow where a deterministic answer is enough, and record a consumption baseline before metering gets more complicated.

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

Worth reading?

Recommended

Salesforce plans agent identities and metered billing for Agentic API calls (opens in a new tab)

You will learn what Agentic Identity and Headless Platform Interactions are, which calls count toward Flex Credits, and when the transition deadlines and production-only billing rules apply.

Why read this

The exact multiplier is still unannounced.

Traditional integrations

  • Existing pricing kept
  • Existing security kept

Registered agents

  • Counted as HPIs
  • Drawn from Flex Credits
Traditional integrations keep existing terms, while agentic interactions move to the new HPI model

Salesforce has described upcoming changes to AIforce and the Headless Toolkit in its help documentation. The main changes are agent-specific security features, agent registration, and a consumption-based billing model. Agentic Identity would give AI agents their own identity rather than having them act under the identity of the human they assist, allowing separate credentials, finer permissions and better oversight.

Successful calls by registered agents, whether through MCP or direct APIs, will be counted as Headless Platform Interactions and drawn from Flex Credits, monitored through Digital Wallet. The author stresses that the Flex Credits multiplier has not been announced, agentic consumption is not yet metered, and Salesforce will give 30 days’ notice before metering begins. Traditional integrations keep their existing pricing and security arrangements.

Transition timing differs by customer type: new customers must register agents via APIs within three months of the Agentic Identity availability notice, existing API customers migrate at renewal, and MCP server users have three months from notice. Sandboxes, Scratch Orgs and Developer Edition orgs will not consume Flex Credits for HPIs. The author argues architects will need to plan for call volumes, permissions, monitoring and cost forecasting for multi-call agent tasks.

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

Worth reading?

How to enable and assign the Slackbot UI permission in Salesforce (opens in a new tab)

You will learn how to connect your Salesforce org to Slack and configure the Slackbot UI system permission so users can access the agent directly in Lightning Experience.

  1. Connect Salesforce org to Slack workspace
  2. Create a Permission Set for Slackbot
  3. Enable the Slackbot UI system permission
  4. Assign the Permission Set to users
The setup sequence for giving users access to Slackbot in Salesforce Lightning

The article outlines the configuration steps required to make Slackbot available inside Salesforce Lightning Experience. Before any user-facing features can be enabled, administrators must link their Salesforce org to a Slack workspace through the Manage Slack Connection setting and accept the pending request.

Access is controlled via a dedicated system permission called Slackbot UI. Administrators create a Custom Permission Set, navigate to System Permissions, check the box for the Slackbot UI capability, and save the changes. The Permission Set is then assigned to individual users or groups who require access.

Best practices emphasize validating the connection in a Sandbox first, using a dedicated Permission Set for easier auditing, and setting assignment expiration dates for pilot phases. The guide also notes that using Slackbot may require Flex Credits approval from a Salesforce administrator, and recommends verifying that the agent respects existing object and field-level security before full deployment.

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

Worth reading?

Salesforce discusses partner concerns over new AI agent billing model (opens in a new tab)

Readers will learn how Salesforce plans to charge Flex Credits for external AI agent interactions via MCP and APIs, and what partners are urging the company to adjust regarding predictability and friction.

Salesforce has introduced a pricing model requiring external artificial intelligence agents to register on the platform and consume Flex Credits for every successful call made through the Model Context Protocol or direct application programming interfaces. The initiative tracks each interaction as a Headless Platform Interaction, shifting costs away from traditional seat licensing toward usage-based billing for agentic traffic.

The announcement triggered significant pushback from implementation partners and independent architects who warned that per-action charges would create financial friction and discourage developers from building around the platform. Critics noted that customers already face heavy seat costs and questioned whether the market would accept paying for every individual request made by automated systems.

In response to the community reaction, Salesforce leadership initiated direct conversations with key ecosystem stakeholders to address these concerns. Participants emphasized the need for transparent pricing structures, additional platform value to justify the fees, and mechanisms that allow partners and administrators to continue leveraging artificial intelligence tools without unexpected production expenses.

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

Worth reading?

Recommended

Six checks to vet agents and MCP tools before installing from AgentExchange (opens in a new tab)

Readers will learn a structured six-point checklist for evaluating the security, permissions and costs of agents and MCP tools before they reach production.

Why read this

The guide explains how to test these integrations safely and establish ongoing monitoring.

The article outlines the transition of AppExchange to AgentExchange, noting that the marketplace now hosts agents, subagents and MCP servers alongside traditional managed packages. It emphasizes that these newer components operate at runtime rather than just adding static metadata, which changes how administrators must assess their impact.

Authors provide a six-step verification process covering security review status, profile access limits, data flow mapping, agent user permissions, pricing structures using Flex Credits, and publisher reputation. They stress that passed security reviews set a baseline but do not guarantee safe runtime behavior.

The piece recommends a Sandbox evaluation workflow that includes testing under different user states, allowing only necessary MCP tools, enabling logging, and modeling costs at projected volumes. It concludes with operational rules such as enforcing least privilege, requiring weekly transcript reviews during pilots, and defining offboarding procedures before deployment.

Read the original at dev.to (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?

Must-read

Preparing your org for the Claudeforce partnership and new billing model (opens in a new tab)

Readers will learn how to configure the Salesforce in Claude plugin, audit permissions for agentic access, and prepare for the November billing model using Flex Credits and agent registration.

  1. Audit Permission Sets and profiles
  2. Clean the fields the skills read
  3. Keep approvals on
  4. Pilot in a sandbox
  5. Name an owner for connections
Five checks to prepare your Salesforce org for Claudeforce and AIforce billing

Claudeforce, the expanded Salesforce and Anthropic partnership announced on August 26, 2026, works in two directions. Claude becomes a reasoning model inside Agentforce and the default model in Slack, while Salesforce reaches into Claude through the Salesforce in Claude plugin. That plugin bundles 37 prebuilt sales skills covering account research, call prep, pipeline review and CRM updates, with Salesforce and Slack connectors. It is in beta for approved orgs on paid Claude plans and requires the latest Sales Cloud Enterprise edition.

On security, sellers sign in with their own Salesforce credentials, so Claude can only do what their permissions allow, and by default it asks for approval before any write. Salesforce Help notes that when a custom action uses a Claude model hosted inside the Salesforce Trust Boundary, data stays inside that boundary, though Einstein Trust Layer data masking is disabled for those agents and zero data retention still applies. The article advises reading that page in full before writing a risk assessment, and it warns that most capability claims come from launch material and should be tested in a sandbox first.

The setup path has four stages. First, the org confirms eligibility and gets approval through the beta sign-up on AgentExchange. Second, a Salesforce admin creates an External Client App for Claude, because Connected Apps are not supported for MCP clients. Third, a Claude Primary Owner or Owner enables the plugin in Organization settings and enters the app’s consumer key and secret. Finally, each member signs in with their own Salesforce account on first use.

The billing changes are targeted for November. Admins register agents, each of which gets its own identity and can hold a narrower Permission Set than a human user. Every successful MCP or API call from a registered agent counts as a Headless Platform Interaction, paid with Flex Credits, though the rates are still TBA and metering applies only to active production orgs, with 30 days’ notice before it starts. Customers who buy on or after September 17, 2026 must register agents at purchase, while existing customers register at renewal. The article does not say how the Salesforce in Claude plugin will be classified under this model.

The article recommends five preparation steps: audit Permission Sets and Profiles, clean the fields the skills read, keep approvals switched on, pilot in a sandbox, and name an owner for connections and consumption. Cloud Odyssey’s own view is that Claudeforce exposes existing CRM data quality problems, and it suggests starting with a health check, connecting surrounding systems, piloting with one team, and keeping model choice open.

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

Worth reading?

Recommended

New Flex Credit pricing for AI agents risks pushing customers toward ungoverned architectures (opens in a new tab)

Readers will learn how Salesforce plans to charge Flex Credits for AI agent interactions through MCP and direct APIs, and why this pricing structure creates financial pressure to bypass governed platform access.

Why read this

The article outlines practical steps for modeling usage volumes and optimizing agent workflows to control costs without compromising security.

Salesforce intends to bill Flex Credits when third-party AI agents successfully call into the platform via MCP or standard APIs. This pricing strategy conflicts with the company’s push for structured, governed machine access, creating a financial incentive for customers to minimize platform interactions.

Charging per successful interaction can lead to double billing alongside external AI vendor costs. Because autonomous agents generate significantly more API calls than human users, the cumulative expense grows quickly. Teams facing these costs may resort to duplicating data externally or routing logic outside Salesforce to avoid fees, which undermines the intended security and traceability benefits of Agentic Identity and the Headless Toolkit.

The author advises teams to accept the current policy while proactively modeling worst-case usage scenarios to forecast expenses. Practitioners should track exact interaction volumes, prepare data for negotiations with account executives, and optimize agent designs to reduce unnecessary calls. The guidance emphasizes maintaining governed architectures rather than building workarounds that violate platform policies.

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

Worth reading?