Use cases by system2 use cases
AI on Salesforce without buying Agentforce for one use case
Salesforce is where sales data is supposed to live, and often does not. A thread on r/sales this spring, with 176 comments, was about an insurance rep at 120% of quota reprimanded for not copying WhatsApp, iMessage and Facebook chats into 40 required dropdowns. The builds in this hub fix that end of the problem: qualifying and routing inbound leads before they go cold, and writing call and email outcomes back to the CRM once the rep approves.
Salesforce's own answer is Agentforce, and its pricing shows who it is for: $2 per conversation, or Flex Credits at $500 per 100,000 credits, which works out to about $0.10 per action, plus per-user add-ons from $125 a month and Agentforce 1 editions from $550 per user a month. For a service organization already deep in Service Cloud and Data Cloud, that can be reasonable.
For a 30-seat sales team that needs one workflow, it is a platform decision made for a feature. A custom agent instead signs in as an API-only integration user, pays for model usage, and reads the systems Salesforce does not hold. Both paths are legitimate; the deciding question is how many use cases you will actually run.
What to build around Salesforce
Every inbound lead researched, scored and routed before a rep opens it
Researches and scores every inbound lead against your rubric, catches existing customers, routes by territory and capacity, and replies with a booking link.
HubSpot / Salesforce / Enrichment provider (Clay or Apollo) / Cal.com or Calendly / Slack
Sales calls and emails that update the CRM on their own, after the rep approves
Reads customer calls and email threads, proposes stage, next step and close date changes with evidence, and writes them to the CRM after one click from the rep.
HubSpot / Salesforce / Gmail or Outlook / Zoom, Google Meet or Microsoft Teams / Slack
API budgets, change events and validation rules
API calls are a shared daily budget
Every org has a rolling 24-hour API allocation tied to edition and licenses, shared by the ERP sync, the marketing tool and anything new. The build uses composite requests, Bulk API 2.0 for backfills, and events instead of polling, so it does not starve the others.
Change events instead of polling
Change Data Capture and Platform Events, delivered through the Pub/Sub API, tell the agent when a lead or opportunity changes. After an outage it resumes from the last stored replay ID instead of rescanning the org.
Validation rules push back
Writes fail on validation rules and required fields. The agent treats each failure as a question for the rep, never as something to force through with a placeholder value.
A dedicated integration user
The build runs as an API-only integration user whose permission set grants exactly the objects and fields it needs, so field-level security keeps it away from everything else.
Flows hand the work over
A record-triggered Flow can publish a Platform Event or make an HTTP callout, so your admins decide inside Salesforce when the agent gets involved, and can switch it off the same way.
When Agentforce is the right answer, and when it is not
Agentforce fits Salesforce-centered service
High-volume case deflection on Service Cloud, customer data already unified in Data Cloud, and an admin team that will own the agents: that is the setup Agentforce is priced for.
One use case rarely justifies it
Licenses, credits and configuration time for a single lead-routing flow usually cost more than building the flow. If a roadmap of agent use cases follows, the math changes, and I would say so.
Data that lives outside the org
Agentforce works best on data already in Salesforce or Data Cloud. A quote that needs ERP stock, a lead arriving on WhatsApp or a renewal that depends on billing can be handled by an agent that queries those systems where they are, with no data project first.
Assistants and MCP
Buyers ask for a custom MCP server so Claude or Copilot can read the pipeline. Salesforce has announced MCP support of its own, so I check what your edition includes before building one.
Frequently asked questions
How much does Agentforce cost?
Salesforce lists several models: $2 per conversation, Flex Credits at $500 per 100,000 credits with an action costing about $0.10, per-user add-ons from $125 a month, and Agentforce 1 editions from $550 per user a month. Which one applies depends on the use case and your contract, so model it on your real volumes against the current pricing page.
Is Agentforce worth it for a mid-sized company?
It can be, if Salesforce is the center of your service or sales operation and you plan several agent use cases. For one workflow, such as routing inbound leads or logging call outcomes, a custom integration is usually cheaper and quicker to change. The honest test is how many use cases you will run in the next year.
Can Claude or ChatGPT connect to Salesforce?
Yes, through MCP servers or connectors, and search suggestions show people asking for custom MCP servers for Salesforce and Copilot Studio. For a team, the connection should run as a scoped integration user with read-only tools by default and approval for writes, so an assistant cannot change records nobody asked it to touch.
Can AI fill in Salesforce fields from calls and emails?
Yes, within your org's rules. The conversation is mapped to the fields your record type requires, picklist values are chosen only from the allowed list, and the rep approves the changes before anything is saved. Validation rules still run on save, and a required field the conversation never covered goes back to the rep as a question instead of being filled with a guess.
Also browse: Sales and lead handling · SaaS · HubSpot · all use cases