# Conditions

# Overview

The **Conditions** page defines reusable tests for schedules, caller identity, channel usage, queue state, variables, authentication, and other routing decisions. Open it from **Configuration > Conditions**.

The page works against the tenant currently selected in the top bar. The screenshots and demo rows were captured in the **Canistracci OIL** tenant.

<figure id="bkmrk-conditions-list-page">![Conditions list page filtered to documentation examples in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/8A0conditions-list.png)<figcaption>Conditions list page filtered to documentation examples in the Canistracci OIL tenant.</figcaption></figure>## Working with conditions

<table id="bkmrk-taskhow-to-do-it-add"><thead><tr><th>Task</th><th>How to do it</th></tr></thead><tbody><tr><td>Add</td><td>Select New Condition, enter a name, choose the condition type, complete the type-specific fields, and select Save.</td></tr><tr><td>Edit</td><td>Open a condition by selecting its name in the list, change the fields, and select Save.</td></tr><tr><td>Duplicate</td><td>Use the duplicate action in the Actions column to copy an existing condition before changing it.</td></tr><tr><td>Delete</td><td>Select one or more rows and use Delete Selected, or open a condition and delete it after checking references.</td></tr><tr><td>Show flow</td><td>Use the flow action in the Actions column to inspect where the condition routes calls.</td></tr></tbody></table>

## Page functions

<table id="bkmrk-actiondescription-ne"><thead><tr><th>Action</th><th>Description</th></tr></thead><tbody><tr><td>New Condition</td><td>Opens the creation form for a new condition.</td></tr><tr><td>Delete Selected</td><td>Deletes selected conditions after confirmation.</td></tr><tr><td>Search</td><td>Filters the visible rows by name, type, condition summary, or action text.</td></tr><tr><td>Sort</td><td>Sorts the list by the selected column.</td></tr><tr><td>Page size</td><td>Changes how many conditions are shown per page.</td></tr></tbody></table>

## List columns

<table id="bkmrk-columndescription-se"><thead><tr><th>Column</th><th>Description</th></tr></thead><tbody><tr><td>Select</td><td>Selects a condition for bulk deletion.</td></tr><tr><td>Name</td><td>Condition display name. Select it to edit the condition.</td></tr><tr><td>Type</td><td>Condition type code used by MiRTA PBX.</td></tr><tr><td>Condition</td><td>Human-readable summary of the configured match rule.</td></tr><tr><td>Actions</td><td>Duplicate and flow-inspection actions for the row.</td></tr></tbody></table>

## Condition types

