Impact of "Collect Digits" following a "Queue to Skill" vect 1

[SignalCorpNCO]

My question is regarding a "collect # digits after announcement ####" step following a "queue-to skill ### pri x" and the impact the collect digits step has on the queue-to skill step.

Seems like I recall something like the collect digits will nullify the queue to step or something like that, but I'm not exactly sure if this is the case. If it is, would/ should another queue-to step be include following the collect digits?

Any input/ directection will be greatly appreciated; thanks in advance.

Here's an example - after the queue step, caller gets the option to dial their party by name (if digit = #), or dial the known extension; (it's assumed that) else, wait for next availiable agent.

...
04 queue-to skill ## pri h
05 collect # digits after announcement #### for none
06 route-to number #### with cov y if digit = #
07 route-to digits with coverage y
08 wait-time 30 secs hearing music
...

Signal Corp NCO

“To invent, you need a good imagination and a pile of junk.”

Thomas A. Edison

 

[Stinney]

Collect digits won't remove the call from queue.

Routing the call to another VDN, Vector, Extension, will take the call out of queue.

- Stinney

Favorite all too common vendor responses: "We've never seen this issue before." AND "No one's ever wanted to use it like that before.

 

[SF0751]

However, if the call is queued before the digits are requested/collected, you stand a chance of the call being answered before the caller can enter any digits.

Susan
“Before you criticize someone, you should walk a mile in their shoes.
Then, when you criticize them, you are a mile away ...
and you have their shoes.”

 

[inerguard]

if you do a goto vector xx at step xx the call control will still stay with the original vector and keep the call in the queue. You then do a RETURN command to go back to the original vector.


[Started on Version 3 software 15 years a go]