Executive Summary
Introduce a configuration toggle in the call queue setup interface that gives administrators the flexibility to choose between the legacy management framework (requiring only a manager email or distribution list) and the current framework (mandating an individual directory user account). This ensures teams that rely on collaborative group oversight are not forced into an individual user dependency.

🔴 Problem & Business Impact
The current setup strictly enforces the assignment of a specific individual user profile from the corporate directory. For organizations built around decentralized management, this introduces severe operational bottlenecks:

Forced Individual Dependencies: Attaching a single user account creates an immediate single point of failure if that person is out of office or leaves the company.

Information Siloing: Performance alerts, voicemail notifications, and critical queue tracking flow into a single inbox rather than a shared ecosystem.

Flawed Workarounds: Using dummy or placeholder user accounts adds unnecessary account overhead and fundamentally fails to grant collective reporting or monitoring access to the wider team.

💡 Proposed Solution
Instead of a total system-wide reversion, implement a dynamic toggle selection during the call queue setup wizard:

Management Mode Toggle: Provide a clear switch or selection field allowing the administrator to choose between "Group/Manager Email Setup" and "Individual Directory User."

Option A: Group/Manager Email (Legacy Framework): Selecting this mode makes entering a manager email address the only requirement to complete the step. It must natively accept individual addresses, shared mailboxes, or distribution lists (DLs) without validating against a specific directory user profile.

Option B: Directory User (Current Framework): Retain the current behavior for teams that prefer mapping the call queue's administrative permissions directly to a single, active system user account.

✅ Success Criteria
Administrators can seamlessly toggle between both setup methodologies during call queue creation or modification.

Selecting the email-only option successfully deploys the queue without requiring an active directory account or drawing from individual user license pools.

Queue metrics, voicemail routing alerts, and notifications successfully distribute to whatever endpoint is entered in the email option, including complex multi-user distribution lists.