Handling Maximum Session Overflow in UCCX

[R M]

Is there a best practice for handling calls that exceed the maximum number of sessions provided in the application/trigger parameter in UCCX?

Presently I've got the script checking the position in queue and if it's in the last spot before the maximum number of sessions, it sends the caller to a CUC greeting that tells the caller to try back at another time. This seems to work, but seems imperfect.

What are the options for handling these excess calls?

Thanks!

[Tagir Temirgaliyev]

redirect busy and redirect not registered to hunt pilot

[R M]

The redirect on the CTI Route Point (for the UCCX trigger) doesn't work. When setup that way, the call still attempts to go to UCCX and the caller receives a rapid busy.