# Create and Edit Queues

Use this page when creating a new queue or editing an existing queue from **Configuration &gt; Queues**.

The form screenshots below are separated by block where the application exposes separate sections. Complete the required values, review routing or destination references, and save the record.

## Form sections

<table id="bkmrk-sectiondescription-i"><thead><tr><th>Section</th><th>Description</th></tr></thead><tbody><tr><td>Information</td><td>Core identity and routing fields for the object.</td></tr><tr><td>Agents</td><td>Agent assignment and queue membership behavior.</td></tr><tr><td>Periodic Announce</td><td>Settings shown in the Periodic Announce block.</td></tr><tr><td>Queue exit key</td><td>Settings shown in the Queue exit key block.</td></tr><tr><td>Call Back service</td><td>Settings shown in the Call Back service block.</td></tr><tr><td>Abandoned Calls</td><td>Settings shown in the Abandoned Calls block.</td></tr><tr><td>Position/Time Announce</td><td>Settings shown in the Position/Time Announce block.</td></tr><tr><td>API Integrations</td><td>API-related credentials, restrictions, and integration controls.</td></tr></tbody></table>

### Information

<figure id="bkmrk-information-section-">![Information section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Y1pqueues-form-section-1.png)<figcaption>Information section on the edit form.</figcaption></figure>Core identity and routing fields for the object.

### Agents

<figure id="bkmrk-agents-section-on-th">![Agents section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/bjQqueues-form-section-2.png)<figcaption>Agents section on the edit form.</figcaption></figure>Agent assignment and queue membership behavior.

### Periodic Announce

<figure id="bkmrk-periodic-announce-se">![Periodic Announce section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/2vWqueues-form-section-3.png)<figcaption>Periodic Announce section on the edit form.</figcaption></figure>Settings shown in the Periodic Announce block.

### Queue exit key

<figure id="bkmrk-queue-exit-key-secti">![Queue exit key section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/EQuqueues-form-section-4.png)<figcaption>Queue exit key section on the edit form.</figcaption></figure>Settings shown in the Queue exit key block.

### Call Back service

<figure id="bkmrk-call-back-service-se">![Call Back service section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/1Uuqueues-form-section-5.png)<figcaption>Call Back service section on the edit form.</figcaption></figure>Settings shown in the Call Back service block.

### Abandoned Calls

<figure id="bkmrk-abandoned-calls-sect">![Abandoned Calls section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Fnhqueues-form-section-6.png)<figcaption>Abandoned Calls section on the edit form.</figcaption></figure>Settings shown in the Abandoned Calls block.

### Position/Time Announce

<figure id="bkmrk-position%2Ftime-announ-1">![Position/Time Announce section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Suhqueues-form-section-7.png)<figcaption>Position/Time Announce section on the edit form.</figcaption></figure>Settings shown in the Position/Time Announce block.

### API Integrations

<figure id="bkmrk-api-integrations-sec">![API Integrations section on the edit form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/GY3queues-form-section-8.png)<figcaption>API Integrations section on the edit form.</figcaption></figure>API-related credentials, restrictions, and integration controls.

## Main fields

<table id="bkmrk-fielddescription-nam"><thead><tr><th>Field</th><th>Description</th></tr></thead><tbody><tr><td>Name:</td><td>Display name used in lists and references.</td></tr><tr><td>Number:</td><td>Dialed value, identifier, or matching value used by the PBX.</td></tr><tr><td>Always Record:</td><td>Recording behavior or recording delivery setting.</td></tr><tr><td>Email recording to:</td><td>Email address used for notifications, delivery, or mailbox access.</td></tr><tr><td>Minimum Size (bytes):</td><td>Object setting shown by the form.</td></tr><tr><td>Play to the caller:</td><td>Caller ID or caller matching value.</td></tr><tr><td>Queue timeout:</td><td>Timing value used by the service.</td></tr><tr><td>Service level:</td><td>Object setting shown by the form.</td></tr><tr><td>Max Queue Length:</td><td>Object setting shown by the form.</td></tr><tr><td>Weight:</td><td>Object setting shown by the form.</td></tr><tr><td>Auto fill:</td><td>Object setting shown by the form.</td></tr><tr><td>Queue rule:</td><td>Object setting shown by the form.</td></tr><tr><td>Queue min penalty:</td><td>Object setting shown by the form.</td></tr><tr><td>Queue max penalty:</td><td>Object setting shown by the form.</td></tr><tr><td>Queue raise penalty:</td><td>Object setting shown by the form.</td></tr><tr><td>Progress:</td><td>Object setting shown by the form.</td></tr><tr><td>Queue server:</td><td>Server, host, or node selection used by the object.</td></tr><tr><td>Strategy:</td><td>Object setting shown by the form.</td></tr><tr><td>allowoptimization</td><td>Object setting shown by the form.</td></tr><tr><td>Ring when in use:</td><td>Object setting shown by the form.</td></tr><tr><td>Ring when offline:</td><td>Object setting shown by the form.</td></tr><tr><td>Available Agent ringing:</td><td>Object setting shown by the form.</td></tr><tr><td>Report caller's hold time:</td><td>Caller ID or caller matching value.</td></tr><tr><td>Agent timeout:</td><td>Timing value used by the service.</td></tr><tr><td>Wrap-up time:</td><td>Object setting shown by the form.</td></tr><tr><td>Wait time for retry:</td><td>Timing value used by the service.</td></tr><tr><td>Penalty members limit:</td><td>Object setting shown by the form.</td></tr><tr><td>Auto pause:</td><td>Object setting shown by the form.</td></tr></tbody></table>

