Parts and Inventory Check Agent

Hannah ticks the handover on the Parts Desk half an hour later, and the transfer completes. The clinic is cooling again by early afternoon, and the florist's cooler is fixed at 2:30 with the relay Ben almost used up.

The demonstration company is in San Francisco, so the agent writes US English. That follows your settings.

• Every van and shelf

  His van, warehouses after their reserve, and colleagues' vans with who has them and where.

  Watch it at 0:49

• The right part

  Only approved substitutes; anything else gets the warranty reason.

  Watch it at 1:15

• The next job, protected

  The last part on the van is kept for a later job that needs it.

  Watch it at 1:23

• From a colleague, fairly

  A colleague's van gives only what their own jobs don't need.

  Watch it at 1:44

• Approve once

  Review Parts Request shows exactly what will be requested.

  Watch it at 1:53

• Tomorrow, sorted

  Every job checked; a fix for every gap; one pick list.

  Watch it at 2:52

• Owners

  Fixed on the first visit.

  Fewer second visits, no parts bought twice and emergency stock where it should be.

• Technicians

  One question, in his own words.

  Asked in the app he already uses, then one tap to approve.

• Warehouse and parts teams

  Nothing to chase.

  Every request arrives approved, tied to a job, with tomorrow's pick lists the night before.

• Salesforce teams

  Built the Salesforce way.

  An Agentforce Employee Agent on standard Field Service inventory, with an approval step and a conversation test suite.

1. 01

   Map your stock

   Warehouses, vans, reserves, the approved-substitute list and who runs the Parts Desk.

2. 02

   Configure in your org

   The agent, Review Parts Request in the app, the Parts Desk and your wording.

3. 03

   Test with your technicians' words

   Real questions from your jobs, replayed before go-live and before every change.

4. 04

   Go live and hand over

   A pilot with a few technicians and one warehouse, then everyone, with a runbook and the test set.

• Field Service: Warehouses, vans and stock, with required parts on your jobs.
• The Field Service app: For your technicians, and Agentforce.
• Your approved list and reserves: Which parts can replace which, and what to hold back.
• A Parts Desk team: Who picks, hands over and orders.

Salesforce products

AgentforceSalesforce Field Servicethe Field Service mobile app

Editions and licenses

Agentforce must be enabled in your org. Confirm editions and licenses with your Salesforce account team; we check them in the first workshop.

Agent type

Agentforce Employee Agent

From you

Field Service · The Field Service app · Your approved list and reserves · A Parts Desk team

Language

English. The agent writes in your locale and follows your wording settings.

Where it runs

Inside your Salesforce org. Records are read and written through the agent’s approved actions only.

Not included

Purchase orders to suppliers stay with your Parts Desk. A colleague is told by a notification when a part comes from their van. It works in the Field Service app on Android and iOS; the review step is a quick action on the job.

Checked against the agent's last validation on 2026-11-06.

• Deployable sourceThe agent, its actions, objects and screens as Salesforce metadata, in your repository.
• Solution designA Solution Design Document with UML: architecture, data model, sequence and security.
• Test suiteApex tests on every action, plus scripted conversations replayed before every release.
• Least-privilege accessIts own permission sets, so the agent and your staff see only what the job needs.
• Runbook and handoverHow to run it, change its rules and roll back, with a walkthrough for your team.

• Least-privilege access

  It runs as its own user with permission sets written for this agent, so it can reach only what the job needs.

• Changes only through approved actions

  The agent cannot edit records freely. Every change goes through one of its 12 actions, each with one job.

• People make the big calls

  Every request is a draft until the technician approves it on Review Parts Request.

• Runs inside Salesforce

  Agentforce runs on the Salesforce platform and its Einstein Trust Layer. Confirm which Trust Layer features apply to agents in your org with your Salesforce account team.

• Every change is on the record

  What the agent does lands as normal Salesforce records with their full history, so you can see who changed what and when.

• The review is free

  A 60-minute call with an architect about the Parts and Inventory Check Agent and your org, with a written plan you keep.

• A fixed-scope proposal first

  Before any work starts you get a written proposal with milestones. You approve it, or you do not.

• Timing follows scope

  How long it takes depends on your setup and your rules. The proposal states the milestones up front.

• Or inside a monthly plan

  Agents can be built and run through one of our monthly delivery plans, alongside your other Salesforce work.

Salesforce licenses, including Agentforce, are bought from Salesforce and are not part of our fee. See our plans and pricing →

• The live run · 4:26

  The full film of the agent on a real Salesforce org, with chapters.

  Watch the film →

• One-page brief (PDF)

  What it does, the rules it follows and what you need, on one page you can forward.

  Get the brief →

• Slide deck (PDF, 8 slides)

  For your team or steering group: the problem, what it does, the rules it follows and how we deliver it.

  Get the slides →

• Talk to an architect

  A free 60-minute session on how it would work in your org, with your processes, your data and your rules.

  Book a session →

• The whole library

  Every agent we offer, by business area.

  Browse agents →

Further reading from our architects

• Claudeforce: what actually changes for the people who run the orgSalesforce and Anthropic announced Claudeforce on 26 August 2026. What the sources actually state, what nobody has published yet, and what to do in your org before the beta reaches you.
• The grounding checklist we run before an agent talks to a customerTwelve pre-flight checks we run before an AI agent is allowed near a real customer, each with the failure it catches and the fix. A go or no-go list, not a readiness score.
• Personalisation with an agent in the loopWhere generated marketing content needs a human gate, and why the answer follows from how reversible the channel is rather than from how good the model has become.

• Does it work in the Salesforce Field Service mobile app?

  Yes. Technicians open Agentforce from the job's Actions and ask in their own words. Review Parts Request is a quick action on the same job.

• Does it protect emergency stock?

  Yes. Every warehouse keeps the reserve you set for each part, and a colleague's van keeps what their own jobs still need.

• Can it stop the wrong part being fitted?

  It only suggests parts on your approved list, and says why when an offered part isn't approved: it could affect the warranty.

• Does it look ahead to the technician's other jobs?

  Yes. If a part is the last one on his van and a later job today needs it, the agent tells him to keep it. It also checks tomorrow's jobs and finds a source for every gap.

• Does anything get requested before the technician approves?

  No. Every request is a draft until he approves it. Then it is created once and goes to the Parts Desk.

• What does the warehouse see?

  A live Parts Desk in Salesforce: requests with source, technician and job, van stock to restock, stock near reserve and tomorrow's pick lists.

• Does it show prices or edit stock?

  No. Costs and suppliers are never shown, and stock counts are never edited by the agent.

• How long does setup take?

  It depends on your Field Service inventory and rules. We scope it with you on a call.