<Enqueue> verb enqueues the current call in a call queue. Enqueued calls wait in hold music
until the call is dequeued by another caller via the
<Dial> verb or transferred out of the queue via
the REST API or the
<Enqueue> verb will create a queue on demand, if the queue does not already exist. The default maximum length of the queue is 100. This can be modified using the
<Enqueue> verb supports the following attributes that modify its behavior:
|Attribute Name||Allowed Values||Default Value|
|action||relative or absolute URL||none|
|waitUrl||relative or absolute URL||default classical playlist|
|workflowSid||TaskRouter Workflow Sid||none|
The 'action' attribute takes an absolute or relative URL as a value.
A request is made to this URL when the call leaves the queue, describing the dequeue reason and details
about the time spent in the queue, which are described below. In the case where a call is dequeued due to
a REST API request or the
<Leave> verb, the action URL is requested right away. In the case where a call
is dequeued via the
<Dial> verb, the action URL is hit once when the bridged parties disconnect.
If no 'action' is provided, Twilio will fall through to the next verb in the document, if any.
Twilio will pass the following parameters in addition to the standard TwiML Voice request parameters with its request to the 'action' URL:
|QueueResult||The final result of the enqueued call. See queue result values below for details.|
|QueueSid||The SID of the queue. This is only available if the call was actually enqueued.|
|QueueTime||The time the call spent in the queue. This is only available if the call was actually enqueued.|
The following values represent the result of an attempt to enqueue a caller.
|bridged||The call was dequeued and bridged to the dequeuer.|
|bridging-in-process||Twilio has been instructed to bridge the enqueued party.|
|error||The TwiML contained an error, either in the
|hangup||The enqueued caller hung up before connecting to a dequeued call.|
|leave||The enqueued caller exited the queue via the
|redirected||While in the queue, the call was redirected out of the queue, typically by a REST API request.|
|redirected-from-bridged||The queued and then successfully bridged session was transferred out.|
|queue-full||The targeted queue was full, thus the enqueue attempt was rejected.|
|system-error||The Twilio system malfunctioned during the enqueue process. This can happen if a caller hangs up before being fully enqueued.|
The 'method' attribute takes the value 'GET' or 'POST'. This tells Twilio whether to request the 'action' URL via HTTP GET or POST. This attribute is modeled after the HTML form 'method' attribute. 'POST' is the default value.
The 'waitUrl' attribute specifies a URL pointing to a TwiML document containing TwiML verbs that will be executed while the caller is waiting in the queue.
Once the waitUrl TwiML flow runs out of verbs to execute, Twilio will re-request the waitUrl and start over, essentially
looping hold music indefinitely. The
<Redirect> verb can be used for multiple document flows, but flow will always return to the waitUrl
once there is no TwiML left to execute.
The following verbs are supported in the waitUrl TwiML document:
|<Play>||Plays a file to the caller.|
|<Say>||Say something to the caller using Twilio text-to-speech.|
|<Pause>||Pauses for a specified duration.|
|<Hangup>||Hangs up the call and thereby leaving the queue and ending the call.|
|<Redirect>||Redirect to another TwiML document.|
|<Leave>||Makes the current call leave the queue, but doesn't hang up the call. Execution proceeds with the next verb after the '<Enqueue>' verb.|
|<Gather>||Collects digits that a caller enters into his or her telephone keypad. NOTE: only DTMF input type is supported in '<Gather>' returned in an '<Enqueue>' waitUrl; speech input type will not work.|
Twilio will pass the following parameters in addition to the standard TwiML Voice request parameters with its request to the 'waitUrl' URL:
|QueuePosition||The current queue position for the enqueued call.|
|QueueSid||The SID of the Queue that the caller is in.|
|QueueTime||The time in seconds that the caller has been in the queue.|
|AvgQueueTime||An average of how long the current enqueued callers have been in the queue in seconds.|
|CurrentQueueSize||The current number of enqueued calls in this queue.|
The 'waitUrlMethod' attribute takes the value 'GET' or 'POST'. This tells Twilio whether to request the 'waitUrl' via HTTP GET or POST. This attribute is modeled after the HTML form 'method' attribute. 'POST' is the default value.
The 'workflowSid' attribute tells Twilio to create a new TaskRouter Task to represent this call and specifies the ID of the desired Workflow to handle it.
If 'workflowSid' is specified, it is not necessary to specify a name for the Queue to place the call in. When a Worker is identified to handle the call it can be dequeued and connected using the dequeue assignment instruction.
The "noun" of a TwiML verb is the nested content of the verb that's not a verb itself; it's the information the verb acts upon. These are the nouns for
|plain text||The name of a particular queue.|
|Task||The attributes to be set for the newly created task, formatted as JSON|
If the named queue wasn't already created, it will be created on demand. The queue name can not be longer than 64 characters.
You can find more information and examples on how to use Task on the TaskRouter TwiML Integration page.
This TwiML document tells Twilio to fetch the wait-music.xml TwiML document and execute it while the caller is in the queue:
The wait-music.xml TwiML document plays some nice hold music:
- You can use the parameters on the 'waitUrl' request to
<Say>back to the caller what his or her queue position is and how long he or she can expect to wait.