SARK UCS/MVP Automation Panel

_SARK UCS/MVP _ Automation Panel is the place where closed time segments are declared.

About Automation

SAIL uses the concept of "Date Segments" to manage time. Principally, the IVR is only interested in whether the switch is in a "closed" or "open" state. IVR determines this by examining each date segment in the system. If any date segment is "true" then the system will consider itself to be in a "closed" state and it will behave accordingly.

Beginning of close period

Description - Used in conjunction with End of close period field to define the beginning of a time segment.
Permissable values - drop down - hours and minutes.
Default - * - (means no state).

End of close period

Description - Used in conjunction with Beginning of close period field to define the end of a time segment.
Permissable values - drop down - hours and minutes.
Default - * - (means no state).

Week Day of close period

Description - Used on its own to define a day-of-week segment.
Permissable values - drop down - monday thru sunday.
Default - * - (means no state).

Date of close period

Description - Used in conjunction with Month of close period to define a date segment.
Permissable values - drop down - dates of month.
Default - * - (means no state).

Month of close period

Description - Used in conjunction with Date of close period to define a date segment.
Permissable values - drop down - months of year.
Default - * - (means no state).

How SAIL processes your Date Segments

Each time a call comes in to the exchange then, provided the open/closed master override is set to AUTO (its default setting), each Date Segment rule is checked against the calendar and clock to see if we are closed (SARK actually uses a mechanism called MTIME to do this).

If any of the rules are true then the PBX will choose the "Closed Inbound Route" in the inbound true, otherwise the PBX will choose the "Open Inbound Route".

Time segments can be overriden by manually setting the PBX to CLOSED (*31*) or OPEN (*32*). If it is OPEN, then control is handed to the Open Inbound Route. Finally, if the PBX override is CLOSED, then the PBX will hand the call to the Closed Inbound Route. To set the system back to AUTO, use *30*.

How to create a Date Segment.

This can be a little confusing until you get your head around how it works. There are essentially three types of closed period you can define here; - one which goes along the lines of, "We're closed every sunday", another which goes, "We're closed every day between 6:00PM and 8:30AM", and another which goes, "We're closed on Christmas day". You can also just manually throw the Open/Closed master override switch (*31* and *32* privileged operator command) at any time and force the system into a CLOSED or OPEN state. This can be useful if, for example, you decide to open on a day when you're normally closed. Rather than change the rules, you can just throw the master OPEN switch by entering *32* at the operator extension and the date segment rules will be ignored.

Examples.

To say, "We're closed every Sunday", Put "Sun" in the weekday field and put asterisks in all the other fields.

To say, "We're closed every evening between 6:00PM and 8:30AM", put "18:00" in the beginning hour field, and "08:30" in the end hour field. Put asterisks in all the other fields.

To say, "We're closed on Wednesday afternoons", Put "Wed" in the weekday field, put "13:00" (or whatever time you close) in the beginning hour field, "17:30" (or whenever, as long as it overlaps the evening close time) in the end hour field and put asterisks in all the other fields.

To say, "We're closed on Christmas Day", Put "25" in the date field and put "dec" in the month field. Put asterisks in all the other fields.

You can have as many of these rules as you like and it doesn't matter if they overlap each other as long as they don't overlap a date and time when you are actually open!