<table id="bkmrk-typepurposeexample-r"><thead><tr><th>Type</th><th>Purpose</th><th>Example record</th></tr></thead><tbody><tr><td>Weektime</td><td>Matches weekly recurring time slots, such as business hours or after-hours periods.</td><td>Docs Condition - Weektime</td></tr><tr><td>Calendar</td><td>Matches absolute date and time ranges for holidays, maintenance windows, and one-off closures.</td><td>Docs Condition - Calendar</td></tr><tr><td>Hours</td><td>Matches one or more daily time ranges without selecting specific weekdays.</td><td>Docs Condition - Hours</td></tr><tr><td>Simple Caller ID</td><td>Matches the caller number against one or more literal values or regular expressions.</td><td>Docs Condition - Simple Caller ID</td></tr><tr><td>Simple Caller ID Name</td><td>Matches the caller name against one or more literal values or regular expressions.</td><td>Docs Condition - Simple Caller ID Name</td></tr><tr><td>Weekday</td><td>Matches selected days of the week.</td><td>Docs Condition - Weekday</td></tr><tr><td>Date - exact match</td><td>Matches one or more exact dates or date/time values.</td><td>Docs Condition - Date - exact match</td></tr><tr><td>Date - lesser than date</td><td>Matches when the current date/time is earlier than the configured date/time.</td><td>Docs Condition - Date - lesser than date</td></tr><tr><td>Date - greater than date</td><td>Matches when the current date/time is later than the configured date/time.</td><td>Docs Condition - Date - greater than date</td></tr><tr><td>Date - between dates</td><td>Matches when the current date/time is between a configured start and end value.</td><td>Docs Condition - Date - between dates</td></tr><tr><td>Day of the month</td><td>Matches a specific day number in the month.</td><td>Docs Condition - Day of the month</td></tr><tr><td>Extension status</td><td>Matches the state of one selected extension or numbered flow.</td><td>Docs Condition - Extension status</td></tr><tr><td>Variable value</td><td>Matches a tenant user variable value.</td><td>Docs Condition - Variable value</td></tr><tr><td>Multiple variable values</td><td>Matches one variable against multiple possible values, each with its own destination path.</td><td>Docs Condition - Multiple variable values</td></tr><tr><td>System variable value</td><td>Matches an Asterisk or system channel variable value.</td><td>Docs Condition - System variable value</td></tr><tr><td>Multiple extensions status</td><td>Checks the combined state of multiple selected extensions.</td><td>Docs Condition - Multiple extensions status</td></tr><tr><td>AGI Script</td><td>Runs an AGI script and compares the AGIRESULT variable with TRUE.</td><td>Docs Condition - AGI Script</td></tr><tr><td>Authenticate</td><td>Prompts the caller for a PIN and matches when authentication succeeds.</td><td>Docs Condition - Authenticate</td></tr><tr><td>Tenant - number of I/O channels (external)</td><td>Matches when the tenant has more than the configured number of external channels in use.</td><td>Docs Condition - Tenant - number of I/O channels (external)</td></tr><tr><td>Tenant - number of any channels (internal and external)</td><td>Matches when the tenant has more than the configured number of total channels in use.</td><td>Docs Condition - Tenant - number of any channels (internal and external)</td></tr><tr><td>DID - number of inbound channels</td><td>Matches when a selected DID has more than the configured number of inbound channels in use.</td><td>Docs Condition - DID - number of inbound channels</td></tr><tr><td>Number of custom group channels</td><td>Matches when a custom channel group has more than the configured number of active channels.</td><td>Docs Condition - Number of custom group channels</td></tr><tr><td>Answering Machine Detection</td><td>Runs answering machine detection and matches according to the analysis result.</td><td>Docs Condition - Answering Machine Detection</td></tr><tr><td>SIP Header</td><td>Matches a SIP header against a regular expression.</td><td>Docs Condition - SIP Header</td></tr><tr><td>Agent logged in a queue</td><td>Matches when the selected agent is logged in to the selected queue.</td><td>Docs Condition - Agent logged in a queue</td></tr><tr><td>Agent paused from queue</td><td>Matches when the selected agent is paused in the selected queue.</td><td>Docs Condition - Agent paused from queue</td></tr><tr><td>Caller ID in Phonebook</td><td>Matches when caller ID is found in a selected phone book.</td><td>Docs Condition - Caller ID in Phonebook</td></tr><tr><td>Feature code parameter</td><td>Matches parameters collected by a feature code.</td><td>Docs Condition - Feature code parameter</td></tr><tr><td>All conditions listed satisfied</td><td>Matches only when every selected condition is satisfied.</td><td>Docs Condition - All conditions listed satisfied</td></tr><tr><td>Any conditions listed satisfied</td><td>Matches when at least one selected condition is satisfied.</td><td>Docs Condition - Any conditions listed satisfied</td></tr><tr><td>Negate condition result</td><td>Matches when the selected condition does not match.</td><td>Docs Condition - Negate condition result</td></tr><tr><td>Use a Global Condition</td><td>References a global condition from the tenant configuration.</td><td>Docs Condition - Use a Global Condition</td></tr><tr><td>Check SMS message</td><td>Matches SMS message content.</td><td>Docs Condition - Check SMS message</td></tr><tr><td>Check if a specific channel is running</td><td>Checks whether a channel matching the configured attributes is currently running.</td><td>Docs Condition - Check if a specific channel is running</td></tr><tr><td>Multiple destination over weektime</td><td>Routes to different destinations based on a color-coded weekly timetable.</td><td>Docs Condition - Multiple destination over weektime</td></tr><tr><td>Call Screening using a random PIN</td><td>Screens a call by playing a prompt and asking the caller to enter a generated PIN.</td><td>Docs Condition - Call Screening using a random PIN</td></tr><tr><td>Caller has already called in</td><td>Checks recent inbound call history for the current caller.</td><td>Docs Condition - Caller has already called in</td></tr><tr><td>Caller has been called out</td><td>Checks recent outbound call history for the current caller.</td><td>Docs Condition - Caller has been called out</td></tr><tr><td>Queue Callers, more than</td><td>Matches when a selected queue has more than the configured number of callers waiting.</td><td>Docs Condition - Queue Callers, more than</td></tr></tbody></table>

## Demo records

