Salesforce runs its own support on Agentforce and cut support headcount from ~9,000 to ~5,000

Salesforce calls itself 'customer zero' for Agentforce. Its AI agents now handle a large share of customer support conversations on its help site, and the company reduced support roles.

Organization: Salesforce
Industry: Enterprise Software
When: Aug 2025
Evidence: Company reported
Agents and tools: Agentforce

Reported outcome

About 1.5M customer conversations handled by agents, with CSAT about the same as humans; support headcount went from ~9,000 to ~5,000.

~1.5M
Agent conversations
~9,000 → ~5,000
Support headcount
-17% in 2025
Support cost

Caveats

Stated by the company that uses the agent (blog, earnings call, interview). Not independently audited.

Figures come from CEO Marc Benioff on a podcast and from company spokespeople, not an audit.
Salesforce sells Agentforce, so it has a strong reason to show success.
Benioff called the change a 'rebalance'; Salesforce says hundreds of staff moved to sales and customer success.

What the agent does

Agentforce agents answer customer questions on Salesforce's help site. They pull answers from product documentation and case history, and escalate to human support engineers when needed.

What happened

Salesforce says the agents now handle about half of service interactions. It reports a 17% drop in support costs since the start of 2025. It also says it no longer backfills many support engineer roles.

What to copy

Use it yourself first. "Customer zero" deployments find problems before customers do.
Track CSAT for agent conversations separately from human ones.
Plan where people move to before you scale the agent. Redeployment is easier than rehiring.

Starter prompt

Written by us, not by Salesforce.

You are the first-line support agent for {product}.
Search the documentation and known-issue list before every answer.

For each answer:
1. State the fix in numbered steps.
2. Link the exact doc page.
3. Ask if it worked.

Escalate to a human support engineer if: the customer reports data loss,
an outage, a security concern, a billing dispute, or the same issue twice.
Include the customer's org ID and the steps already tried.