Salesforce
genAI agent deployed in-house on its own funnel (inbound lead qualification and self-service support)
Salesforce uses its own Agentforce agent on help.salesforce.com (4.3 million inquiries, 70% resolved) and on its inbound funnel, where it identified 130 million dollars in pipeline autonomously.
Key points
- Agentforce genAI agent deployed in-house on support (help.salesforce.com) and inbound lead qualification.
- Agentforce stack plus Data Cloud and RAG on the knowledge base, with a human in the loop.
- 4.3 million inquiries handled on the portal (70% resolved), $130M in pipeline identified autonomously.
- Evidence level A, confirmed status.
Objective
Run its own growth with its own product. Salesforce uses Agentforce on its web properties to qualify inbound leads and generate pipeline, and on help.salesforce.com to resolve support inquiries without a human, publicly dogfooding the technology it sells.
The deployment
Salesforce put Agentforce into production on its own channels. On help.salesforce.com, the agent handles help inquiries and resolves a large share of cases end to end, on a portal that sees about 60 million sessions and more than 2 million support cases per year. In parallel, a qualification agent (SDR / Engagement Agent) works inbound leads: it engages contacts, creates opportunities, and feeds the sales pipeline, first under human supervision and then autonomously with a human in the loop. Salesforce communicates these figures as proof of real use of its own product.
Results Proof A
The portal figures (4.3 million inquiries, 70% resolved) appear in an official Salesforce release, and the internal pipeline figures are attributed by name to the CMO of Agentforce Applications. Aligned sources, official release plus trade press, with exec confirmation on earnings.
How it works
Documented architectureThe stack in detail
- plateforme Salesforce Agentforce Salesforce's LLM agent platform, deployed in-house for support (help.salesforce.com) and inbound lead qualification.
- plateforme Salesforce Data Cloud Data layer that connects the agent to the contact's CRM history.
- outil Moteur RAG sur knowledge base Retrieval-augmented generation over the product knowledge base; without an up-to-date KB, the resolution rate drops.
- outil CRM Salesforce Creation of opportunities and tracking of the pipeline generated by the agents (SDR / Engagement Agent).
How it runs, concretely
For ops teams-
1Intent detection AI
The agent identifies whether the visitor is seeking support, product information, or is a lead to qualify.
-
2Knowledge-grounded response AI
It responds by drawing on the knowledge base and CRM data via RAG, on help.salesforce.com or on the site.
-
3Qualification and opportunity creation AI
For a lead, the agent engages, qualifies, and creates the opportunity in the CRM.
-
4Handoff to a human Sales / support team
Complex or high-stakes cases are routed to an SDR or a human support agent.
-
5Measurement and adjustment Revenue operations
Resolution rate, pipeline generated, and conversion are tracked to adjust the agent's prompts and scope.
The product knowledge base and the contact's CRM history. Without an up-to-date knowledge base and clean CRM data, the agent hallucinates or misqualifies, and the resolution rate drops.
How your customers perceive this type of use
Sourced studiesLes consommateurs n'acceptent pas les chatbots par defaut : 64% prefereraient que les entreprises n'utilisent pas d'IA dans leur service client (Gartner, 2024) et pres d'un utilisateur sur cinq du service client par IA n'en retire aucun benefice (Qualtrics, 2025). L'acceptation se construit sur trois conditions mesurees par Salesforce : savoir qu'on parle a une IA, pouvoir escalader vers un humain, comprendre la logique de l'agent.
Acceptance conditions
- Etre informe qu'on parle a une IA et non a un humain (pres de 75% le demandent, Salesforce 2024)
- Un chemin d'escalade clair vers un agent humain (45% plus enclins a utiliser l'agent IA, Salesforce 2024)
- Une logique de l'agent clairement expliquee (44% plus enclins, Salesforce 2024)
Red lines
- Rendre l'humain injoignable : c'est la premiere inquietude des consommateurs sur l'IA dans le service client (Gartner 2024) et 50% craignent que l'IA les coupe du contact humain (Qualtrics 2025)
- Remplacer le service client par l'IA sans alternative : 53% envisageraient de partir chez un concurrent (Gartner 2024)
Sources: Salesforce 2024 · Gartner 2024 · Qualtrics 2025
How to replicate
Inference, not sourcedData prerequisites
- a structured product knowledge base
- clean first-party CRM data
- support and lead history
Org prerequisites
- a revenue operations team
- an escalation process to humans
- governance of prompts and agent scope
Possible stack
- an agent platform (Agentforce, Copilot Studio, in-house agent)
- CRM
- CDP
- a RAG engine over the knowledge base
The plan, step by step
- Step 1Clean up the product knowledge base and define the scope of inquiries covered and excluded by the agent.Deliverable: Up-to-date KB and a validated list of covered cases.
- Step 2Configure the agent (support or lead qualification) with a human in the loop and escalation rules to SDR / support.Deliverable: Agent in pre-production on a single channel.
- Step 3Launch a pilot on limited real traffic and measure resolution rate, qualified leads, and pipeline created.Deliverable: Resolution/pipeline dashboard on real data.
- Step 4Broaden the scope and degree of autonomy based on observed quality, keeping supervision on high-stakes cases.Deliverable: Agent in production with documented supervision rules.
First step: Connect an agent to an up-to-date knowledge base and a narrow scope of inquiries, with a human in the loop.
Sources
- S1 Salesforce Launches Agentforce Help Agent That Deploys in Minutes and Only Charges for Resolutions Primary archive pending
- S2 Salesforce Agentforce applications transform marketing workflows Secondary archive pending
- S3 Salesforce's AI Agents Are Now Outworking Its Human Support Teams Secondary archive pending
- S4 Agentforce Now Live on Salesforce Help Portal, Marc Benioff Reveals Secondary archive pending
An error, newer info, a source?
This page lives on its accuracy. If a figure has moved, if the deployment has changed, or if you have a higher-quality source, tell us. Every sourced correction is verified before publication.