The Canistracci OIL tenant contains one documentation example for each available condition type: 39 records with names beginning with **Docs Condition -**. A global example named **Docs Global Condition - Weektime** is also available for the Use a Global Condition type.

## Deleting records

Before deleting a condition, check call flows, destinations, schedules, IVRs, feature codes, and reports that may reference it. MiRTA PBX asks for confirmation before the delete is submitted.

# Weektime

The **Weektime** type matches weekly recurring time slots, such as business hours or after-hours periods.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Weektime** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-weektime-condition-e">![Weektime condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/xgQweektime.png)<figcaption>Weektime condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Weektime.</td></tr><tr><td>Timezone</td><td>Timezone used to evaluate the weekly schedule. Leave it empty to use the tenant default.</td></tr><tr><td>Select timeslots</td><td>Weekly calendar where matching time blocks are drawn.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Weektime</td></tr><tr><td>Timeslot</td><td>Monday 09:00-17:00</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Weektime** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Calendar

The **Calendar** type matches absolute date and time ranges for holidays, maintenance windows, and one-off closures.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Calendar** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-calendar-condition-e">![Calendar condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/QSMcalendar.png)<figcaption>Calendar condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Calendar.</td></tr><tr><td>Timezone</td><td>Timezone used to evaluate the calendar entries.</td></tr><tr><td>Select timeslots</td><td>Calendar where date and time blocks are entered.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Calendar</td></tr><tr><td>Calendar slot</td><td>2026-12-24 09:00 to 2026-12-24 17:00</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Calendar** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Hours

The **Hours** type matches one or more daily time ranges without selecting specific weekdays.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Hours** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-hours-condition-edit">![Hours condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/VN1hours.png)<figcaption>Hours condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Hours.</td></tr><tr><td>Timezone</td><td>Timezone used to evaluate the time ranges.</td></tr><tr><td>From - To</td><td>Up to three daily start and end ranges.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Hours</td></tr><tr><td>From - To</td><td>09:00 to 17:00</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Hours** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Simple Caller ID

The **Simple Caller ID** type matches the caller number against one or more literal values or regular expressions.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Simple Caller ID** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-simple-caller-id-con">![Simple Caller ID condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/lvqsimple-caller-id.png)<figcaption>Simple Caller ID condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Simple Caller ID.</td></tr><tr><td>Caller ID</td><td>Caller number value or regular expression to match. Multiple rows can be used.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Simple Caller ID</td></tr><tr><td>Caller ID</td><td>^1555</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Simple Caller ID** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Simple Caller ID Name

The **Simple Caller ID Name** type matches the caller name against one or more literal values or regular expressions.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Simple Caller ID Name** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-simple-caller-id-nam">![Simple Caller ID Name condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/jYvsimple-caller-id-name.png)<figcaption>Simple Caller ID Name condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Simple Caller ID Name.</td></tr><tr><td>Caller ID Name</td><td>Caller name value or regular expression to match. Multiple rows can be used.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Simple Caller ID Name</td></tr><tr><td>Caller ID Name</td><td>Canistracci</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Simple Caller ID Name** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Weekday

The **Weekday** type matches selected days of the week.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Weekday** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-weekday-condition-ed">![Weekday condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Lrfweekday.png)<figcaption>Weekday condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Weekday.</td></tr><tr><td>Timezone</td><td>Timezone used to determine the current weekday.</td></tr><tr><td>Sunday through Saturday</td><td>Checkboxes for the days that should match.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Weekday</td></tr><tr><td>Days</td><td>Monday through Friday</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Weekday** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Date - exact match

The **Date - exact match** type matches one or more exact dates or date/time values.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Date - exact match** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-date---exact-match-c">![Date - exact match condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/prNdate-exact-match.png)<figcaption>Date - exact match condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Date - exact match.</td></tr><tr><td>Timezone</td><td>Timezone used to evaluate the date.</td></tr><tr><td>Date</td><td>Exact date or date/time value to match.</td></tr><tr><td>Recurring</td><td>Treats the date as recurring instead of a one-time date.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Date - Exact Match</td></tr><tr><td>Date</td><td>2026-12-25 00:00:00</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Date - exact match** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Date - lesser than date

