Blocked Employment Movements
Operational process at alan-health where incoming employment data that cannot be automatically processed due to inconsistencies requires manual investigation and resolution. Serves as the first successful use case for alan-ai-agents-platform, achieving 70% processing rate and 94% accuracy, serving as proof-of-concept for enterprise AI agent deployment.
Process Definition
Data Flow Context
When new employment data arrives from multiple sources:
- HR admin invitations: Manual company administrator entries
- Bulk imports: Large-scale employee data uploads
- System integrations: Automated feeds from HR systems
Blocking Conditions
Employment movements become "blocked" when automatic processing fails due to:
- Partial matches: Email and names match existing users but social security numbers differ
- Data inconsistencies: Conflicting information across data sources
- Ambiguous identities: Multiple possible matches for single employment record
- Missing information: Required fields absent or incomplete
Manual Resolution Process
Traditional operator workflow involves:
- Case review: Examine blocked movement details in internal tool
- Scenario identification: Determine which type of inconsistency applies
- Data investigation: Check existing user profiles and employment history
- External communication: Contact HR admins when clarification needed
- Record updates: Modify database records to resolve inconsistencies
- Status management: Update movement status to processed or escalated
AI Agent Implementation
Agent Capabilities
alan-ai-agents-platform deployment includes:
- 15 tools: Mirror complete operator workflow capabilities
- Conversational interface: Multi-turn interaction embedded in existing tool
- Reasoning: Natural language processing of complex scenarios
- Decision making: Automated resolution of standard cases
Tool Categories
- Read-only tools: User profile fetching, data comparison, history review
- Write tools with approval: Email sending to external admins, record updates
- Status management: Blocked movement resolution and escalation
Permission Framework
- Automatic execution: Read-only data gathering tools
- Human-in-the-loop: Write operations require operator approval
- Application-layer validation: Cannot bypass security regardless of LLM behavior
Production Results
Automation Metrics
- 70% processing rate: Agent handles majority of blocked movements
- 25% full automation: End-to-end resolution without human intervention
- 94% accuracy: Weekly tracking with expert operator annotations
- 15 tools implemented: Comprehensive workflow coverage
Performance Characteristics
- Complex reasoning: Handles edge cases like compound names ("Marie Marceau-Dupont" vs "Marie Dupont")
- Fuzzy matching: Natural language approach to data comparison vs exhaustive rules
- Context awareness: Considers full employment history and company relationships
- Escalation capability: Routes unsolvable cases to human queues
Strategic Significance
Platform Validation
Chosen as first use case due to:
- Well-defined process: Clear procedural documentation and success criteria
- Structured outcomes: Database record modifications with measurable accuracy
- Manageable scope: Contained workflow suitable for initial development
- Business impact: Significant manual effort reduction opportunity
Learning Outcomes
Provided key insights for platform development:
- Tool permission patterns: Application-layer security more reliable than LLM self-policing
- Conversational superiority: Multi-turn interaction more flexible than single-turn structured output
- Integration importance: Embedded UI better than standalone tools
- Configuration management: git-based-configuration enables operations team ownership
Scaling Foundation
Success enabled platform expansion to:
- belgium-claims-processing: Geographic and domain validation
- Sales AI agents: Different department deployment
- Reusable components: Generic infrastructure for rapid deployment
Technical Implementation Details
Integration Architecture
- Embedded interface: Chat panel within existing blocked movements tool
- Real-time updates: Agent actions immediately reflected in operator interface
- Task orchestration: Integration with existing queue management systems
- Escalation workflow: Seamless handoff when agent cannot resolve case
Configuration Management
- Git-based prompts: Operations team can modify agent behavior
- Branch testing: Safe iteration on agent configuration in staging
- Evaluation datasets: Test cases stored alongside configuration
- Performance tracking: Metrics correlation with configuration changes
Example Resolution Flow
- Case ingestion: Agent receives blocked movement details
- Scenario analysis: Determines partial match with existing user
- Data gathering: Fetches user profiles and employment history
- Tool execution: Compares names allowing for variation patterns
- Resolution decision: Determines safe automatic merge or escalation needed
- Action execution: Updates records with operator approval if required
- Status update: Marks case as resolved or escalated
Lessons Learned
Successful Patterns
- Reasoning over rules: LLM handles unanticipated variations better than exhaustive branching
- Permission-based security: Application layer enforcement more reliable than prompt-based restrictions
- Embedded deployment: Integration within existing workflows reduces adoption friction
- Iterative configuration: Operations team ownership enables continuous improvement
Implementation Challenges
- Compound name handling: Required specific prompt instruction for name variations
- Performance tracking: Weekly annotation overhead for accuracy measurement
- Team transition: UX challenges when empowering operations teams with Git workflows
- Tool complexity: 15 tools required for comprehensive workflow coverage
This case study represents one of the most successful documented implementations of AI agents for enterprise operational processes, providing practical patterns for automated decision-making with appropriate human oversight.
See also
- alan-ai-agents-platform - Platform and architecture context
- david-merkle - Platform architect and implementation lead
- git-based-configuration - Configuration management approach
- tool-permission-systems - Security framework
- belgium-claims-processing - Follow-up validation use case
- operations-team-autonomy - Team empowerment philosophy