Priority Routing Module Documentation
Table of Contents
- Module Overview (Technical)
- Module Overview (Commercial/Business)
- Module Overview (End User/Administrator)
- Configuration Fields Reference
- Common Scenarios & Examples
- Limitations & Important Notes
- Troubleshooting Tips
- Glossary
---
1. Module Overview (Technical)
What Is Priority Routing?
Priority Routing allows administrators to define named routing rules with priority scores. These rules route calls to specific destinations and can be referenced by other modules like queues or VIP lists to give certain callers higher queue position scores.
Architecture
Key Tables
| Table | Purpose |
|---|---|
public.priority_routing | Priority rule definitions |
Key Files
| File | Description | |
|---|---|---|
admin/apps/web/src/modules/priorityRouting/ | Frontend module | |
admin/apps/web/src/i18n/en/priorityRouting.json | Translations |
Integration Points
Priority Routing rules can be referenced by:
- VIP Lists → Assign priority to matching callers
- Queue Profiles → Route to priority-specific destinations
- Routing Engine → Select destination based on priority
---
2. Module Overview (Commercial/Business)
Business Value
Priority Routing enables differentiated service levels:
| Without Priority Routing | With Priority Routing | |
|---|---|---|
| All callers equal | VIP callers prioritized | |
| No service tiers | Named priority tiers | |
| Manual escalation | Automatic routing | |
| No tracking | Named rules for reports |
Use Cases
- VIP Customer Handling
- Route directly to senior agents
- Service Tier Management
- Different queue destinations per tier
- Partner Program
- Dedicated support queues
- Account-Based Routing
- SMB accounts to SMB queue
Feature Highlights
| Feature | Benefit | |
|---|---|---|
| Priority Score (0-10) | 10 levels of prioritization | |
| Named Rules | Easy identification | |
| Module/Destination | Route to any PBX destination | |
| Enable/Disable | Quick activation toggle |
3. Module Overview (End User/Administrator)
What Can You Do?
- Create named priority routing rules
- Set priority scores (0-10, 10 = highest)
- Configure destination module/target
- Enable/disable rules
Administrator Workflow
Priority Visual Scale
| Score | Color | Level | |
|---|---|---|---|
| 8-10 | 🔴 Red | Critical/VIP | |
| 5-7 | 🟡 Yellow | Important | |
| 0-4 | 🟢 Green | Standard |
Quick Tips
---
4. Configuration Fields Reference
Priority Routing Fields
| Field | Description | Example | Required | |
|---|---|---|---|---|
| Name | Rule identifier | VIP Customers | Yes | |
| Priority | Score 0-10 (10 = highest) | 10 | Yes | |
| Route To (Module) | Destination module | Queue, Extension, etc. | No | |
| Route To (Destination) | Specific destination | VIP Support | No | |
| Enabled | Rule active status | On/Off | Yes |
Priority Score Guide
| Score Range | Description | Typical Use | |
|---|---|---|---|
| 10 | Highest priority | VIP customers, executives | |
| 8-9 | Very high priority | Premium members, key accounts | |
| 6-7 | Above normal | Gold members, partners | |
| 5 | Normal priority | Standard customers | |
| 3-4 | Below normal | Trial users | |
| 0-2 | Lowest priority | Public, unidentified |
5. Common Scenarios & Examples
Scenario 1: Customer Tier System
Rules:| Name | Priority | Route To | |
|---|---|---|---|
| Platinum | 10 | Queue: VIP Support | |
| Gold | 8 | Queue: Premium Support | |
| Silver | 6 | Queue: Priority Support | |
| Bronze | 4 | Queue: Standard Support |
Scenario 2: Partner Routing
Rules:| Name | Priority | Route To | |
|---|---|---|---|
| Strategic Partners | 9 | Queue: Partner Desk | |
| Resellers | 7 | Queue: Channel Support | |
| Affiliates | 5 | Queue: General Support |
Scenario 3: Account Size Routing
Rules:| Name | Priority | Route To | |
|---|---|---|---|
| Enterprise | 10 | Queue: Enterprise Team | |
| Mid-Market | 7 | Queue: Business Team | |
| SMB | 5 | Queue: Small Business | |
| Startup | 3 | Queue: Growth Team |
6. Limitations & Important Notes
Technical Notes
Best Practices
- Plan Priority Tiers: Define your tier structure before creating rules
- Reserve Top Scores: Keep 9-10 for truly exceptional cases
- Use Meaningful Names: Names appear in reports and logs
- Test Integration: Verify VIP lists and queues reference correctly
- Document Rules: Keep a reference of what each priority level means
---
7. Troubleshooting Tips
Common Issues
| Symptom | Possible Cause | Solution | |
|---|---|---|---|
| Rule not applied | Rule disabled | Enable the rule | |
| Wrong destination | Wrong module selected | Verify module/destination | |
| Priority not working | Not linked to VIP list | Reference rule in VIP list | |
| Unexpected routing | Higher priority rule matched | Check all enabled rules |
Diagnostic SQL
List priority routing rules: Check VIP list references:---
8. Glossary
| Term | Definition | |
|---|---|---|
| Priority Routing | Named rule with priority score for call routing | |
| Priority Score | 0-10 value (10 = highest priority) | |
| VIP List | List of caller IDs that reference priority rules | |
| Routing Engine | System component that evaluates and applies rules | |
| Destination Module | Target type (Queue, Extension, IVR, etc.) |
Lua Handler Status
⚡ No Dedicated Handler Required
Priority Routing is a configuration module. The rules are:
- Stored in
public.priority_routing - Referenced by VIP Lists and Queue configurations
- Consumed by the main routing engine during call processing
---
Documentation last updated: January 2026