The **Date - lesser than date** type matches when the current date/time is earlier than the configured date/time.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Date - lesser than date** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-date---lesser-than-d">![Date - lesser than date condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/5JWdate-lesser-than-date.png)<figcaption>Date - lesser than date condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Date - lesser than date.</td></tr><tr><td>Lesser than Date</td><td>Date or date/time threshold used by the comparison.</td></tr><tr><td>Recurring</td><td>Treats the threshold as a recurring date value.</td></tr><tr><td>Custom</td><td>Uses a custom date expression instead of the date picker value.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Date - Lesser Than Date</td></tr><tr><td>Lesser than Date</td><td>2026-12-31 23:59:59</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Date - lesser than date** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Date - greater than date

The **Date - greater than date** type matches when the current date/time is later than the configured date/time.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Date - greater than date** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-date---greater-than-">![Date - greater than date condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/ujUdate-greater-than-date.png)<figcaption>Date - greater than date condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Date - greater than date.</td></tr><tr><td>Greater than Date</td><td>Date or date/time threshold used by the comparison.</td></tr><tr><td>Recurring</td><td>Treats the threshold as a recurring date value.</td></tr><tr><td>Custom</td><td>Uses a custom date expression instead of the date picker value.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Date - Greater Than Date</td></tr><tr><td>Greater than Date</td><td>2026-01-01 00:00:00</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Date - greater than date** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Date - between dates

The **Date - between dates** type matches when the current date/time is between a configured start and end value.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Date - between dates** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-date---between-dates">![Date - between dates condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/4DSdate-between-dates.png)<figcaption>Date - between dates condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Date - between dates.</td></tr><tr><td>Between Date/Time</td><td>Start and end values for a matching window. Multiple windows can be configured.</td></tr><tr><td>Recurring</td><td>Treats the date window as recurring.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Date - Between Dates</td></tr><tr><td>Between Date/Time</td><td>2026-12-24 09:00:00 and 2026-12-24 17:00:00</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Date - between dates** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Day of the month

The **Day of the month** type matches a specific day number in the month.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Day of the month** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-day-of-the-month-con">![Day of the month condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/4Hwday-of-the-month.png)<figcaption>Day of the month condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Day of the month.</td></tr><tr><td>Timezone</td><td>Timezone used to evaluate the month day.</td></tr><tr><td>Day of the month</td><td>Day number from 1 to 31.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Day of the Month</td></tr><tr><td>Day of the month</td><td>15</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Day of the month** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Extension status

The **Extension status** type matches the state of one selected extension or numbered flow.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Extension status** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-extension-status-con">![Extension status condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/BAkextension-status.png)<figcaption>Extension status condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Extension status.</td></tr><tr><td>Extension</td><td>Extension or flow whose state is checked.</td></tr><tr><td>State</td><td>State to match: in use, not in use, or DND active.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Extension Status</td></tr><tr><td>Extension</td><td>100 - Alex Reed</td></tr><tr><td>State</td><td>Not in use</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Extension status** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Variable value

The **Variable value** type matches a tenant user variable value.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Variable value** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-variable-value-condi">![Variable value condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/7VAvariable-value.png)<figcaption>Variable value condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Variable value.</td></tr><tr><td>Variable</td><td>User variable name. The form prefixes the value with USR-.</td></tr><tr><td>Value</td><td>Value to compare against.</td></tr><tr><td>Use as Regex</td><td>Treats the value as a regular expression.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Variable Value</td></tr><tr><td>Variable</td><td>DEPARTMENT</td></tr><tr><td>Value</td><td>Accounting</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Variable value** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Multiple variable values

The **Multiple variable values** type matches one variable against multiple possible values, each with its own destination path.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Multiple variable values** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-multiple-variable-va">![Multiple variable values condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/P2Dmultiple-variable-values.png)<figcaption>Multiple variable values condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Multiple variable values.</td></tr><tr><td>Variable</td><td>User variable name. The form prefixes the value with USR-.</td></tr><tr><td>Value rows</td><td>Values to compare against.</td></tr><tr><td>Destination rows</td><td>Destination selected for each matching value.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Multiple Variable Values</td></tr><tr><td>Variable</td><td>SERVICE</td></tr><tr><td>Values</td><td>billing, support</td></tr></tbody></table>

## Destinations

This type hides the standard single match destination and shows destination rows for each configured variable value.

## Editing and deleting

To edit this condition, open **Docs Condition - Multiple variable values** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# System variable value

