Sales · Pipeline inspection
Pipeline review and sales roundup
Turn pipeline changes and account activity into a ranked forecast review, while the sales manager controls forecast overrides and save plays.
Illustrative product view
run_sales_roundup_01
A scheduled pipeline review begins or a material deal signal changes.
Trigger captured
Pipeline evidence is gathered
Evidence attached
Risk and change are explained
Evidence attached
Human decision required
Terminal approval step
The operating problem
Where the process breaks.
Pipeline reviews depend on stale fields and manual rollups, so material deal changes surface late. Managers need evidence behind risk signals before changing a forecast or directing account action.
Governed execution
How the work runs.
Order remains explicit from trigger to decision. Every step runs inside the tools, data scope, and policy assigned to this workflow.
- 01Trigger
Review window opens
A schedule or material opportunity change starts the governed review.
- 02Agent
Pipeline evidence is gathered
The agent reads permitted opportunity fields, activity history, next steps, and recent communications.
- 03Agent
Risk and change are explained
Deals are ranked with evidence-linked reasons, missing information, and a proposed save play.
- 04Human
Manager confirms intervention
The manager approves or overrides forecast changes and any account-level intervention as the terminal step.
Decision boundary
Human approval is the boundary.
The approval node is terminal today. A post-approval send or write happens only through a separate manual or newly triggered continuation.
Required decision
A sales manager confirms every forecast override and account intervention; CRM writes require a separate manual or newly triggered continuation.
Approval recorded
Actor, decision, edits, and timestamp join the receipt.
Separate continuation
External write
Nothing resumes silently after the human decision.
Proof of execution
Execution receipt.
The output is not just a result. It carries the trigger, evidence, proposed actions, decision, and final workflow state.
Illustrative receipt
sample · run_sales_roundup_01
- Review trigger and opportunity set
- captured · evidence_01
- Evidence used for each risk signal
- captured · evidence_02
- Proposed forecast and action changes
- captured · evidence_03
- Manager decisions and overrides
- captured · evidence_04
- Manager decision and continuation status
- approved · continuation_not_started
Output · A ranked risk digest, proposed forecast updates, manager decisions, and receipt.
Connected work
Example systems in this workflow
These are illustrative system choices, not a claim that every one is a native connector. Configure supported native tools, MCP servers, OpenAPI imports, or approved HTTP tools for your environment.
Deployment boundary
Run the workflow in Zilionix Cloud, inside your VPC, or through the self-hosted deployment path while keeping organization-scoped data and credentials inside the selected boundary.
Zilionix Cloud
Your VPC
Self-hosted
Policy before autonomy
Guardrails for this run.
Risk signals cite the activity and field evidence used.
Forecast changes cannot commit in the approval run; a separate continuation is required.
Account access follows organization and workspace permissions.
Every override remains visible in the audit history.
External evidence
Benchmark the opportunity.
This source illustrates the surrounding business problem. It is not a Zilionix deployment, customer result, or performance guarantee.
Bring this workflow into view.
Map the trigger, tools, approval boundary, and execution receipt against the way your team already works.