Hello,

has anyone tried to use an API call to detect a newly originating outbound call and based on some parameters rerouting it to a predefined announcement? 

In other words, if there a call placed by Agent A to number XXX-XXX-XXXX but agent forgets to specify an outbound queue I would like to intercept the call prior to it reaching the client and play an announcement asking them to select a queue and try again. 

I tried to do it with triggers and data actions and it was a no-go. 

I was able to use an API call to detect an outbound call and disconnect it; however, it messes up reporting and confuses the hell out of the agent. Thus a glimmer of hope that perhaps I can somehow change the destination address. If not, then perhaps add an announcement as a third party and then kill the outbound leg? 

Take a look at this blueprint in the Developer Center to get you started. You'll have to modify to suit your needs:

https://developer.genesys.cloud/blueprints/terminate-voice-calls-with-no-queue/

Hello,

has anyone tried to use an API call to detect a newly originating outbound call and based on some parameters rerouting it to a predefined announcement? 

In other words, if there a call placed by Agent A to number XXX-XXX-XXXX but agent forgets to specify an outbound queue I would like to intercept the call prior to it reaching the client and play an announcement asking them to select a queue and try again. 

I tried to do it with triggers and data actions and it was a no-go. 

I was able to use an API call to detect an outbound call and disconnect it; however, it messes up reporting and confuses the hell out of the agent. Thus a glimmer of hope that perhaps I can somehow change the destination address. If not, then perhaps add an announcement as a third party and then kill the outbound leg? 

The issue I had with that Blueprint was whilst it terminates the call, the customer's phone would briefly ring before immediately terminating essentially pranking them.  

Take a look at this blueprint in the Developer Center to get you started. You'll have to modify to suit your needs:

https://developer.genesys.cloud/blueprints/terminate-voice-calls-with-no-queue/

Hello,

has anyone tried to use an API call to detect a newly originating outbound call and based on some parameters rerouting it to a predefined announcement? 

In other words, if there a call placed by Agent A to number XXX-XXX-XXXX but agent forgets to specify an outbound queue I would like to intercept the call prior to it reaching the client and play an announcement asking them to select a queue and try again. 

I tried to do it with triggers and data actions and it was a no-go. 

I was able to use an API call to detect an outbound call and disconnect it; however, it messes up reporting and confuses the hell out of the agent. Thus a glimmer of hope that perhaps I can somehow change the destination address. If not, then perhaps add an announcement as a third party and then kill the outbound leg? 

The issue I had with that Blueprint was whilst it terminates the call, the customer's phone would briefly ring before immediately terminating essentially pranking them.  

Take a look at this blueprint in the Developer Center to get you started. You'll have to modify to suit your needs:

https://developer.genesys.cloud/blueprints/terminate-voice-calls-with-no-queue/

Hello,

has anyone tried to use an API call to detect a newly originating outbound call and based on some parameters rerouting it to a predefined announcement? 

In other words, if there a call placed by Agent A to number XXX-XXX-XXXX but agent forgets to specify an outbound queue I would like to intercept the call prior to it reaching the client and play an announcement asking them to select a queue and try again. 

I tried to do it with triggers and data actions and it was a no-go. 

I was able to use an API call to detect an outbound call and disconnect it; however, it messes up reporting and confuses the hell out of the agent. Thus a glimmer of hope that perhaps I can somehow change the destination address. If not, then perhaps add an announcement as a third party and then kill the outbound leg?