The **System variable value** type matches an Asterisk or system channel variable value.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **System variable value** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-system-variable-valu">![System variable value condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/96Isystem-variable-value.png)<figcaption>System variable value condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select System variable value.</td></tr><tr><td>System variable</td><td>Variable name available in the call, such as CALLERID(num).</td></tr><tr><td>Value</td><td>Value to compare against.</td></tr><tr><td>Use as Regex</td><td>Treats the value as a regular expression.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - System Variable Value</td></tr><tr><td>System variable</td><td>CALLERID(num)</td></tr><tr><td>Value</td><td>^1555</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - System variable value** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Multiple extensions status

The **Multiple extensions status** type checks the combined state of multiple selected extensions.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Multiple extensions status** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-multiple-extensions-">![Multiple extensions status condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/bebmultiple-extensions-status.png)<figcaption>Multiple extensions status condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Multiple extensions status.</td></tr><tr><td>Extensions</td><td>Extensions or numbered flows included in the check.</td></tr><tr><td>State</td><td>Combined state rule that must match.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Multiple Extensions Status</td></tr><tr><td>Extensions</td><td>100 and 101</td></tr><tr><td>State</td><td>All users are online</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Multiple extensions status** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# AGI Script

The **AGI Script** type runs an AGI script and compares the AGIRESULT variable with TRUE.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **AGI Script** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-agi-script-condition">![AGI Script condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/wv6agi-script.png)<figcaption>AGI Script condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select AGI Script.</td></tr><tr><td>AGI Script</td><td>Script to execute.</td></tr><tr><td>Parameter 1-5</td><td>Optional script parameters, depending on the selected script definition.</td></tr><tr><td>AGIRESULT</td><td>The script result variable must evaluate to TRUE for the condition to match.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - AGI Script</td></tr><tr><td>AGI Script</td><td>Docs Demo AGI 1</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - AGI Script** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Authenticate

The **Authenticate** type prompts the caller for a PIN and matches when authentication succeeds.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Authenticate** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-authenticate-conditi">![Authenticate condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/K4pauthenticate.png)<figcaption>Authenticate condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Authenticate.</td></tr><tr><td>Welcome Message</td><td>Prompt played before PIN entry.</td></tr><tr><td>PIN</td><td>Valid PIN value. Additional PIN fields can define more accepted values.</td></tr><tr><td>Maximum digits</td><td>Maximum number of digits the caller can enter.</td></tr><tr><td>Wrong PIN Message</td><td>Prompt played after an invalid PIN.</td></tr><tr><td>Max attempts</td><td>How many failed attempts are allowed.</td></tr><tr><td>Timeout</td><td>How long to wait for digits.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Authenticate</td></tr><tr><td>PIN</td><td>1234</td></tr><tr><td>Max attempts</td><td>3</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Authenticate** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Tenant - number of I/O channels (external)

The **Tenant - number of I/O channels (external)** type matches when the tenant has more than the configured number of external channels in use.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Tenant - number of I/O channels (external)** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-tenant---number-of-i">![Tenant - number of I/O channels (external) condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/JPltenant-number-of-io-channels-external.png)<figcaption>Tenant - number of I/O channels (external) condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Tenant - number of I/O channels (external).</td></tr><tr><td>More than # of I/O channels used</td><td>External channel threshold.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Tenant Channels</td></tr><tr><td>More than</td><td>5</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Tenant - number of I/O channels (external)** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Tenant - number of any channels (internal and external)

The **Tenant - number of any channels (internal and external)** type matches when the tenant has more than the configured number of total channels in use.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Tenant - number of any channels (internal and external)** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-tenant---number-of-a">![Tenant - number of any channels (internal and external) condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/PmOtenant-number-of-any-channels.png)<figcaption>Tenant - number of any channels (internal and external) condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Tenant - number of any channels (internal and external).</td></tr><tr><td>More than # of any type of channels used</td><td>Total channel threshold, including internal and external channels.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Tenant Any Channels</td></tr><tr><td>More than</td><td>10</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Tenant - number of any channels (internal and external)** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# DID - number of inbound channels

The **DID - number of inbound channels** type matches when a selected DID has more than the configured number of inbound channels in use.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **DID - number of inbound channels** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-did---number-of-inbo">![DID - number of inbound channels condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/YC0did-number-of-inbound-channels.png)<figcaption>DID - number of inbound channels condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select DID - number of inbound channels.</td></tr><tr><td>DID to monitor</td><td>DID whose inbound channel usage is checked.</td></tr><tr><td>More than # of channels used</td><td>Inbound channel threshold.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - DID Channels</td></tr><tr><td>DID</td><td>Docs Demo DID 1</td></tr><tr><td>More than</td><td>1</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - DID - number of inbound channels** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Number of custom group channels

