Agentforce Use Cases Are Easy to List and Hard to Sort
You have the list. Every Salesforce leader does. Somewhere there is a slide or a spreadsheet with fifteen things the company wants to automate, and the word Agentforce sits at the top of it.
The teams getting the most from Agentforce sort that list first. Some of it is exactly what Agentforce was built for. Some belongs to a different kind of agent, one built around a single person and their context rather than around your records. Get the split right and both do their best work.
So this post does the sorting for you. Nine real pieces of work that almost every Salesforce organization recognizes, each run through the same five questions, each with a verdict and a reason. Use it as a template for your own list.
The short version
- Agentforce runs on records. A custom agent runs on context. One works across your org under your sharing model at volume. The other works around one person, across everything they touch, on work that is different every time.
- Five questions sort almost any candidate. Stable actions, repeat frequency, who is on the other side, audit requirements, and whether the deliverable is a record or a document.
- A split result means two use cases wearing one name. Separate them first. Most arguments about which agent to use end the moment you do.
- The cost shapes differ. Agentforce scales with conversation volume. A custom agent scales with headcount.
- Five of nine land on Agentforce, four on custom. Neither replaces the other, and the order you build them in changes the outcome.
Where the Test Comes From
The five questions below come out of our advisory brief Agentforce or a Custom Agent?, and the reasoning behind them is in our earlier post on why most people draw the line wrong. The short version: Agentforce operates on records, inside your org, under your sharing model, at volume. A custom agent operates on context, around one person, across every system they touch, on work that is different every time.
If you want the cost math worked through out loud, Cirrius Talk Episode 19 has Tim and Nancy pricing the same example both ways, and our cost breakdown post has the numbers in writing.
The cost shapes are different too, and that matters when you sort. Salesforce meters Agentforce by usage. Flex Credits run about ten cents per standard action, and a real conversation burns five to fifteen of them. A custom agent is a flat subscription per person. One scales with conversation volume. The other scales with headcount. Get the sort right and both budgets stay predictable.
The Five-Question Routing Test
Run any candidate through these before anyone scopes anything. Answers on the left point to Agentforce. Answers on the right point to a custom agent.
Are the systems and actions known in advance, and stable? Agentforce if you can enumerate the action list up front. Custom if you will not know what you need until you are in the work.
Does it happen the same way many times a week? Agentforce if the shape repeats. Custom if every instance is materially different.
Who is on the other side of it? Agentforce for a team, a customer, or the whole org. Custom for one person’s own judgment work.
Does the outcome need to be auditable and governed? Agentforce if compliance or a shared record of truth depends on it. Custom if a human reviews and approves before it ships.
Is the deliverable a record change or a document? Agentforce for a field updated, a case closed, a reply sent. Custom for a written artifact, an analysis, or a decision.
One rule before the examples. A split result means you have two use cases wearing one name. Separate them first. Most arguments about which agent to use end the moment you do.
Nine Agentforce Use Cases, With Verdicts
1. Qualify and route inbound web inquiries
Record backed, constant, whole sales team.
Hover for the reason
1. Qualify and route inbound web inquiries
The routing decision needs an audit trail. This is the textbook first use case, and for most orgs it is the one with the cleanest data.
2. Write the quarterly adoption update
A document, written once, from many sources.
Hover for the reason
2. Write the quarterly adoption update
It reflects one person’s read of the org. Topics and actions are built for bounded decisions on records, and long form drafting is a different kind of work.
3. Answer order status on the support portal
Customer facing, high volume, answerable from records.
Hover for the reason
3. Answer order status on the support portal
Deflection you can measure.
4. Draft a response to a nuanced escalation
Judgment heavy, and the context lives outside the CRM.
Hover for the reason
4. Draft a response to a nuanced escalation
It needs the email thread, the contract, and history Salesforce never saw. A human sends the final version, so governance is already in the loop.
5. Nudge reps on opportunities gone quiet
Deterministic rule, runs on records, serves a team.
Hover for the reason
5. Nudge reps on opportunities gone quiet
Twenty-one days with no activity triggers it, and the impact shows up in forecast quality within a quarter.
6. Route and acknowledge inbound support cases
Pure record work with fixed rules.
Hover for the reason
6. Route and acknowledge inbound support cases
By product line and priority. It runs constantly and every routing decision needs to be logged.
7. Summarize win and loss patterns
The instructive edge case.
Hover for the reason
7. Summarize win and loss patterns
The data lives in Salesforce, so people reflexively call it platform work. It is not. The work is unstructured analysis and the deliverable is a document, not a transaction.
8. Answer employee policy questions
Many users, grounded in approved knowledge.
Hover for the reason
8. Answer employee policy questions
It benefits from consistency and logging. Keep the knowledge base curated, because the agent is only as good as the knowledge it is grounded in.
9. Write requirements for a new Agentforce agent
Design work, not transaction work.
Hover for the reason
9. Write requirements for a new Agentforce agent
This is the custom agent building the Agentforce agent, and it is the reason the two compound instead of compete.
Score it up and the pattern is obvious. Five of nine are Agentforce work. Four are custom agent work. Neither one replaces the other. If your own list comes back with items that seem to be both, apply the split rule.
Why the Order You Build Them Matters
Most organizations get better results starting with the individual agent, for two reasons. It costs less to be wrong. And it builds the internal fluency that makes the platform work land properly. The sequence that works:
Prove it on one person. Stand up a custom agent for whoever is carrying the Salesforce agenda. Point it at the work already eating their calendar: documentation, analysis, drafting, meeting prep. No governance conversation required, because nothing is shared yet.
Pick the first platform use case. Run the candidate list through the routing test and choose the highest volume, cleanest data item. For most orgs that is number 1 or number 6 above. Use the custom agent to write the requirements and test cases. Model the usage cost before you commit to a rollout scope.
Scale on evidence. Instrument the deployed agent. Watch escalation, deflection, and error rates. Expand into adjacent processes only where the data supports it, and extend custom agents to other leaders as fluency spreads.
The mistake we see most is inverting this. Teams start with the use case that has the most executive attention rather than the cleanest data, skip the data work to hit a date, and spend the next two quarters rebuilding trust. Early credibility is worth more than early ambition.
Frequently Asked Questions
What is the best first Agentforce use case?
The one with the cleanest data and the highest volume, not the one with the most executive attention. For most Salesforce organizations that is inbound lead qualification and routing, or case routing by product line and priority. Both are record backed, repeat constantly, and produce a measurable result within weeks.
Can Agentforce work outside Salesforce?
Yes. External Services, Apex and Flow callouts, and MuleSoft are all generally available paths, and there is a native MCP client that is still in Beta. The difference from a custom agent is not reach but gravity. Every external action in Agentforce is one you enumerate, build, and govern in advance. A custom agent’s reach is whatever its owner can already access.
When should I not use Agentforce?
When the task is ambiguous, needs judgment, or produces a document rather than a record change. Long form drafting, research and synthesis, and cross system analysis for one person are custom agent work. Agentforce topics and actions are built for bounded decisions on records, and work with no fixed shape is what a custom agent is for.
Do I have to choose between Agentforce and a custom agent?
No, and the highest return pattern is using both. The custom agent is the workshop: it reads the process docs and transcripts, writes the topic instructions and test cases, and later reads the telemetry to draft improvements. Agentforce is the factory floor that runs the finished process at volume with governance and an audit trail.
Run Your Own List Through It
The fastest way to settle the question is to bring the actual backlog. In one working session we sort it into platform work and individual work, identify the Agentforce use case with the strongest data foundation, and stand up a custom agent for the person carrying the Salesforce agenda. Cirrius has delivered more than 2,500 Salesforce implementations, and we build and run both kinds of agent every day, including for ourselves.
Download the full brief, Agentforce or a Custom Agent?, for the side by side comparison and cost model, then bring us your list.
