Aeion Blueprint for CRM Lead Routing
The work of CRM isn't entering a lead — it's deciding what happens next. Qualification (does this lead match ICP?), routing (which rep gets it?), follow-up (when + how?), nurture (if non-converted, what sequence?). Most teams cobble this together from Zapier + Outreach + manual spreadsheets. Blueprint generates the full pipeline from a natural-language brief, then lets ops refine it in the visual editor — and re-runs against the CRM data already in Aeion.
The Lead-Routing Problem
A typical inbound lead arrives from a marketing site, gated demo request, or partner referral. The work of converting that lead into pipeline is multi-step and constraint-heavy:
The AI-Generated Workflow Walkthrough
`
Real Lead-Routing Patterns
`
Refinement + Iteration
`
Tying Into Existing Sales Stack
`
FAQ
Those are tightly coupled to their respective CRMs. Blueprint is module-agnostic — works on Aeion CRM, can also dispatch to Salesforce/HubSpot via Singularity. Plus AI generation from prompts is unique.
Confidence score guides this. High-confidence (0.85+): typically production-ready with minor review. Medium (0.6-0.84): production with manual validation of edge cases. Low (<0.6): regenerate with a refined prompt.
Blueprint can integrate via Singularity (Salesforce, HubSpot, Pipedrive native connectors). Triggers + actions for external CRMs via webhook. Best experience is on Aeion CRM; external CRM is a fully-supported alternative.
Yes — deduplication node in the workflow. Track last_notified_at per lead; skip if recent. Common pattern.
Workflows scoped to tenant. Cross-tenant operations require explicit tenant_id parameter + super-admin role.
Yes — split node in workflow. Random assignment to variant A or B; measure conversion per variant.
Typical: 200-500ms (event → workflow trigger → first action). For enrichment-heavy workflows: 2-10 seconds. Async execution; doesn't block lead creation.
Workflows can check rep.available status. If unavailable: backup rep, manager, or queue.
Yes — governance policy can require approval before a workflow is allowed to execute, and workflows can branch to a manual-review step (e.g., create a task) for a human to action. Pending approvals surface in the admin's Pending Approvals queue.
Workflow execution: free. Per-workflow AI inference: per-token via AI provider gateway with cost caps. Typical: $20-100/month for mid-volume lead-routing workflow.
GDPR-aware. Per-lead consent tracked; opt-out respected. Data retention per tenant policy.