The **Number of custom group channels** type matches when a custom channel group has more than the configured number of active channels.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Number of custom group channels** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-number-of-custom-gro">![Number of custom group channels condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/xgMnumber-of-custom-group-channels.png)<figcaption>Number of custom group channels condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Number of custom group channels.</td></tr><tr><td>Group name</td><td>Custom group name to count.</td></tr><tr><td>More than # of channels used</td><td>Channel count threshold.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Channel Group Count</td></tr><tr><td>Group name</td><td>support</td></tr><tr><td>More than</td><td>2</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Number of custom group channels** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Answering Machine Detection

The **Answering Machine Detection** type runs answering machine detection and matches according to the analysis result.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Answering Machine Detection** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-answering-machine-de">![Answering Machine Detection condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/t6oanswering-machine-detection.png)<figcaption>Answering Machine Detection condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Answering Machine Detection.</td></tr><tr><td>Initial silence</td><td>Maximum initial silence before greeting detection.</td></tr><tr><td>Greeting</td><td>Maximum greeting duration.</td></tr><tr><td>After greeting, silence</td><td>Silence duration after greeting.</td></tr><tr><td>Total analysis time</td><td>Maximum analysis window.</td></tr><tr><td>Word settings</td><td>Minimum and maximum word lengths, silence between words, and maximum word count.</td></tr><tr><td>Silence threshold</td><td>Audio threshold used for silence detection.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Answering Machine Detection</td></tr><tr><td>Total analysis time</td><td>5000</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Answering Machine Detection** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# SIP Header

The **SIP Header** type matches a SIP header against a regular expression.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **SIP Header** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-sip-header-condition">![SIP Header condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/pW3sip-header.png)<figcaption>SIP Header condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select SIP Header.</td></tr><tr><td>SIP Header</td><td>Header name to inspect.</td></tr><tr><td>Regular Expression</td><td>Expression used to match the header value.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - SIP Header</td></tr><tr><td>SIP Header</td><td>X-Account</td></tr><tr><td>Regular Expression</td><td>Accounting</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - SIP Header** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Agent logged in a queue

The **Agent logged in a queue** type matches when the selected agent is logged in to the selected queue.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Agent logged in a queue** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-agent-logged-in-a-qu">![Agent logged in a queue condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/0Q4agent-logged-in-a-queue.png)<figcaption>Agent logged in a queue condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Agent logged in a queue.</td></tr><tr><td>Agent</td><td>Agent extension or external agent to check.</td></tr><tr><td>Queue</td><td>Queue where login state is checked.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Agent Logged In</td></tr><tr><td>Agent</td><td>100 - Alex Reed</td></tr><tr><td>Queue</td><td>Accounting</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Agent logged in a queue** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Agent paused from queue

The **Agent paused from queue** type matches when the selected agent is paused in the selected queue.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Agent paused from queue** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-agent-paused-from-qu">![Agent paused from queue condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/PTOagent-paused-from-queue.png)<figcaption>Agent paused from queue condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Agent paused from queue.</td></tr><tr><td>Agent</td><td>Agent extension or external agent to check.</td></tr><tr><td>Queue</td><td>Queue where pause state is checked.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Agent Paused</td></tr><tr><td>Agent</td><td>100 - Alex Reed</td></tr><tr><td>Queue</td><td>Accounting</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Agent paused from queue** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Caller ID in Phonebook

The **Caller ID in Phonebook** type matches when caller ID is found in a selected phone book.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Caller ID in Phonebook** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-caller-id-in-phonebo">![Caller ID in Phonebook condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/BZzcaller-id-in-phonebook.png)<figcaption>Caller ID in Phonebook condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Caller ID in Phonebook.</td></tr><tr><td>Caller ID</td><td>Caller number to look up, usually provided dynamically during a call.</td></tr><tr><td>Phonebook</td><td>Phone book used for the lookup.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Caller ID in Phonebook</td></tr><tr><td>Caller ID</td><td>${CALLERID(num)}</td></tr><tr><td>Phonebook</td><td>Default</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Caller ID in Phonebook** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Feature code parameter

The **Feature code parameter** type matches parameters collected by a feature code.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Feature code parameter** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-feature-code-paramet">![Feature code parameter condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/Yvbfeature-code-parameter.png)<figcaption>Feature code parameter condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Feature code parameter.</td></tr><tr><td>Parameter</td><td>Parameter value to compare. Multiple parameter rows can be used.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Feature Code Parameter</td></tr><tr><td>Parameter 1</td><td>42</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Feature code parameter** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# All conditions listed satisfied

