UCBC
Admin Guide

Time Conditions

7 min read

A Time Condition routes calls differently depending on the day and time they arrive — the classic example is "during business hours, ring the office; after hours and on weekends, go to voicemail." You can also use a Time Condition to route calls differently on specific holidays or date ranges.

Overview#

You manage Time Conditions from Applications > Media Settings > Time Conditions, which has two tabs:

  • Time Conditions — the list of time-based rules you've created, each one acting like a routing switch.
  • Presets — a UCBC feature for managing the built-in holiday/date shortcuts offered on every Time Condition's own condition list (covered in full below).

Each Time Condition rule checks the day/time against one or more conditions. If the call matches, it goes to that condition's own destination; if nothing matches, the call falls through to the rule's Alternate Destination.

The Time Conditions list

Screenshot needed · time-conditions-list

How to Create a Time Condition#

  1. Go to Applications > Media Settings > Time Conditions and click Add.
  2. Enter a Name and an Extension (the internal number other menus/routes will point to in order to run this check).
  3. Under Settings, build one or more Conditions. Each condition is a rule such as:
    • Day of Week — e.g. Monday through Friday.
    • Day of Month, Month, Week of Year, Week of Month — for recurring monthly/annual patterns.
    • Hour of Day or Time of Day — e.g. 9:00 AM to 5:00 PM.
    • Date and Time — an exact date/time range (for a one-off closure, etc.).
  4. For each condition group, choose the Destination that calls should go to when that condition is true (business hours destination, holiday destination, etc.). You can add several condition groups, each with its own destination — they're checked in order.
  5. If you want to use one of the built-in holiday/date shortcuts instead of building your own date rule, open the Presets section on this same page (see below), check the ones you want, and give each a Destination.
  6. Set the Alternate Destination — where a call goes if none of your conditions or presets match (this is your "false"/out-of-range fallback, e.g. after-hours voicemail).
  7. Set the Order (evaluation order relative to other dialplan rules) and make sure Enabled is checked.
  8. Save.

Setting the True/In-Range and False/Out-of-Range Destinations#

  • Every condition group (custom condition or checked preset) has its own destination — this is effectively its "true" result. The first condition group that matches wins.
  • The single Alternate Destination field is the overall "false" result — it only fires if the call didn't match any condition group or checked preset at all.
  • You can click Advanced next to the Presets list to set one shared Default Destination that's applied to every checked preset that doesn't already have its own destination set — handy when several holidays should all go to the same place (e.g. "closed" voicemail) without filling in the same destination over and over.

The Presets Tab (UCBC Custom Feature)#

Every Time Condition's own condition list offers a set of built-in holiday/date presets for your region (for example, in the USA: New Year's Day, Martin Luther King Jr. Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, Christmas Day). The underlying date rule for each one is shared platform-wide, but the Presets tab lets you customize how they appear for your own domain, and add entirely new ones of your own:

Renaming a preset for your domain#

  1. Go to Applications > Media Settings > Time Conditions > Presets.
  2. In the table, find the preset under Default Name.
  3. Type your own wording into its Custom Name for This Domain field (for example, rename a US-holiday-based preset to whatever your own locality calls that day).
  4. Leave the field blank to keep using the default name.
  5. Click Save. This only changes what the preset is called on your Time Condition screens — the underlying date/day-of-week rule behind it is unchanged.

Hiding a built-in preset#

  1. On the same Presets tab, check the Hidden box next to any built-in preset you don't want offered on your Time Condition screens.
  2. Click Save.
  3. This only hides it for your domain — it does not delete the shared, platform-wide preset, which may still be visible to other domains.

Adding a brand-new custom preset#

  1. On the Presets tab, scroll to Add Custom Preset.
  2. Enter a Name for your new preset.
  3. Click + Add Condition and build its rule: choose Day of Month, Month, or Day of Week, then pick a starting value and (optionally) an ending value to define a range.
  4. Add additional condition rows if the preset needs more than one rule (e.g. a specific month AND a specific day range).
  5. Click Add Preset. It now appears in the Presets list on this tab (so you can rename or hide it later) and on every Time Condition's own condition list, right alongside the built-in ones.

Deleting a custom preset#

  1. On the Presets tab, find your custom preset's row.
  2. Click Delete next to it and confirm.
  3. This only removes presets you added yourself — built-in presets can only be renamed or hidden, not deleted.

How to Edit a Time Condition#

  1. Go to Applications > Media Settings > Time Conditions.
  2. Click the rule's name in the list.
  3. Adjust conditions, presets, or destinations, then Save.
  4. Use the Enabled toggle in the list to quickly turn a rule on or off without opening it.

How to Delete a Time Condition#

  1. Go to Applications > Media Settings > Time Conditions.
  2. Check the box next to the rule(s) to remove.
  3. Click Delete and confirm.

Field Reference#

FieldDescription
NameA label for the Time Condition rule.
ExtensionThe internal number other routes point to in order to run this check.
ConditionThe type of day/time rule: day of week, day of month, month, week of year/month, hour of day, time of day, or an exact date and time.
Condition Value / RangeThe specific value, or start–end range, for that condition.
Destination (per condition/preset)Where a call goes when that specific condition or preset matches.
PresetsBuilt-in (and any custom) holiday/date shortcuts you can check instead of building your own date rule.
Default Destination (Advanced)A shared fallback destination applied to any checked preset that has no destination of its own.
Alternate DestinationWhere the call goes if nothing else matched — your "after hours" / default fallback.
OrderEvaluation order of this rule relative to others.
EnabledTurns the whole rule on or off.
DescriptionInternal notes about the rule.
Presets tab: Default NameThe built-in name for a region's preset (read-only).
Presets tab: Custom Name for This DomainYour own replacement name for that preset, shown only to your domain.
Presets tab: HiddenHides a built-in preset from your domain's Time Condition screens without deleting it.
Presets tab: Add Custom Preset — NameThe name of a brand-new, domain-only preset.
Presets tab: Add Custom Preset — ConditionThe date/day rule (day of month, month, or day of week, with an optional range) that defines when your custom preset applies.

Tips & Common Issues#

  • Build your "business hours" condition first and give it the normal working destination; then add holiday presets or custom date presets above/below it as needed, each pointing wherever that day should go.
  • Always set an Alternate Destination — if you leave it blank, a call that matches nothing may not route anywhere sensible.
  • If a holiday preset doesn't fit your business (wrong date for your country, or a holiday you don't observe), don't try to edit the condition directly — rename it or hide it on the Presets tab instead, or add your own custom preset with the exact dates you need.
  • Renaming or hiding a preset only affects your own domain; it never changes what other customers on the platform see.
  • Remember that the Alternate Destination only fires if literally nothing else matched — if a call is going to the wrong place, check whether an earlier condition or preset is unintentionally catching it first.
💬 Chat with Ace: SIITS AI