VIP Lists (Queues VIP) Module Documentation
Table of Contents
- Module Overview (Technical)
- Module Overview (Commercial/Business)
- Module Overview (End User/Administrator)
- Configuration Fields Reference
- Priority Scoring
- Common Scenarios & Examples
- Limitations & Important Notes
- Troubleshooting Tips
- Glossary
---
1. Module Overview (Technical)
What Are VIP Lists?
VIP Lists are reusable caller identification lists that boost queue priority for matching phone numbers. When a caller's number matches a VIP list member, they receive priority treatment in the queue.
Architecture
Key Tables
| Table | Purpose | |
|---|---|---|
public.vip_lists | VIP list definitions | |
public.vip_list_members | Phone numbers and settings | |
public.call_center_queue_vip_lists | Queue-VIP list associations |
Key Files
| File | Description | |
|---|---|---|
admin/apps/web/src/modules/vipLists/ | Frontend module | |
admin/apps/web/src/i18n/en/vipLists.json | Translations |
2. Module Overview (Commercial/Business)
Business Value
VIP Lists provide differentiated customer experiences:
| Without VIP Lists | With VIP Lists | |
|---|---|---|
| All callers equal priority | VIP callers prioritized | |
| No caller recognition | Automatic identification | |
| Manual escalation | Automatic queue boost | |
| No tier forcing | Direct to best agents |
Use Cases
- Enterprise Customers
- Direct routing to senior agents
- Premium Memberships
- Higher queue priority
- Partner Programs
- Dedicated tier access
- Account-Based Service
- Custom service levels
Feature Highlights
| Feature | Benefit | |
|---|---|---|
| Reusable Lists | One list, multiple queues | |
| Weight Scoring | 1-100 priority boost | |
| Level Override | Force specific tier | |
| Position Override | Force queue position | |
| Per-Member Enable | Individual control | |
| Drag-and-Drop | Easy member ordering |
3. Module Overview (End User/Administrator)
What Can You Do?
- Create named VIP lists
- Add phone numbers as members
- Set priority weights (1-100)
- Override tier levels (force to senior agents)
- Override queue positions (jump to front)
- Assign lists to multiple queues
Administrator Workflow
Queue Integration
In Queue settings, select VIP Lists to associate:
Quick Tips
TIP
Reusable Lists: Create one "VIP Customers" list and use across multiple queues.TIP
Weight vs Override: Use weight for relative priority, overrides for absolute control.CAUTION
Position Override = 1: This puts caller at front of queue—use sparingly.---
4. Configuration Fields Reference
VIP List Fields
| Field | Description | Example | |
|---|---|---|---|
| List Name | Unique identifier | Premium Customers | |
| Description | Optional description | Enterprise accounts | |
| Enabled | List active status | On/Off |
VIP Member Fields
| Field | Description | Range | Default | |
|---|---|---|---|---|
| Phone Number | Caller ID to match | E.164 format | Required | |
| Weight | Priority score boost | 1-100 | 10 | |
| Level Override | Force tier level | 1-10 (1=highest) | None | |
| Position Override | Force queue position | 1-200 (1=first) | None | |
| Enabled | Member active status | On/Off | On |
Field Behaviors
| Field | Effect | |
|---|---|---|
| Weight | Adds to caller's queue score (higher = more priority) | |
| Level Override | Forces caller to specific agent tier (1 = senior agents) | |
| Position Override | Places caller at specific queue position (1 = front) |
5. Priority Scoring
How VIP Scoring Works
Priority Matrix
| Configuration | Effect | |
|---|---|---|
| Weight only | Relative priority boost | |
| Level Override only | Force to specific agent tier | |
| Position Override only | Force to specific queue position | |
| Weight + Level | Boost + tier forcing | |
| All three | Maximum VIP treatment |
6. Common Scenarios & Examples
Scenario 1: Enterprise Accounts
VIP List: "Enterprise"| Phone | Weight | Level | Position | |
|---|---|---|---|---|
| +15551234567 | 50 | 1 | - | |
| +15559876543 | 50 | 1 | - | |
| +15555551212 | 50 | 1 | - |
Scenario 2: Tiered Service Levels
VIP List: "Premium Service"| Phone | Weight | Level | Position | Description | |
|---|---|---|---|---|---|
| +15551111111 | 100 | 1 | 1 | CEO | |
| +15552222222 | 80 | 1 | - | CFO | |
| +15553333333 | 50 | 2 | - | Directors |
Scenario 3: Multi-Queue VIP
VIP List: "Gold Members"Assigned to:
- Sales Queue
- Support Queue
- Billing Queue
---
7. Limitations & Important Notes
Technical Notes
NOTE
Configuration Module: VIP Lists is a configuration module. List matching occurs during queue entry via mod_callcenter integration.WARNING
Phone Format: Use consistent format (E.164 recommended: +15551234567).Best Practices
- Use E.164 Format: +[country][number] for consistent matching
- Meaningful Weights: Use ranges (10-30-50-80-100) for clear tiers
- Level Override Sparingly: Reserve for true VIP
- Position Override Rarely: Only for executive-level callers
- Name Lists Clearly: "Enterprise Accounts" not "VIP 1"
---
8. Troubleshooting Tips
Common Issues
| Symptom | Possible Cause | Solution | |
|---|---|---|---|
| VIP not recognized | Phone format mismatch | Use consistent E.164 format | |
| No priority boost | List not assigned to queue | Assign in queue settings | |
| Member not working | Member disabled | Enable the member | |
| List not working | List disabled | Enable the list | |
| Wrong tier | Level override conflict | Check override values |
Diagnostic SQL
List VIP lists: Check VIP members: Check queue VIP list assignments:---
9. Glossary
| Term | Definition | |
|---|---|---|
| VIP List | Collection of priority caller phone numbers | |
| Weight | Priority score boost (1-100) | |
| Level Override | Forces caller to specific agent tier | |
| Position Override | Forces caller to specific queue position | |
| E.164 | International phone format (+[country][number]) |
Lua Handler Status
⚡ No Dedicated Handler Required
VIP Lists is a configuration module. The VIP matching is:
- Stored in
public.vip_listsandpublic.vip_list_members - Associated with queues via
public.call_center_queue_vip_lists - Evaluated by mod_callcenter or queue entry logic during call processing
---
Documentation last updated: January 2026