Description of the Idea:
Introduce an official and documented API endpoint to apply a Call Queue template directly when creating or updating multiple call queues, ensuring the template’s configuration is systematically reflected during provisioning.

Current Issue:
- There is no standard API to directly apply a Call Queue template at creation time.
- The current workaround involves copying settings manually from an existing queue, but this does not always reflect the full template configuration.
- This leads to inconsistent behavior and slows down automated provisioning pipelines, especially in large-scale deployments.

Suggested Improvement:
Implement and expose a dedicated API endpoint such as:

Example usage

baseurl = f"/restapi/v1.0/account/~/queue/templates/{templateid}/bulk-apply"
return self.platform.post(
base_url,
{
"queueIds": List[int], # List of target queue IDs
"notifyManager": bool, # Optional: notify queue manager
"emailAddresses": List[str], # Optional: notification recipients
}
)

This would allow applying a saved template to multiple queues in a reliable, scalable, and automated way.

Benefits:
- Ensures consistency in configuration across queues
- Speeds up onboarding and provisioning processes
- Reduces risk of human error
- Simplifies infrastructure-as-code and DevOps automation
- Improves maintainability and reduces support requests due to misconfigured queues

Priority:
High — Needed ASAP for organizations managing a large number of call queues through automation.

Conclusion:
Adding an API endpoint like /queue/templates/{template_id}/bulk-apply would empower teams to apply templates programmatically, improving consistency and provisioning speed across the RingCentral platform.

Let me know if a formal use case or deployment diagram would be helpful to support this idea.