Escalation Overview
Escalation rules automatically promote claims up the chain when needed.When to Escalate
- Claim approaching SLA deadline
- No one assigned after X hours
- Critical priority not addressed
- Safety concern requires executive review
- Cross-department issue needs coordination
Creating Escalation Rules
- Admin Console → Escalation Rules
- Click “Add Rule”
- Set trigger conditions:
- Priority = Critical
- Category = Safety
- Open > 2 hours without assignment
- Set escalation action:
- Escalate to manager
- Escalate to director
- Notify department head
- Save and test
Common Escalation Scenarios
Scenario 1: Unassigned Critical Claims
Rule:- Trigger: Priority = Critical AND no assignment after 1 hour
- Action: Escalate to Department Manager
Scenario 2: SLA At-Risk Claims
Rule:- Trigger: SLA status = At-Risk (2 hours before deadline)
- Action: Notify assignee + add to manager dashboard
Scenario 3: Safety Claims
Rule:- Trigger: Category = Safety AND Priority = High
- Action:
- Auto-escalate to Safety Manager
- Email Safety Officer
- Copy Executive Director
Scenario 4: Cross-Department Issues
Rule:- Trigger: Comments mention multiple departments
- Action: Escalate to Operations Director
Escalation Chain
Define multi-level escalation:Managing Escalations
Preventing Escalations
Better to prevent than escalate:- More resources upfront
- Clear procedures
- Better training
- Process improvements
Responding to Escalations
When escalated:- Drop what you’re doing
- Prioritize over routine work
- Get help if needed
- Update status frequently
- Report resolution quickly
Monitoring Escalations
Dashboard shows:- How many escalations per week
- Which rules trigger most
- Escalation success rate
- Patterns in escalations
- Insufficient resources
- Process issues
- Unclear procedures
- Need for training