Evidence the run may read
- Submitted lead data
- Approved ideal-customer profile
- Territory and routing rules
production blueprint · sales & revenue operations
Inbound lead qualification agent blueprint.
Normalize an inbound request, compare it with an approved fit model, and prepare a routed qualification brief.
Search intent: AI agent for inbound lead qualification
Published by a2a cloudProduct-source methodology →
01 · the contract
Start from a bounded job, not a blank chat box.
trigger
A new inbound lead or contact request is created.
owner
sales owner
agent stops at
Revenue operations approves routing and a seller approves outreach.
KPI · decrease
qualified lead response time (minutes). Measure complete inbound request to accepted owner assignment.
outputs
Artifacts the run must produce
- Fit and completeness assessment
- Research questions
- Routing recommendation
02 · topology
Small specialists. Named handoffs. One accountable decision.
Each stage produces an artifact another stage can inspect. The final node is a person, not an autonomous write to an external system.
- 01
intake
Validate and normalize the inbound lead qualification inputs.
- 02
lead normalizer
Produce the fit and completeness assessment.
- 03
fit researcher
Produce the research questions.
- 04
revenue operations reviewer
Challenge the inbound lead qualification result and prepare an approval packet.
- 05
sales owner
Revenue operations approves routing and a seller approves outreach.
intake→ validated input packet →lead-normalizer
lead-normalizer→ Fit and completeness assessment →fit-researcher
fit-researcher→ Research questions →revenue-operations-reviewer
revenue-operations-reviewer→ approval packet with evidence references →human-approver
03 · authority
Grant the run only what this case needs.
Source material is read-only. Drafts land in a case-specific output path. Tools may read or propose; the human gate owns the external write.
case inputs
workspace/sales/inbound-lead-qualification/inputs/**Read only the evidence attached to this workflow instance.
case outputs
workspace/sales/inbound-lead-qualification/outputs/**Write drafts and evidence artifacts without modifying source records.
approved tools
sales:inbound-lead-qualification:read-or-proposeInvoke only tools explicitly granted for this run; external writes remain gated.
04 · implementation
A private, bounded starting manifest.
The blueprint starts private, caps its DAG, disables replanning, and exposes no public endpoint. Add only the tools and data adapters this workflow has approved.
a2a.yamlsafe starting point
name: sales-inbound-lead-qualification
version: 0.1.0
entrypoint: agent:BlueprintAgent
expose:
public: false
composition:
planning: deterministic_dag
max_nodes: 6
max_parallel: 1
max_replans: 005 · acceptance test
Pass only with evidence.
- 01
Evidence traceability
Every material conclusion cites an input artifact or a scoped tool result from this run.
- 02
Qualification cites submitted or approved research evidence and does not infer protected traits.
Qualification cites submitted or approved research evidence and does not infer protected traits.
- 03
Approval boundary
The run stops at a proposal and records the human decision before any external side effect.
failure containment
Stop small. Preserve the evidence.
Identity, company, consent, or territory data is too ambiguous for reliable routing.
Containment: Return a partial result with unresolved items; do not broaden scope or perform an external write.
Operator: Attach the missing evidence, narrow the brief, or explicitly approve a new scoped run.
A required input or tool grant is unavailable.
Containment: Stop the affected branch and preserve completed artifacts in the case output workspace.
Operator: Grant only the missing resource or continue with that branch marked out of scope.
06 · proof
Sign the run facts. Keep money in the billing ledger.
Current platform receipts sign caller identity or classification, skill, bounded input evidence, verified grant IDs when present, outcome or result preview, and timing. Optional file, tool, artifact, handoff, evaluation, and review fields require separate instrumentation and are not populated by default. Price, fees, payouts, and later human approvals remain separate platform records.
The example uses only fields populated by the current platform sealing paths. It is illustrative, not a record of a real customer run.
ExecutionReceipt · selected fieldsEd25519 token
{
"receipt_id": "rcpt_01J...",
"schema_version": 1,
"agent_name": "sales-inbound-lead-qualification",
"caller": "user:workflow-owner",
"task_id": "case_inbound_lead_qualification",
"skill_name": "inbound_lead_qualification",
"input_hash": "4d7c...9a2f",
"grant_ids": [
"grt_case_inputs",
"grt_tool_propose"
],
"status": "ok",
"result_preview": "Output prepared: Fit and completeness assessment. Human decision remains separate.",
"elapsed_ms": 4218
}related blueprints
Keep the operating model consistent.
Sales & Revenue Operations
Account research brief
Turn approved public and internal account evidence into a sourced, time-stamped briefing for a seller.
Sales & Revenue Operations
Sales meeting preparation
Assemble approved account, opportunity, and prior-interaction evidence into an agenda and decision-oriented prep packet.
Sales & Revenue Operations
CRM hygiene review
Identify incomplete, stale, and contradictory opportunity fields and prepare proposed corrections for the record owner.
put the pattern to work
Start private. Scope the authority. Require the decision.
Deploy the workflow as a bounded internal agent, verify its outputs and the receipt fields actually emitted, then expand only the scopes your acceptance test proves it needs.