Profile Overview
Pendingmessy_crm_export.csv · Lead routing · analyzed Aug 2, 2026, 12:05 PM
routing readiness
Not ready for routing - 7 issue types unresolved
Prepare records for owner assignment, SLA routing, and rep handoff. Weighted by active workflow impact, ambiguity, and whether a fix can apply without business context.
Dataset summary
- Rows
- 79
- Columns
- 10
- Issue types
- 7
- Findings
- 116
Active workflow mode
Lead routing
75 unresolved impact signals
Records without owners, standard territory fields, or valid segments can fall out of routing.
Issue Count By Category
Record-level findingsDownstream Impact Simulator
RoutingWould fail routing
Records need a valid owner or explicit review assignment before rep routing.
May route to wrong territory
Territory filters depend on standardized state values.
Need queue triage
Segment gaps can bypass route-to-team logic.
Reference Context
Optional structured sources currently grounding recommendation basis and confidence.
Ownership rules
region / territory / segment / owner
real_ownership_rules_from_cleaned.csv
51 parsed rows
Inspect-only derived patterns. Disabled by default unless a single-owner pattern is consistent.
Segment dictionary
segment / allowed_values / definition / lifecycle_stage
real_segment_dictionary_from_cleaned.csv
3 parsed rows
Validates allowed segment taxonomy from the real cleaned export.
Clean CRM reference export
account / state / country / segment / owner / territory
real_clean_crm_reference_from_cleaned.csv
56 parsed rows
Primary trusted source for owner, segment, and state recommendations.
Top Issues By Business Risk
Ranked by workflow impact and fix ambiguity — not record count.
Prioritization Logic
1. Routing blockers first
Issue order changes based on the selected workflow mode, so the highest business risk appears first.
2. Review-first suggestions remain visible
Missing owner, segment, state, and lifecycle recommendations show confidence and rationale before approval.
3. Deterministic cleanup is still traceable
Lower-risk changes stay transparent, reversible, and logged with the same approval trail.