I found the UI for creating schedules is a little bit misleading for some cases.
I wanted to create a rule for Saturday 4pm to Sunday 10pm. The visual placement of the drop-down menus in the lines "From" and "To" suggested to me, that I can select these two dates and times. But what really got created was a schedule "4 pm to 10 pm, on Saturday and Sunday". Maybe this behavior can be reflected in the UI by replacing the day-of-the-week drop-down menus with checkboxes.
So, Erik, would this work
So, Erik, would this work for 8-5 Monday through Friday?
Month From * to *
Day-of-Month From * to *
Day-of-Week From Monday to Friday
Hour From 8 to 17
Minute From * to *
I have been creating 5 different time ranges to cover that.
I'm not Erik... but this
I'm not Erik... but this would work at described. I messed up the schedules in the beginning too. Thinking about what TL is, I started to think "cron" and all strange results vanished. Normally when we create inbound routes, we place a "catch all" as the last rule witch points to the closed IVR. Before the last one we place the rule(s) for opening hours. The top most rules are holiday greetings and so. This way you are sure that the caller hears a greeting, even if you f..up your schedules. Unless you of course broke the catch all rule... By having a permanent holiday rule, you only have to edit the schedule (which most customers can lern to edit) and don't need to mess with the inbound route (where the customer is likely to get confused and screw up).
/Ole
well you cannot wildcard
well you cannot wildcard minutes if you did not wildcard hours.. so you have to specify the minutes. If you are wanting 8am to 5pm you need to say 8:00 to 16:59. If you say 17:00 then at 17:00:25 a call will still match true even though the receptionist is walking away from her desk. As Ole said, the best way to run a night greeting is to use the tl-allhours schedule for the night rules. That way if vacation and day don't match, the night rule will. In other words, if it isn't day, then of course its night :)
I agree the UI confuses people. Instead of viewing two rows of date it needs to be viewed as columns.
you arent making one rule that says from sunday, march 1, 8am TO friday, arpil 3, 5pm... that rule would give you insane results, for example any saturday would fail to match, any day of the month that isnt 1,2, or 3 would fail to match (like march 5th), etc.
Ive requested many times that at least some shading be done to visualize them in columns instead of rows but nothing has ever changed.
your match is calculated by comparing each column and if its true, proceeding to the next column... so lets take
* (month) * (day) mon - friday (day of week) 0800 - 1559 (time)
in this case the logic is...
month... anything matches so proceed
day... anything matches so proceed
day of week... must be between mon and friday.. its tuesday so proceed
time... must be 0800 to 1559, its 1700 so fail
a lot of people thing they can just put in this one entry to cover some range of dates when they will be closed for a holiday. When this overlaps a calendar month name, this can be a disaster.