Sales · Speed to lead
Lead qualification and routing
Turn new leads and configured intent signals into enriched routing proposals and outreach drafts, while reps and managers control first touch and named-account routing.
Illustrative product view
run_lead_routing_01
A form, webhook, or configured external intent event starts the workflow.
Trigger captured
Account context is enriched
Evidence attached
Fit and ownership are proposed
Evidence attached
Human decision required
Terminal approval step
The operating problem
Where the process breaks.
New leads arrive with incomplete context and wait while teams research fit, ownership, and intent. Blind automation can move faster but risks poor assignments and unreviewed outreach to sensitive accounts.
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
Lead enters the queue
A form, CRM event, or permitted intent signal starts the workflow.
- 02Agent
Account context is enriched
The agent retrieves approved firmographic, CRM, territory, and engagement data.
- 03Agent
Fit and ownership are proposed
The workflow explains its score, selects a routing rule, and drafts a context-aware first touch.
- 04Human
Owner reviews the decision
The rep approves outreach; a manager approves named-account or exception routing as the terminal workflow 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
The assigned rep approves first touch, and a manager approves named-account or exception routing; writes require a separate 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_lead_routing_01
- Lead source and trigger payload
- captured · evidence_01
- Enrichment sources and normalized fields
- captured · evidence_02
- Scoring rationale and routing rule
- captured · evidence_03
- Rep or manager approval decision
- captured · evidence_04
- Human decision and continuation status
- approved · continuation_not_started
Output · An enriched lead, explained owner proposal, outreach draft, and human decision 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.
Routing rules are deterministic and visible alongside model reasoning.
Named-account changes require manager approval and a separate continuation.
First-touch messages cannot send in the approval run.
Enrichment tools receive only the fields permitted for that step.
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.