The following vector example explains how the Time of Day (TOD) and Day of the Week (DOW) variables can be used for call center business hours to control call processing in a desired manner.

 1. goto step 30 if T < O     				[if tod is earlier than 0700 hours, go to the out of hours treatment]
 2. goto step  8 if T < W 					[if tod is earlier than 1600 (earliest possible closing time), working hours apply.
														Continue with step 8]
 3. goto step 30 if D = 1      				[if dow is Sunday, go to the out of hours treatment]
 4. goto step 30 if D = 7 					[if dow is Saturday, go to the out of hours treatment]
 5. goto step  8 if T < F 					[if tod is earlier than 2100 (Friday close time), working hours apply]
 6. goto step 30 if D = 6     				[if tod is later than 2100 (as determined by the preceding step), and dow is Friday, 
														go to the out of hours treatment]
 7. goto step 30 if T > L     				[if tod is later than 2300, go to the out of hours treatment]
 8. goto step 31 if holiday in table 8  [based on the outcome of all preceding steps, working hours apply unless today is a 
														holiday]
 9.  announcement 16549 [Please wait for the next available agent]
 10. consider skill 80 pri m adjust by 0
 11. consider location 16 adjust by 10
 12. queue-to best
 13. goto step 30 if staffed agents in skill 80 = 0
 14. wait-time 2 secs hearing silence
....
....
30. announcement 18465 [Please call again during regular business hours]
31. closed for holiday treatment

In the vector example, tod, dow and global collect variables control the call process flow by testing the call time and day values against a series of time windows that represent possible ranges of operational hours for the call center.

Steps 1 and 2 determine whether the time is within the minimum window of operational hours common to all work days, which is currently defined as 0700 to 1600 hours.

Step 1 tests whether the time is earlier than the 0700 opening time that is common to every day of the week (T < O). If the time is earlier than 0700, vector processing branches to the out of hours treatment at step 30. Otherwise, control passes to step 2.

Step 2 tests whether the time is earlier than the earliest possible closing time for any day of the week, which is 1600 on weekend days (T < W). If so, the call time is within the range of work hours that are common to all days of the week, and processing branches to step 8, which checks for a holiday before processing goes through the series of consider and queue-to best steps that are included in steps 9 through 12. Otherwise, vector processing goes to step 3 for further assessment.

Steps 3 and 4 then test whether the current day is Saturday (dow = 7) or Sunday (dow = 1). When either case is true, call control passes to the out of hours treatment provided at step 30. Otherwise, the call control passes to step 5 for further assessment.

Step 5 tests whether the time is earlier than the Friday closing time (T < F). If so, the current time is within the normal range of operating hours for Monday through Friday, and call processing branches to steps 8 through 12 for in-hours treatment. Otherwise, call vectoring goes to step 6 for further assessment.

Step 6 tests whether the day is Friday (dow = 6). If so, processing goes to out of hours treatment at step 30. Otherwise, call vectoring continues at step 7.

Step 7 completes the assessment of possible time windows by testing whether the tod is later than the latest possible closing time of 2300 hours on Monday through Thursday (T < L). If so, the call is directed the out of hours treatment provided at step 30. Otherwise, the time falls within normal work hours for Monday through Thursday and processing goes to steps 8 through 12 for in-hours treatment.