Workflow Example — Lead Routing & Sales Ops
Sales Operations
intake → normalization → routing → SLA enforcement → exceptions → handoff
deterministic routing policy, enforceable timing, auditable handoffs
What This Workflow Demonstrates
This example shows how to design a lead routing workflow that is:
- consistent (routing rules are explicit)
- fast (automatic assignment and follow-up enforcement)
- resilient to messy inbound lead data
- governed with human review for edge cases and high-value leads
Example Workflow Structure (Steps + Actors)
Actors
- System Actor: intake normalization, routing, timers
- CRM Actor: create/update lead records
- AI Actor: enrichment and summarization under guardrails
- Sales Ops / Manager: exception review and overrides
- SDR / AE: lead owners and follow-up executors
Steps
Ingest inbound lead Accept from web forms, email, partner referrals, or imports.
Normalize and validate fields Standardize company, region, email domain, and required fields.
Deduplicate Match against existing CRM records and apply merge rules.
Enrich lead (AI-assisted where safe) Enrich firmographics and produce a short summary for the rep.
Apply routing rules Route by territory, segment, and explicit policy (including round-robin where applicable).
Start SLA timer Track time-to-first-touch based on policy.
Reminder and escalation If SLA is missed:
- notify owner
- escalate to manager
- optionally re-route based on capacity rules
Exception handling (human review) Route edge cases for Sales Ops / Manager review:
- ambiguous territory
- high-value lead
- missing critical fields
Handoff checkpoint When moving SDR → AE, require required fields/notes and log the transition.
Audit logging Record routing logic used, ownership changes, timestamps, and exceptions.
Human-in-the-Loop Checkpoints
Humans remain responsible for:
- policy exceptions and overrides
- high-value lead handling
- final decisions on ambiguous routing
AI Guardrails (Recommended)
AI can assist with:
- enrichment
- summarization
- classification
AI should not:
- assign ownership without policy logic
- change routing rules
- override exceptions without human review