The functionality in PureConnect is Handlers-based (even for Attendant-based ACD), so when an agent comes available it triggers a handler which starts the alerting. In that sense it is definitely different.
I can't remember if the In Queue Timeout event will steal a call away from the handler which is alerting the call on an agent's queue. Sorry...been too long since I have experimented with that.
------------------------------
George Ganahl GCP (Genesys Cloud), ICCE
Principal Technology Consultant
Genesys
------------------------------
Original Message:
Sent: 07-14-2020 16:18
From: Kleid G
Subject: Disregard Queue TimeOut after alerting an agent
Thanks George - Do you know if PureConnect handled this differently?
------------------------------
Kleid G
Mindsight
------------------------------
Original Message:
Sent: 07-14-2020 13:57
From: George Ganahl
Subject: Disregard Queue TimeOut after alerting an agent
Auto-answer is the only thing available which can help in the situation you describe. The call is under control of the In-Queue Call flow until an agent answers, so there is a race condition between the alert and the timeout built into the flow.
------------------------------
George Ganahl GCP (Genesys Cloud), ICCE
Principal Technology Consultant
Genesys
Original Message:
Sent: 07-14-2020 12:40
From: Kleid G
Subject: Disregard Queue TimeOut after alerting an agent
That is a good idea but is not going to work in this environment since the agents are not always ready to take a call
------------------------------
Kleid G
Mindsight
Original Message:
Sent: 07-14-2020 00:54
From: Paulo Mesquita
Subject: Disregard Queue TimeOut after alerting an agent
With PureCloud you could try to enable the auto answer.
------------------------------
Paulo Mesquita
Spark NZ Trading