How to choose your first Agentforce use case

The short answer: Choose a first Agentforce use case that is frequent, low-risk, easy to check and sits on data you trust. Score each candidate from one to five on those four things, drop anything that scores a one on risk or data, and write the stop condition before you start. Answering questions or drafting for a person to review beats changing records or messaging customers.

Say three ideas land on your desk in the same week. Sales wants an agent that updates opportunities from call notes. Support wants one that answers order questions. The COO wants one that “handles renewals”. All three are reasonable, and nobody has said which should go first, or what would make you stop.

The first one sets how much your company trusts the next ten. Here is a way to pick it on purpose.

What makes a good first Agentforce use case?

A good first use case has four traits: it happens often, a mistake is cheap, a person can tell quickly whether the output is right, and the data underneath is reliable. Salesforce’s own getting-started advice says much the same: focus on one achievable use case, look for high-volume simple requests, and ground the agent on smaller, clean pieces of data before widening it.

Here’s what each trait means in practice.

  • Frequent. You need enough real examples to learn from within weeks, not quarters. A task that comes up twice a month will take half a year to tell you anything.
  • Low-risk. If the agent is wrong, nothing irreversible happens: no money moves, no customer is told something binding, no record is silently changed.
  • Easy to check. Someone can read the output and know in seconds whether it’s right. “Is this the correct return window?” is checkable. “Is this a good account strategy?” is a matter of taste.
  • On data you trust. The records and articles the agent reads are current, deduplicated and mean what the fields say. This is the one that sinks most pilots, and it’s the part you can fix before you start.

How do you score a use case?

Score each candidate one to five on each trait, add up the four, and apply two rules. Use the table below, which is plain enough to paste into a spreadsheet. The scores are judgment, so have two people score separately.

CandidateFrequent (1 = rarely, 5 = daily)Low-risk (1 = costly if wrong, 5 = harmless)Easy to check (1 = needs an expert, 5 = obvious)Trusted data (1 = messy, 5 = clean)Total (of 20)
Example: answer common policy questions from published articles545418
Example: update opportunities from call notes423211
Your candidate 1
Your candidate 2

Both example rows are illustrative, to show the method. They aren’t measurements.

The rules, which are our opinion and not Salesforce’s:

  1. A one in low-risk or trusted data disqualifies it as a first pick. A high total can’t buy that back.
  2. Sixteen or more is a reasonable first pilot. Eleven to fifteen means fix the weak column first. Under eleven, leave it for later.

Also answer one yes or no question outside the score: does a named person own this and want it? A use case without an owner stalls the week after the demo.

What are examples of good and bad first use cases?

Good first use cases mostly read and suggest. Bad ones mostly decide and change. Here are generic examples, described by kind and not by company.

Usually a good first pickWhyUsually a bad first pickWhy
Answer a common internal question from published articlesFrequent, checkable against the sourceUpdate or merge records without reviewMistakes are silent and hard to find
Summarize a case or account history for a personA reader spots errors at a glanceSend messages to customers unreviewedErrors reach the customer first
Draft a reply for a person to approveA human is the checkAnything involving refunds, discounts or pricingMistakes cost money
Suggest a category for incoming requests, with a person confirmingLow-risk, easy to compareWork that depends on a messy field everyone uses differentlyData trust is a one
Find the right article for a questionRead-onlyAn open-ended task with no right answerNobody can say if it worked

The good column starts with answer, summarize, draft or suggest. The bad column starts with update, send or decide. Acting comes second, once the reading and suggesting has proved right.

What can go wrong even with a good candidate?

The agent runs as a user, and it believes your data. If three records exist for the same customer, it may answer from the wrong one, confidently. If its user can see more than anyone intended, it can repeat what it finds. A low-risk use case reduces the damage; it doesn’t remove the cause.

So before you build, check two things. First, look at the data the use case reads: duplicates, empty fields, fields that mean different things to different teams. Our post on Agentforce data readiness goes through it, and the Agent Readiness Checklist turns it into 25 yes/no checks. Second, check what the agent’s user can see and change. If the answer is “everything”, fix that first.

The platform already helps with the rest. Salesforce’s developer documentation describes a Testing Center and a testing API for agents, so use them in a sandbox with realistic questions, not the clean ones from the demo. Salesforce’s Dreamforce 2026 list includes Agent Health Monitoring (labeled GA), and its Winter ’27 platform blog lists an Observability Center in beta. Check the status for your org first. For afterwards, see how to tell what an AI agent changed.

How do you set a stop condition for an Agentforce pilot?

Write down, before the pilot starts, the specific results that end it. A pilot without a stop condition becomes a permanent experiment. Fill in the blanks below with numbers that suit your volume, and agree them with the owner in advance.

Pilot stop condition (template)

– End date: The pilot ends on ___ whatever else happens. Extending needs a written decision.

– Review: A named person reads every response for the first ___ days, then a sample of ___ per week.

– Stop early if: reviewers mark more than ___ in 10 responses wrong in any week; the agent shows anyone data they shouldn’t see; any record changes that nobody expected; or the reviewer can’t keep up.

– Continue if: the wrong-answer rate stays under ___ for ___ weeks in a row, and the owner still wants it.

The blanks are deliberate. Salesforce’s getting-started advice says to decide what you’ll measure before launch, and we can’t know your volumes. If you can’t fill a blank in, you’ve learned the use case isn’t easy to check yet.

What to do Monday:

– List five candidate use cases on one sheet. Don’t evaluate yet.

– Score each one with the table, with a second person scoring separately.

– Take the top scorer that passes both rules and name its owner.

– Fill in the stop condition template and send it to the owner before anyone builds anything.

Where we come in

The working session in week two of our Agentforce Readiness Sprint does this scoring with the people who do the job today. The Sprint lasts two to four weeks and ends with a use-case short list, guardrails and a pilot plan including a stop condition. It’s a plan, not the build, and it isn’t a licensing review.

Questions people ask

Should my first Agentforce use case be customer-facing?

Usually not. An internal use case lets your own staff catch mistakes before a customer does, and gives you real examples with less at stake. Once an internal agent has run cleanly through its pilot, a customer-facing version with a human approving replies is a sensible second step.

How long should an Agentforce pilot run?

Long enough to see ordinary cases and a few odd ones, so volume decides more than the calendar. Pick an end date up front, check in weekly, and extend only by written decision. A pilot that has no end date has no stop condition either.

Does this scoring only work for Agentforce?

No. The four traits apply to any AI assistant, from a chat tool to a custom build. We use Agentforce as the example because the platform is where your data already lives, and its permissions apply to the agent. The scoring itself needs no license.

Sources