Synchronize Queue Distribution Changes Across Custom Rules with callHandlingAction = AgentQueue
Description of the Idea:
When modifying a Call Queue’s distribution method (e.g., Round-Robin, Simultaneous, etc.), custom call handling rules that use callHandlingAction = AgentQueue are not updated accordingly. This leads to operational inconsistencies and requires manual updates to each rule individually, which is error-prone and time-consuming.
Suggested Improvement:
Introduce automatic synchronization between a queue’s main distribution settings and all custom rules that use that queue via callHandlingAction = AgentQueue.
This could be implemented in one of two ways:
- Add a new boolean attribute, e.g. syncqueuedistribution, in the PUT /business-hours-rule request. When true, all relevant rules will inherit the updated distribution method.
- Or, update these rules systematically whenever a queue’s configuration is changed.
Use Case:
- A company updates a call queue to switch from Rotating to Simultaneous ringing.
- All business-hours rules that previously directed calls to this queue should now reflect this new behavior automatically.
- Today, this requires modifying each rule manually, which is not scalable for environments with dozens or hundreds of rules.
Technical Suggestion (Example):
PUT /restapi/v1.0/account/~/call-handling/business-hours-rule
{
"callHandlingAction": "AgentQueue",
"queueId": "123456",
"syncqueuedistribution": true
}
Benefits:
- Improves operational consistency
- Reduces manual effort and risk of misconfiguration
- Ensures alignment between queue settings and rule behavior
- Supports automation and large-scale administration
Priority:
Medium, but impacts operational efficiency and user experience — ideally implemented ASAP for large-scale queue management.
Conclusion:
Adding automatic synchronization (or a syncqueuedistribution option) will ensure that rule behavior remains consistent with the queue's active configuration, streamlining queue management and reducing errors in call handling logic.
Let me know if a configuration flow or JSON schema proposal would help further illustrate the use case.