The **All conditions listed satisfied** type matches only when every selected condition is satisfied.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **All conditions listed satisfied** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-all-conditions-liste">![All conditions listed satisfied condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/all-conditions-listed-satisfied.png)<figcaption>All conditions listed satisfied condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select All conditions listed satisfied.</td></tr><tr><td>Conditions</td><td>Conditions that must all match.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - All Conditions</td></tr><tr><td>Conditions</td><td>Weektime and Weekday</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - All conditions listed satisfied** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Any conditions listed satisfied

The **Any conditions listed satisfied** type matches when at least one selected condition is satisfied.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Any conditions listed satisfied** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-any-conditions-liste">![Any conditions listed satisfied condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/any-conditions-listed-satisfied.png)<figcaption>Any conditions listed satisfied condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Any conditions listed satisfied.</td></tr><tr><td>Conditions</td><td>Conditions where any one match is enough.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Any Conditions</td></tr><tr><td>Conditions</td><td>Weektime or Caller ID</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Any conditions listed satisfied** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Negate condition result

The **Negate condition result** type matches when the selected condition does not match.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Negate condition result** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-negate-condition-res">![Negate condition result condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/negate-condition-result.png)<figcaption>Negate condition result condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Negate condition result.</td></tr><tr><td>Condition</td><td>Condition whose result is inverted.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Negate Condition</td></tr><tr><td>Condition</td><td>Docs Condition - Weektime</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Negate condition result** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Use a Global Condition

The **Use a Global Condition** type references a global condition from the tenant configuration.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Use a Global Condition** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-use-a-global-conditi">![Use a Global Condition condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/use-a-global-condition.png)<figcaption>Use a Global Condition condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Use a Global Condition.</td></tr><tr><td>Condition</td><td>Global condition to evaluate from this tenant.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Use Global Condition</td></tr><tr><td>Global condition</td><td>Docs Global Condition - Weektime</td></tr></tbody></table>

## Destinations

The global condition supplies the test. The tenant condition still defines the destinations that should run when the global test matches or does not match.

## Editing and deleting

To edit this condition, open **Docs Condition - Use a Global Condition** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Check SMS message

The **Check SMS message** type matches SMS message content.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Check SMS message** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-check-sms-message-co">![Check SMS message condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/check-sms-message.png)<figcaption>Check SMS message condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Check SMS message.</td></tr><tr><td>Message content</td><td>Text or expression used to match the SMS body.</td></tr><tr><td>Case sensitive</td><td>Requires exact case matching.</td></tr><tr><td>Exact Match</td><td>Compares exact content without filtering characters.</td></tr><tr><td>Use regex</td><td>Treats message content as a regular expression.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Check SMS Message</td></tr><tr><td>Message content</td><td>STOP</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Check SMS message** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Check if a specific channel is running

The **Check if a specific channel is running** type checks whether a channel matching the configured attributes is currently running.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Check if a specific channel is running** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-check-if-a-specific-">![Check if a specific channel is running condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/check-if-a-specific-channel-is-running.png)<figcaption>Check if a specific channel is running condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Check if a specific channel is running.</td></tr><tr><td>Channel</td><td>Channel name or pattern.</td></tr><tr><td>Context</td><td>Dialplan context to match.</td></tr><tr><td>Extension</td><td>Dialplan extension to match.</td></tr><tr><td>State</td><td>Channel state to match.</td></tr><tr><td>CallerID</td><td>Caller ID value to match.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Check Channel</td></tr><tr><td>Channel</td><td>PJSIP/100</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Check if a specific channel is running** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Multiple destination over weektime

The **Multiple destination over weektime** type routes to different destinations based on a color-coded weekly timetable.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Multiple destination over weektime** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-multiple-destination">![Multiple destination over weektime condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/multiple-destination-over-weektime.png)<figcaption>Multiple destination over weektime condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Multiple destination over weektime.</td></tr><tr><td>Color names</td><td>Labels for each timetable color.</td></tr><tr><td>Timetable</td><td>Weekly grid where time blocks are assigned to colors.</td></tr><tr><td>Destinations</td><td>Destination selected for each color.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Multiple Destination over Weektime</td></tr><tr><td>Color 1</td><td>Open hours</td></tr><tr><td>Color 2</td><td>After hours</td></tr></tbody></table>

