Official recipe

Convert selected manufacturing forecasts into sales opportunities

An account manager has approved component demand forecasts, but turning them into usable pipeline records can lose product, period or account lineage.

Read original recipe

Proposed inputs

Name
Forecast snapshot
Owner
Planning analyst
Minimum scope
Selected fact IDs, dimensions, periods and quantities
Quality check
Check snapshot version and duplicate keys.
Name
Destination specification
Owner
Account owner
Minimum scope
Exact account and new/existing opportunity
Quality check
Verify ownership and intended close date.
Name
Mapping rules
Owner
Sales administrator
Minimum scope
Product, unit, currency and period mappings
Quality check
Require explicit handling of missing values.

Access and setup — proposed or unknown

Proposed minimum: Use fictional facts and a local mock destination.
Preserve a lineage map for every proposed line and schedule entry.
Compatibility unknowns: Unknown: tenant template availability and whether account automations react to opportunity creation.
External actions requiring approval: Live record creation, integration setup and any resulting outreach or commitments.

Detailed steps and output format

At a glance

Suggested result: A forecast-to-opportunity mapping packet with selected fact IDs, grouping rationale, period totals and unresolved exceptions.Suggested; untested.
Tool: Salesforce AgentforceSource-named; check current access.
Suggested inputs: Forecast snapshot; Destination specification; Mapping rulesProposed; access notes below.
Human review: Proposed: approve exact selected facts, grouping, account, destination and period mappings before any write. Do not infer a customer commitment or permit downstream sales…
Read full note
Proposed: approve exact selected facts, grouping, account, destination and period mappings before any write. Do not infer a customer commitment or permit downstream sales outreach from forecast conversion alone.
Suggested boundaries; source approvals below.
Setup notes: Use fictional facts and a local mock destination. Preserve a lineage map for every proposed line and schedule entry.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 ↓

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

The problem

An account manager has approved component demand forecasts, but turning them into usable pipeline records can lose product, period or account lineage.

Suggested task · untested

Proposed: prepare a traceable conversion plan and reconcile its intended pipeline representation.

What you could produce

A forecast-to-opportunity mapping packet with selected fact IDs, grouping rationale, period totals and unresolved exceptions.

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

Forecast rows can describe the same component across different variants and periods. Combining them casually can double-count quantities or obscure which program created them.
An agent can help choose a grouping and explain mappings, while arithmetic and duplicate checks verify the resulting representation.

Why an agent / simpler alternative

Useful judgment: Clarify selection, grouping and intended destination from business language.
Simpler alternative: Use a validated transformation template when filters and mappings are stable.
Unsuitable when: The forecast is unapproved, account identity is ambiguous, or conversion would trigger unapproved downstream actions.

Expected deliverable and review checks

Proposed artifact: A forecast-to-opportunity mapping packet with selected fact IDs, grouping rationale, period totals and unresolved exceptions.
Critical checks: Selected facts appear exactly once.
Grouped period totals equal the source totals.
Account, product, currency and units remain consistent.
Missing output evidence: Unknown: no actual account output or successful run independently inspected.

First check — proposed, unexecuted

Status: proposed_unexecuted
Synthetic fixture: Offline eight fictional forecast facts across two components, two variants and two periods, plus one duplicate and one missing account reference.
Acceptance checks: Produce a complete lineage table for each grouping.
Reconcile quantities by period.
Duplicate and missing-account rows remain blocked.
Stop conditions: Live CRM access, implicit customer commitment, unapproved pricing or external messages.

Tasks: Sales & outreach

Useful for: Sales professional Data analyst

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
Duplicate facts or repeated conversion
Why it matters
Pipeline can be overstated.
Proposed response
Compare source IDs with prior conversion receipts.
Signal
Grouping hides different variants
Why it matters
Reviewers lose meaningful distinctions.
Proposed response
Show both candidate groupings and obtain an owner choice.
Signal
Unexpected pricing or account resolution
Why it matters
A technically valid record may misstate the opportunity.
Proposed response
Hold the conversion until explicit mappings are supplied.

Effort and cost — unknown

Setup work: Map dimensions, product references and period boundaries.
Ongoing review: Review exceptions and reconcile repeat conversions.
Unknowns: Unknown: licensing, usage charges and downstream automation effort.

Limits

Proposed design only; it does not validate demand, probability of sale or revenue recognition.

Full source evidence

Official recipe · Tool workflows

Original task title: Convert selected manufacturing forecasts into sales opportunities

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=ind.mfg_gen_ai_agentforce_forecast_to_opportunity_topic.htm&language=en_US&type=5 ↗

Attributed to: Salesforce Help

Supporting source context

Project documentation supporting the linked recipe’s scope, permissions and limits. These references do not establish an independent test or add counted jobs.

Official recipe

Original action type: tool_action
What the source reports: Filters manufacturing component forecasts, displays up to 50 records, asks for grouping and a new or existing opportunity, resolves the program account and converts selected forecasts.
Source outcome limits: Opportunity records and schedules represent forecast inputs, not orders, accepted demand or realized revenue. No conversion output was inspected. Requires Program Based Business. Context mappings and product schedules are prerequisites; ambiguous or absent product price books default to the standard price book. Eligible edition and Agentforce for Manufacturing entitlement required. Sales Planning locale support is unresolved because the locale paragraph names another product; the linked agent-creation page was unavailable, so that setup path is unverified.
Evidence attribution caveat: This official recipe describes a procedure; it does not prove successful execution or independently reproduced results.
Source approval description: User chooses grouping and destination and supplies new-opportunity name and close date. A separate final approval gate is unspecified.
Named tools: Program Forecasts to Opportunities subagent; Manufacturing Cloud.
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 currency, fiscal periods, product units and the owner-approved account. Canadian execution and current account-specific eligibility remain unknown.
Recommended approval boundaries: Proposed: approve exact selected facts, grouping, account, destination and period mappings before any write. Do not infer a customer commitment or permit downstream sales outreach from forecast conversion alone.