Create a Call Queue
Create new Call Queues for the given location.
Call queues temporarily hold calls in the cloud when all agents, which can be users or agents, assigned to receive calls from the queue are unavailable. Queued calls are routed to an available agent when not on an active call. Each call queue is assigned a Lead Number, which is a telephone number outside callers can dial to reach users assigned to the call queue. Call queues are also assigned an internal extension, which can be dialed internally to reach users assigned to the call queue.
Creating a call queue requires a full administrator auth token with a scope of spark-admin:telephony_config_write.
URI Parameters
Create the call queue for this location.
Query Parameters
Create the call queue for this organization.
Body Parameters
Unique name for the call queue.
Primary phone number of the call queue.
Primary phone extension of the call queue.
Language code.
First name to be shown when calls are forwarded out of this call queue. Defaults to ".".
Last name to be shown when calls are forwarded out of this call queue. Defaults to phone number if set, otherwise defaults to call group name.
Time zone for the hunt group.
Policy controlling how calls are routed to agents.
Call routing policy to use to dispatch calls to agents.
(Max 1,000 agents) This option cycles through all agents after the last agent that took a call. It sends calls to the next available agent.
(Max 1,000 agents) Send the call through the queue of agents in order, starting from the top each time.
(Max 50 agents) Sends calls to all agents at once
(Max 1,000 agents) Sends calls to the agent that has been idle the longest. If they don't answer, proceed to the next agent who has been idle the second longest, and so on until the call is answered.
(Max 100 agents) Sends call to idle agents based on percentages you assign to each agent (up to 100%).
Settings for when the call into the hunt group is not answered.
If enabled, bounce calls after the set number of rings.
Number of rings after which to bounce call, if call bounce is enabled.
Bounce if agent becomes unavailable.
Alert agent if call on hold more than alertAgentMaxSeconds.
Number of second after which to alert agent if alertAgentEnabled.
Bounce if call on hold more than callBounceMaxSeconds.
Number of second after which to bounce if callBounceEnabled.
Whether or not the call queue has the distinctive ring option enabled.
Whether or not the distinctive ring is enabled.
Ring pattern for when this callqueue is called. Only available when distinctiveRing is enabled for the call queue.
Normal incoming ring pattern.
Incoming ring pattern of two long rings.
Incoming ring pattern of two short rings, followed by a short ring.
Incoming ring pattern of a short ring, followed by a long ring, followed by a short ring.
Overall call queue settings.
Assign the maximum number of calls for this call queue. Once this number is reached, the overflow settings are triggered (max 50).
Play ringing tone to callers when their call is set to an available agent.
Reset caller statistics upon queue entry.
Settings for incoming calls exceed queueSize.
How to handle new calls when the queue is full.
The caller hears a fast-busy tone.
The caller hears ringing until they disconnect.
Enter the number where you want to transfer overflow calls.
When true, forward all calls to a voicemail service of an internal number. This option is ignored when an external transferNumber is entered.
Destination number for overflow calls when action is set to TRANSFER_TO_PHONE_NUMBER.
After calls wait for the configured number of seconds and no agent is available, the overflow treatment is triggered.
Number of seconds to wait before the overflow treatment is triggered when no agent is available.
Indicate overflow audio to be played, otherwise callers will hear the hold music until the call is answered by a user.
How to handle new calls when the queue is full.
Play the custom announcement specified by the fileName field.
Play default announcement.
Array of announcement file name strings to be played as overflow greetings. These files must be from the list of announcements files associated with this call queue.
People, including workspaces, that are eligible to receive calls.
ID of person or workspace.
Weight of person or workspace. Only applied when call policy is WEIGHTED.
Response Properties
ID of the newly created call queue.
Response Codes
The list below describes the common success and error responses you should expect from the API.
| Code | Status | Description |
|---|---|---|
| 200 | OK | Successful request with body content. |
| 204 | No Content | Successful request without body content. |
| 400 | Bad Request | The request was invalid or cannot be otherwise served. An accompanying error message will explain further. |
| 401 | Unauthorized | Authentication credentials were missing or incorrect. |
| 403 | Forbidden | The request is understood, but it has been refused or access is not allowed. |
| 404 | Not Found | The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method. |
| 405 | Method Not Allowed | The request was made to a resource using an HTTP request method that is not supported. |
| 409 | Conflict | The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once. |
| 410 | Gone | The requested resource is no longer available. |
| 415 | Unsupported Media Type | The request was made to a resource without specifying a media type or used a media type that is not supported. |
| 423 | Locked | The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again. |
| 428 | Precondition Required | File(s) cannot be scanned for malware and need to be force downloaded. |
| 429 | Too Many Requests | Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made. |
| 500 | Internal Server Error | Something went wrong on the server. If the issue persists, feel free to contact the Webex Developer Support team. |
| 502 | Bad Gateway | The server received an invalid response from an upstream server while processing the request. Try again later. |
| 503 | Service Unavailable | Server is overloaded with requests. Try again later. |
| 504 | Gateway Timeout | An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it. |
Header
Query Parameters
- Create the call queue for this organization.
Body
- Unique name for the call queue.
- Primary phone number of the call queue.
- Primary phone extension of the call queue.
- Language code.
- First name to be shown when calls are forwarded out of this call queue. Defaults to ".".
- Last name to be shown when calls are forwarded out of this call queue. Defaults to phone number if set, otherwise defaults to call group name.
- Time zone for the hunt group.
- Policy controlling how calls are routed to agents.
- Overall call queue settings.
- People, including workspaces, that are eligible to receive calls.
{
"name": "CallQueue-1",
"phoneNumber": "5558675309",
"extension": "7781",
"firstName": "Hakim",
"lastName": "Smith",
"callPolicies": {
"policy": "UNIFORM",
"waitingEnabled": false,
"noAnswer": {
"nextAgentEnabled": false,
"nextAgentRings": 5,
"forwardEnabled": false,
"numberOfRings": 0,
"destinationVoicemailEnabled": false
},
"businessContinuity": {
"enabled": false,
"destinationVoicemailEnabled": false
}
},
"agents": [
{"id": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS83MGY2MzYzMC1mZjlmLTExZWItODU5YS0xZjhiYjRjNzc1MWQ"},
{"id": "Y2lzY29zcGFyazovL3VzL1BMQUNFLzg0YjQ1OTIyLWZmOWYtMTFlYi1hNGI4LTMzNjI3YmVkNjdiNQ"}],
"enabled": true
}
{
"id": "Y2lzY29zcGFyazovL3VzL0hVTlRfR1JPVVAvYUhaaFpUTjJNRzh5YjBBMk5EazBNVEk1Tnk1cGJuUXhNQzVpWTJ4a0xuZGxZbVY0TG1OdmJRPT0"
}