## Queue rules and penalties

Use a **Queue rule** when a caller should stay in the same queue while the PBX changes which agent penalty levels are eligible as the caller waits. This keeps the caller's queue position instead of moving the caller to another queue or reinserting the caller with different penalty values.

### Queue penalty fields

<figure id="bkmrk-queue-penalty-fields-1">![Queue penalty fields on the queue Information section.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/queue-rule-queue-form.png)<figcaption>Queue penalty fields on the queue Information section.</figcaption></figure><table id="bkmrk-fieldhow-it-works-qu"><thead><tr><th>Field</th><th>How it works</th></tr></thead><tbody><tr><td>Queue rule</td><td>Selects the time-based rule used by the queue. The rule rows are maintained from the Queue rules screen linked from the Queues list.</td></tr><tr><td>Queue min penalty</td><td>Sets the starting lower penalty boundary for the caller. Agents with a lower penalty are not considered while this value is active.</td></tr><tr><td>Queue max penalty</td><td>Sets the starting upper penalty boundary for the caller. Agents with a higher penalty are not considered while this value is active.</td></tr><tr><td>Queue raise penalty</td><td>Treats agents below the selected raise value as if they had the raise value for this caller. This can remove the priority advantage of lower-penalty agents without changing the stored member penalty.</td></tr><tr><td>Penalty members limit</td><td>When this queue-level limit is greater than zero and the queue has that number of members or fewer, Asterisk can ignore penalty weighting for availability decisions.</td></tr></tbody></table>

### Queue rule pages

<figure id="bkmrk-queue-rules-list-wit">![Queue rules list with the Docs Priority Escalation example.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/queue-rules-list.png)<figcaption>Queue rules list with the Docs Priority Escalation example.</figcaption></figure>The Queue rules list shows each rule, its description, and a generated summary of the timed penalty changes. Open the rule name to edit the rule header, or select **Manage rules** to edit the timed rows.

<figure id="bkmrk-queue-rule-header-fo">![Queue rule header form.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/queue-rule-form.png)<figcaption>Queue rule header form.</figcaption></figure>The rule header contains only the rule name and description. Use a descriptive name that explains the escalation purpose, such as **Docs Priority Escalation**.

<figure id="bkmrk-queue-rule-timed-pen">![Queue rule timed penalty changes.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/queue-rule-details.png)<figcaption>Queue rule timed penalty changes.</figcaption></figure><table id="bkmrk-columnmeaning-timese"><thead><tr><th>Column</th><th>Meaning</th></tr></thead><tbody><tr><td>Time</td><td>Seconds after the caller entered the queue. When this wait time is reached, the row values are applied to that caller.</td></tr><tr><td>Min penalty</td><td>New lower boundary for eligible agents.</td></tr><tr><td>Max penalty</td><td>New upper boundary for eligible agents.</td></tr><tr><td>Raise penalty</td><td>New raise value used to make lower-penalty agents behave as if they had the configured penalty for the current caller.</td></tr></tbody></table>

### Example escalation

<table id="bkmrk-wait-timevaluesresul"><thead><tr><th>Wait time</th><th>Values</th><th>Result</th></tr></thead><tbody><tr><td>Queue entry</td><td>Min 0, max 0, raise not used</td><td>Only primary agents with penalty 0 are considered.</td></tr><tr><td>After 30 seconds</td><td>Min 0, max 1, raise 1</td><td>Agents with penalties 0 and 1 are eligible. Penalty 0 agents are treated as penalty 1, so the first overflow tier is considered evenly with the primary tier.</td></tr><tr><td>After 60 seconds</td><td>Min 0, max 2, raise 2</td><td>Agents with penalties 0, 1, and 2 are eligible, and lower tiers are treated as penalty 2 for this caller.</td></tr><tr><td>After 90 seconds</td><td>Min 1, max 2, raise 2</td><td>Penalty 0 agents are no longer considered. The caller continues with the overflow tiers only.</td></tr></tbody></table>

Asterisk applies these values to the queue call variables for the caller currently waiting. Rule changes made after a caller has already entered the queue are not retroactively applied to that caller. For the **Weighted Random** strategy, member penalty is used as a weight for the selection metric, so the practical effect differs from the strict priority behavior used by the other queue strategies.

## Saving and deleting

<table id="bkmrk-taskhow-to-do-it-cre"><thead><tr><th>Task</th><th>How to do it</th></tr></thead><tbody><tr><td>Create</td><td>Select the new action from the Queues list, fill the required fields, and select Save.</td></tr><tr><td>Edit</td><td>Open the existing queue, update the needed fields, and select Save.</td></tr><tr><td>Delete</td><td>Before deleting a queue, check call-flow, destination, schedule, report, provisioning, or integration references. Use the row delete action or the form delete action when available, then confirm.</td></tr></tbody></table>