playing expected-wait-time using vector and announcements 1

[nohuhu]

i'm sure everybody knows how to do that but i'll post it here just in case. it is a subroutine vector that was used in my previous example, made using new features of call center 3.0.

    Number: 2                Name: Play EWT
Multimedia? n      Attendant Vectoring? n    Meet-me Conf? n           Lock? n
     Basic? y   EAS? y   G3V4 Enhanced? y   ANI/II-Digits? y   ASAI Routing? y
 Prompting? y   LAI? y  G3V4 Adv Route? y   CINFO? y   BSR? y   Holidays? y
 Variables? y   3.0 Enhanced? y
01 announcement 5802 (please hold the line)
02 goto step   13          if expected-wait    for call              <= 60
03 goto step   15          if expected-wait    for call              <= 120
04 goto step   17          if expected-wait    for call              <= 180
05 goto step   19          if expected-wait    for call              <= 240
06 goto step   21          if expected-wait    for call              <= 300
07 goto step   23          if expected-wait    for call              <= 360
08 goto step   25          if expected-wait    for call              <= 600
09 goto step   27          if expected-wait    for call              <= 900
10 goto step   29          if expected-wait    for call              <= 1200
11 announcement 5849 (operator will assist you in more than twenty minutes)
12 return
13 announcement 5820 (operator will assist you in a minute)
14 return
15 announcement 5821 (... two minutes)
16 return
17 announcement 5822 (... three minutes)
18 return
19 announcement 5823 (... four minutes)
20 return
21 announcement 5824 (... five minutes)
22 return
23 announcement 5825 (... six minutes)
24 return
25 announcement 5826 (... ten minutes)
26 return
27 announcement 5827 (... fifteen minutes)
28 return
29 announcement 5828 (... twenty minutes)
30 return

again, as this vector is subroutine, we are limited in number of vector steps we could use. thus discretionary time announcements: a minute, two, three, four, five, six, ten, fifteen, twenty and more than twenty minutes. practice shows that announcing exact time is more wrong than right: if we answer a caller in less time than announced, it will be taken more badly than if we answer in more time than announced. i know it sound weird, but it is. so a minute precision is just right for this purpose.
note that we're using expected-wait-time for a call so we don't need to know which splits/skills this call is queued to, the system will calculate ewt for all used splits/skills and use the shortest calculation.