## Destinations

This type uses one destination group for each color in the weekly timetable.

## Editing and deleting

To edit this condition, open **Docs Condition - Multiple destination over weektime** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Call Screening using a random PIN

The **Call Screening using a random PIN** type screens a call by playing a prompt and asking the caller to enter a generated PIN.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Call Screening using a random PIN** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-call-screening-using">![Call Screening using a random PIN condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/call-screening-using-a-random-pin.png)<figcaption>Call Screening using a random PIN condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Call Screening using a random PIN.</td></tr><tr><td>Welcome Message</td><td>Prompt played before PIN entry.</td></tr><tr><td>Wrong PIN Message</td><td>Prompt played after an invalid PIN.</td></tr><tr><td>Max attempts</td><td>How many failed attempts are allowed.</td></tr><tr><td>Timeout</td><td>How long to wait for digits.</td></tr><tr><td>PIN length</td><td>Length of the generated PIN.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Call Screening Random PIN</td></tr><tr><td>PIN length</td><td>4</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Call Screening using a random PIN** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Caller has already called in

The **Caller has already called in** type checks recent inbound call history for the current caller.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Caller has already called in** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-caller-has-already-c">![Caller has already called in condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/caller-has-already-called-in.png)<figcaption>Caller has already called in condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Caller has already called in.</td></tr><tr><td>Lookup days</td><td>How many days back to search.</td></tr><tr><td>Lookup hours</td><td>How many hours back to search.</td></tr><tr><td>Match number of digits</td><td>How many rightmost caller ID digits to compare.</td></tr><tr><td>Disposition</td><td>Call result filter.</td></tr><tr><td>At least</td><td>Minimum call count and optional duration rule.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Caller Already Called In</td></tr><tr><td>Lookup hours</td><td>24</td></tr><tr><td>At least</td><td>1 time</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Caller has already called in** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Caller has been called out

The **Caller has been called out** type checks recent outbound call history for the current caller.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Caller has been called out** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-caller-has-been-call">![Caller has been called out condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/caller-has-been-called-out.png)<figcaption>Caller has been called out condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Caller has been called out.</td></tr><tr><td>Lookup days</td><td>How many days back to search.</td></tr><tr><td>Lookup hours</td><td>How many hours back to search.</td></tr><tr><td>Match number of digits</td><td>How many rightmost caller ID digits to compare.</td></tr><tr><td>Disposition</td><td>Call result filter.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Caller Already Called Out</td></tr><tr><td>Lookup hours</td><td>24</td></tr><tr><td>Disposition</td><td>Answered</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Caller has been called out** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.

# Queue Callers, more than

The **Queue Callers, more than** type matches when a selected queue has more than the configured number of callers waiting.

Open **Configuration &gt; Conditions**, select **New Condition**, enter a name, choose **Queue Callers, more than** in the Type field, complete the type-specific fields, and select **Save**.

<figure id="bkmrk-queue-callers%2C-more-">![Queue Callers, more than condition edit form in the Canistracci OIL tenant.](https://manual.mirtapbx.com/uploads/images/gallery/2026-06/queue-callers-more-than.png)<figcaption>Queue Callers, more than condition edit form in the Canistracci OIL tenant.</figcaption></figure>## Fields

<table id="bkmrk-field-or-optiondescr"><thead><tr><th>Field or option</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Display name used in condition lists and selectors.</td></tr><tr><td>Type</td><td>Select Queue Callers, more than.</td></tr><tr><td>Queue</td><td>Queue to monitor.</td></tr><tr><td>More than # callers</td><td>Waiting caller threshold.</td></tr></tbody></table>

## Example

<table id="bkmrk-fieldexample-value-n"><thead><tr><th>Field</th><th>Example value</th></tr></thead><tbody><tr><td>Name</td><td>Docs Condition - Queue Callers More Than</td></tr><tr><td>Queue</td><td>Accounting</td></tr><tr><td>More than # callers</td><td>3</td></tr></tbody></table>

## Destinations

For tenant conditions, select the destinations that should run when the condition matches and when it does not match. Global conditions are referenced by tenant-level Use a Global Condition records.

## Editing and deleting

To edit this condition, open **Docs Condition - Queue Callers, more than** from the Conditions list, adjust the fields, and select **Save**. Before deleting it, check IVRs, schedules, routes, feature codes, and other call-flow objects that may reference it.