Hi Reader,

Welcome to The CRM Signal — Issue 39, week of September 26, 2026.

SIGNAL · Salesforce and Anthropic put Claude inside CRM workflows · Agentforce zero-click data exploit disclosure · HubSpot's agentic Breeze and self-updating Smart CRM​

▸ The Signal

The Agentforce cost model just got harder to forecast. Salesforce now applies Flex Credits to MCP and API calls, turning integration traffic into a budget question before many teams have a reliable way to model it.

Salesforce confirmed that Flex Credits cover MCP and API calls, not just conversational agent interactions. In practice, a production Agentforce deployment that touches agentic APIs or Model Context Protocol integrations can now generate metered charges under rules that are still incomplete.

​Salesforce Ben's report on the change, published September 24, matches the concerns surfacing in practitioner discussions: per-call multipliers are not public, unused credits do not roll over, and there is no confirmed org-level control for disabling default-on agent billing.

That makes consumption modeling speculative rather than calculable. Teams are having to compare the $2-per-conversation fee, the $500-per-100,000-credit option, and blended consumption structures in the same spreadsheet. Buyers who want to move agents into production cannot give finance a credible cost forecast, so procurement stalls.

The constraint is not agent capability. It is the inability to estimate what running that capability will cost at scale. Digital Wallet logging and Salesforce identity requirements may improve visibility after deployment, but they do not solve the planning problem. Until Salesforce publishes per-call multipliers, clarifies rollover policy, and documents whether default billing is configurable at the org or profile level, cost forecasts remain estimates.

▸ Platform Moves

Salesforce and Anthropic put Claude inside CRM workflows

Salesforce confirmed at Dreamforce that CRM data, workflows, and permissions will be accessible through an AI layer that includes a Claude integration inside the CRM and a Slack-based agent surface. The Claude integration is in beta—not generally available—and ships with 37 prebuilt sales skills.

The direction is clear: Salesforce is treating the browser-based CRM as one access point among several. GA timing, per-seat pricing for the Claude integration, and governance controls below enterprise tiers remain unconfirmed.

→ Salesforce Blog · Salesforce Ben · Salesforce Trail · event coverage​

HubSpot pushes Breeze toward an agentic, self-updating CRM

HubSpot's Fall 2026 Spotlight introduced 134 updates, including a rebuilt Breeze Assistant, automatic capture of calls, emails, and meetings in Smart CRM, a Context Home view, Revenue Hub, and MCP configuration access.

Practitioners read the release as a direct answer to Salesforce's AI positioning, not a routine mid-market refresh. Agent Builder remains in public beta, which limits production readiness for teams evaluating it now. Whether outcome-based pricing for Breeze agents is broadly available or still in regional pilot is unconfirmed.

→ market synthesis · practitioner discussion​

Flex Credit pricing is becoming a deployment gate

Salesforce's extension of Flex Credits to MCP and API calls brings consumption billing into integration and agent workflows. Partner forums and practitioner communities describe sticker shock, unpredictable multipliers, default-on billing, and procurement delays.

The practical consequence is that pricing complexity becomes an adoption barrier, especially for organizations running high-volume automations. Exact per-call multipliers, rollover policy, and whether the Core, Advanced, and Max edition ladder is final across regions remain unconfirmed.

→ Salesforce Ben's reporting · practitioner discussion​

▸ Field Notes

Salesforce Ben reported a data exploit in Agentforce, and Techzine independently described the issue as zero-click CRM data theft. Community threads referenced prompt injection and a named vulnerability circulating as SalesBleed. Salesforce said the issues were fixed and found no evidence of customer exploitation.

The documented vectors centered on public-facing entry points such as lead-capture forms. Security-focused buyers evaluating autonomous agent write access are likely to treat the disclosure as a due-diligence item regardless of the remediation statement. Whether every disclosed vector is fully closed remains unconfirmed.

▸ Verdict

Watch — Salesforce and Anthropic put Claude inside CRM workflows

Multiple independent editorial sources and official Salesforce Blog posts confirm that AIforce and Claudeforce were announced at Dreamforce, with Claudeforce in beta and 37 prebuilt skills. The strategic implication is significant: Salesforce is positioning CRM access as multi-interface rather than screen-bound.

For production buyers, the uncertainty is material. Beta status, GA timing, and governance-tier eligibility are all unresolved, so treat this as a roadmap signal—not a capability to put on a near-term delivery plan.

▸ Buy Side Brief

FOR CRM BUYERS & DECISION-MAKERS

If Claude is going to operate inside CRM workflows, buyers should ask for a GA timeline, seat pricing, data-boundary details, and a written explanation of governance controls below enterprise tiers. Keep the capability in evaluation until those answers are documented and the beta exits.

▸ Watch List

• Watch for Salesforce to publish per-call multipliers, rollover rules, and org-level controls for Flex Credit billing. Those details will determine whether teams can build a defensible production forecast.
• Watch the Salesforce Trust and security-advisory pages for the full remediation scope of the Agentforce zero-click data exploit, including whether the affected public-facing entry points are covered.
• Track Q3 earnings commentary on Agentforce attach rates and any evidence of procurement delays. Continued friction would confirm that Flex Credit complexity is an adoption constraint, not just a negotiation issue.