Lead Qualification and Routing Workflow: A Copyable Template
Automatic routing is useful only when every decision can be explained from evidence the buyer supplied. “Sounds like a good lead” is not a rule. A strong workflow records the signal, applies a visible condition, sends the lead to one accountable destination, and proves that destination accepted it.
This template is product-neutral. It does not claim a native Easy AI or CRM integration. Copy the contract below into a blank document, complete it with the sales and operations owners, then test one labeled event in systems your team has verified.
Copy the workflow worksheet
Workflow name: Qualify and route inbound leads
Trigger: New eligible conversation or form event
Entry requirements: Permission, contact route, source, timestamp, no duplicate active record
Qualification dimensions: Fit / stated need / timing / requested next step
Decision outputs: Sales-ready / nurture / disqualified / human review
Routing key: Territory / product / language / capacity / named account
Destination owner and backup:
Acceptance event and target:
Stop and rollback conditions:
event_id:
source_event_at and timezone:
contact_permission and source:
buyer_goal in the buyer's words:
qualification_evidence (field/value/source/rule version):
qualification_outcome:
qualification_reason (rule IDs):
routing_key used by the system:
assigned_owner and acceptance_state:
next_step_requested:
workflow_version:
Do not launch until the sales and operations owners can fill every line. OpenAI and Anthropic both emphasize bounded workflows, explicit tools/guardrails, and human intervention instead of adding autonomy by default. Review OpenAI's guide and Anthropic's engineering guidance.
Define the decisions before the questions
| Outcome | Required evidence | Destination | Prohibited shortcut |
|---|---|---|---|
| Sales-ready | Declared need, fit rule met, requested sales next step | One named rep or queue | Inferring budget, authority or urgency |
| Nurture | Relevant need but timing or next step is not sales-ready | Approved nurture owner | Treating silence as consent |
| Disqualified | Explicit exclusion rule with recorded reason | Closed state or permitted alternative | Using protected or irrelevant traits |
| Human review | Contradictory, high-value, sensitive or unsupported request | Monitored review queue | Letting the model resolve uncertainty silently |
Salesforce's lead-qualification overview describes qualification as evaluating fit and buying signals before progressing a lead. Use that principle, but make your own criteria explicit and reviewable. Read the source.
Build a rule table
Replace the placeholders with rules your revenue owner approves. A blank condition is safer than a guessed one.
| Rule ID | Evidence field | Condition | Outcome |
|---|---|---|---|
| Q1 | Stated business need | Matches an approved problem area | Continue |
| Q2 | Requested next step | Explicitly asks for sales contact | Sales-ready candidate |
| Q3 | Timing | Buyer states a period the team supports | Add timing label |
| Q4 | Exclusion | Meets an approved exclusion condition | Disqualified |
| R1 | Named account | Exact verified account match | Sales-ready |
| R2 | Language and capacity | Supported language and open queue | Sales-ready |
| Rule ID | Route | On missing or conflict |
|---|---|---|
| Q1 | — | Ask one clarification |
| Q2 | Apply routing rules | Human review if identity/contact is incomplete |
| Q3 | — | Record not stated; never infer |
| Q4 | Closed-state owner | Human review when evidence conflicts |
| R1 | Named-account owner | Operations review on duplicate ownership |
| R2 | Eligible queue | Backup queue; never drop the event |
The table separates qualification from assignment. A lead can be sales-ready while routing is temporarily unresolved; preserve that state instead of changing the qualification result.
When you map the worksheet to CRM fields, keep the field names inside the copyable artifact as the system-facing version of the plain-language lines above—not as a second worksheet. event_id identifies a retry safely; source_event_at keeps the original time; contact_permission records whether contact is allowed and where that decision came from. qualification_evidence, qualification_outcome and qualification_reason preserve what the buyer said, the result and the rules that produced it. routing_key, assigned_owner and acceptance_state then show where the lead went and whether someone received it. On correction, append a new decision event instead of erasing the old one.
Execution sequence
- Validate entry requirements and deduplicate the event.
- Capture only fields that change an approved decision.
- Evaluate rules in a fixed order and expose missing/conflicting evidence.
- Write the qualification outcome and reason atomically where possible.
- Resolve the routing key against current ownership and capacity.
- Send the structured sales handoff.
- Wait for an acceptance event; use the backup route on rejection or timeout.
- Reconcile the final owner and next step, then measure from event records.
Completed fictional run
Fictional company Northstar receives event E-1042 from Linh, Operations Director at a 40-person services company. Linh states a need to route website inquiries, supports English and Vietnamese, and requests a discovery call this month. Rules Q1, Q2 and Q3 pass. No exclusion applies. R1 finds no named account; R2 selects the bilingual inbound queue, whose owner accepts in six minutes. This fills the same canonical artifact used above.
Workflow name: Qualify and route Northstar inbound service leads
Trigger: New eligible website conversation
Entry requirements: Permission=yes; contact route=email; source=website; timestamp present; duplicate check=clear
Qualification dimensions: Fit / stated need / timing / requested next step
Decision outputs: Sales-ready / nurture / disqualified / human review
Routing key: Vietnam / service automation / en+vi / open queue / no named account
Destination owner and backup: bilingual-inbound-queue / revenue-operations-review
Acceptance event and target: queue.accepted within Northstar's 15-minute internal target
Stop and rollback conditions: Stop on missing permission, conflicting identity or failed CRM write; withdraw assignment and route to operations review
event_id: E-1042
source_event_at and timezone: 2026-08-16 10:00 ICT
contact_permission and source: yes; explicit website request
buyer_goal: Route website inquiries to the correct service team
qualification_evidence: Q1=approved problem/message-3/v2026-08-16-a; Q2=discovery call/message-5/v2026-08-16-a; Q3=this month/message-5/v2026-08-16-a
qualification_outcome: sales-ready
qualification_reason (rule IDs): Q1,Q2,Q3,R2
routing_key used by the system: language=en+vi; territory=Vietnam; named_account=false
assigned_owner and acceptance_state: bilingual-inbound-queue; accepted at 10:06 ICT
next_step_requested: discovery call
workflow_version: 2026-08-16-a
The run proves only that the fictional rules executed as designed. It does not prove lead quality, conversion, or product performance.
Exceptions, QA, and measurement
| Failure | Immediate response | Recovery owner |
|---|---|---|
| Duplicate or replayed trigger | Suppress a second record; link the replay | Operations |
| Conflicting qualification evidence | Set human-review; preserve both values |
Sales owner |
| Owner unavailable or rejects | Route once to the declared backup | Routing owner |
| CRM write succeeds but notification fails | Keep pending state; retry notification safely | Systems owner |
| Permission withdrawn | Stop outreach and apply the approved suppression process | Privacy owner |
Before expansion, sample decisions and recalculate them from stored evidence. Track accepted handoffs, unresolved routing, duplicate suppression, time to acceptance, corrections, and downstream dispositions. Do not call a routing rate a revenue result.
Frequently asked questions
These questions cover common edge cases after the rules and ownership are already defined.
Should every lead receive a numeric score? No. Explicit rule outcomes can be easier to audit. Use a score only when its weights, thresholds and interpretation have accountable owners.
What if a qualified lead has no available owner? Preserve the outcome, keep acceptance pending, invoke the declared backup and keep the event visible. Do not silently downgrade or drop it.
Can the workflow infer missing budget or urgency? No. Record not stated, ask an approved clarification when useful, or route to human review.
Next steps and limits
Continue the workflow. Use the revenue-team readiness assessment before rollout and the sales handoff template for the payload delivered to a rep.
Evidence boundary. The example and thresholds are instructional, not benchmarks. This draft claims no Easy AI feature, integration, qualification accuracy, response-time improvement, or revenue outcome.