Official recipe

Create a work-order-linked parts request from a technician’s request

A technician needs a part for a specific repair, but a conversational request can omit the exact job, unit or deadline needed by the stock team.

Read original recipe

Proposed inputs

Name
Technician request
Owner
Technician
Minimum scope
One work order and requested part
Quality check
Confirm intended quantity and date.
Name
Catalogue slice
Owner
Stock controller
Minimum scope
Relevant item IDs and units
Quality check
Separate near-identical names.
Name
Work-order lookup
Owner
Dispatcher
Minimum scope
Authorized open jobs only
Quality check
Require a unique exact identifier.

Access and setup — proposed or unknown

Proposed minimum: Start with exported fictional records and a mocked creation response.
Keep parts submission separate from purchase and dispatch authority.
Compatibility unknowns: Unknown: edition entitlement, tenant configuration and transactional rollback.
External actions requiring approval: Persistent access, production record creation, purchasing and shipment release.

Detailed steps and output format

At a glance

Suggested result: A request receipt containing the work order, chosen part, quantity, need-by date and linked line-item identifier.Suggested; untested.
Tool: Salesforce AgentforceSource-named; check current access.
Suggested inputs: Technician request; Catalogue slice; Work-order lookupProposed; access notes below.
Human review: Proposed: technician confirms the resolved part, quantity, due date and exact work order before submission. Purchasing, substitutions, shipment release and credential setup…
Read full note
Proposed: technician confirms the resolved part, quantity, due date and exact work order before submission. Purchasing, substitutions, shipment release and credential setup need separate authority.
Suggested boundaries; source approvals below.
Setup notes: Start with exported fictional records and a mocked creation response. Keep parts submission separate from purchase and dispatch authority.Guide notes; proposed setup untested.
Cost: Workflow cost not established. Check current tool pricing, setup and human review costs before trying it.No measured cost or time added.
Content depth: Source-linked example · suggestions untestedDepth does not establish successful execution.

Check source evidence and limits ↓

Function and scope

Procurement, Operations · Single task

Editorial classification; no execution or compatibility test is implied.

No tool mapping reviewed for this task.

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

A technician needs a part for a specific repair, but a conversational request can omit the exact job, unit or deadline needed by the stock team.

Suggested task · untested

Proposed: clarify the request, resolve exact catalogue and work-order identifiers, and prepare a linked internal parts requisition with reviewable fields.

What you could produce

A request receipt containing the work order, chosen part, quantity, need-by date and linked line-item identifier.

Where these suggestions come from

Core problem: Our suggestion; no result reported by the source
Agent job: Our suggestion; no result reported by the source
Expected output: Our suggestion; no result reported by the source
Relevant job roles: Our suggestion; no result reported by the source
Benefit type: Our suggestion; no result reported by the source

Suggestions and their limits

Describes the proposed purpose and review output; measured benefit and successful delivery are not established.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Before you try it · suggestions untested

Original decision guidance and first check are proposals. The source supports the attributed task; this guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

A short mobile message may use shorthand that a dispatcher understands but a records system cannot safely match. Quiet defaults can turn incomplete requests into misleading commitments.
An agent can ask targeted questions and translate the resolved request into structured fields, giving the technician a compact receipt to check before anyone promises supply.

Why an agent / simpler alternative

Useful judgment: Recognize omitted units, relative dates and ambiguous part descriptions before invoking record creation.
Simpler alternative: Prefer an existing mobile parts-request form or barcode scan when the technician already has exact identifiers.
Unsuitable when: The job requires diagnosing a fault or approving a technically equivalent substitute.

Expected deliverable and review checks

Proposed artifact: Linked requisition receipt.
Critical checks: Header and line belong to the same work order.
Quantity uses the intended unit.
Due date is confirmed rather than silently guessed.
Missing output evidence: Unknown: no executed request from a real organization inspected.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Three fictional technician messages with an ambiguous part, missing date and invalid work-order number.
Acceptance checks: Ask for unresolved fields.
Create no draft for an invalid job.
Link valid draft fields consistently.
Stop conditions: Live Salesforce writes or any supply commitment.

Tasks: Shopping & products

Useful for: Operations manager Service business owner Engineer

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.

Salesforce AgentforceIndependent testing: No

Failure handling, costs and limits

Failure signals and proposed responses

Signal
Several work orders match
Why it matters
A valid request could attach to the wrong repair.
Proposed response
Reject partial matches and request the exact identifier.
Signal
Header exists without its line
Why it matters
A retry may duplicate the request.
Proposed response
Inspect both records before repair or retry.

Effort and cost — unknown

Setup work: Map catalogue IDs, permissions and validation rules.
Ongoing review: Review incomplete requests and date corrections.
Unknowns: Unknown: action-credit costs, setup effort and stock-system integration.

Limits

Editorial guidance only; request creation does not establish stock availability.

Full source evidence

Official recipe · Tool workflows

Original task title: Create a work-order-linked parts request from a technician’s request

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://help.salesforce.com/s/articleView?id=service.fs_einstein_copilot_example_product_order.htm&language=en_US&type=5 ↗

Attributed to: Salesforce Help

Official recipe

Original action type: tool_action
What the source reports: An Agentforce action collects product, quantity, needed date and work-order number, invokes a Flow that creates a Product Request and line item, then returns the request details. The recipe includes record lookup and error-checking instructions.
Source outcome limits: A documented internal product-request record, not a supplier order, inventory reservation, guaranteed need-by date or physical receipt. Date and quantity defaults can change intent; partial work-order matching can select the wrong job.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: No separate pre-submission approval is specified; product and work-order inputs are required.
Named tools: Agentforce agent action; Salesforce Flow; Field Service Product Request and line-item objects.
Model or version: Unknown
Publication date: Unknown
Source last checked: 2026-10-14
Demonstrated in Canada: Unknown
Canadian availability: Unknown
Proposed Canadian adaptation: Proposed: confirm the technician’s local dates, catalogue units, work-order identifiers and authorized service territory. Canadian edition availability and actual execution are unverified.
Recommended approval boundaries: Proposed: technician confirms the resolved part, quantity, due date and exact work order before submission. Purchasing, substitutions, shipment release and credential setup need separate authority.