Genesys Cloud - Developer Community!

We have a very unique requirement from our reporting admins where they need specific codes associated with all system dispositions, as well as calls that hit an outbound predictive flow, and the customer hangs up before they are connected to an agent.

I have been tinkering with triggers that leverage a data action that inputs the codes to a....contact list...yes, a contact list.  That contact list is extracted by a third party system which uses the codes along with the conversation IDs to map interaction outcomes.  The only issue is when the customer, in that brief second, hangs up when traversing an outbound call flow associated with a predictive campaign.  I have attached a trigger I thought would work, yet every interaction initiates it.  I use a script to set the value for the attribute.  I was thinking that the conversation had to end before this trigger would analyze the conditions and take appropriate action.  If the customer hits the script, the attribute is updated, therefore the trigger should not initiate.  Anyone?

Does that attribute exist on the conversation before it gets to the script? If not, have you tried it with Exists == False?

We have a very unique requirement from our reporting admins where they need specific codes associated with all system dispositions, as well as calls that hit an outbound predictive flow, and the customer hangs up before they are connected to an agent.

I have been tinkering with triggers that leverage a data action that inputs the codes to a....contact list...yes, a contact list.  That contact list is extracted by a third party system which uses the codes along with the conversation IDs to map interaction outcomes.  The only issue is when the customer, in that brief second, hangs up when traversing an outbound call flow associated with a predictive campaign.  I have attached a trigger I thought would work, yet every interaction initiates it.  I use a script to set the value for the attribute.  I was thinking that the conversation had to end before this trigger would analyze the conditions and take appropriate action.  If the customer hits the script, the attribute is updated, therefore the trigger should not initiate.  Anyone?

Does that attribute exist on the conversation before it gets to the script? If not, have you tried it with Exists == False?

We have a very unique requirement from our reporting admins where they need specific codes associated with all system dispositions, as well as calls that hit an outbound predictive flow, and the customer hangs up before they are connected to an agent.

I have been tinkering with triggers that leverage a data action that inputs the codes to a....contact list...yes, a contact list.  That contact list is extracted by a third party system which uses the codes along with the conversation IDs to map interaction outcomes.  The only issue is when the customer, in that brief second, hangs up when traversing an outbound call flow associated with a predictive campaign.  I have attached a trigger I thought would work, yet every interaction initiates it.  I use a script to set the value for the attribute.  I was thinking that the conversation had to end before this trigger would analyze the conditions and take appropriate action.  If the customer hits the script, the attribute is updated, therefore the trigger should not initiate.  Anyone?

This would not work because it would not exist initially which would fire the trigger on every outbound call, even if it makes it to an agent.

Does that attribute exist on the conversation before it gets to the script? If not, have you tried it with Exists == False?

We have a very unique requirement from our reporting admins where they need specific codes associated with all system dispositions, as well as calls that hit an outbound predictive flow, and the customer hangs up before they are connected to an agent.

I have been tinkering with triggers that leverage a data action that inputs the codes to a....contact list...yes, a contact list.  That contact list is extracted by a third party system which uses the codes along with the conversation IDs to map interaction outcomes.  The only issue is when the customer, in that brief second, hangs up when traversing an outbound call flow associated with a predictive campaign.  I have attached a trigger I thought would work, yet every interaction initiates it.  I use a script to set the value for the attribute.  I was thinking that the conversation had to end before this trigger would analyze the conditions and take appropriate action.  If the customer hits the script, the attribute is updated, therefore the trigger should not initiate.  Anyone?

I took another look and you are using the customer.end topic, so should only evaluate when the customer disconnects anyhow...and you said it is triggering for every call as-is...so no help there whichever way you slice it.

Have you used the API Explorer to monitor the notifications coming through for a conversation to see exactly what is being sent for the two situations, one where it does reach an agent and another where it does not?

This would not work because it would not exist initially which would fire the trigger on every outbound call, even if it makes it to an agent.

Does that attribute exist on the conversation before it gets to the script? If not, have you tried it with Exists == False?

We have a very unique requirement from our reporting admins where they need specific codes associated with all system dispositions, as well as calls that hit an outbound predictive flow, and the customer hangs up before they are connected to an agent.

I have been tinkering with triggers that leverage a data action that inputs the codes to a....contact list...yes, a contact list.  That contact list is extracted by a third party system which uses the codes along with the conversation IDs to map interaction outcomes.  The only issue is when the customer, in that brief second, hangs up when traversing an outbound call flow associated with a predictive campaign.  I have attached a trigger I thought would work, yet every interaction initiates it.  I use a script to set the value for the attribute.  I was thinking that the conversation had to end before this trigger would analyze the conditions and take appropriate action.  If the customer hits the script, the attribute is updated, therefore the trigger should not initiate.  Anyone?

I took another look and you are using the customer.end topic, so should only evaluate when the customer disconnects anyhow...and you said it is triggering for every call as-is...so no help there whichever way you slice it.

Have you used the API Explorer to monitor the notifications coming through for a conversation to see exactly what is being sent for the two situations, one where it does reach an agent and another where it does not?

This would not work because it would not exist initially which would fire the trigger on every outbound call, even if it makes it to an agent.

Does that attribute exist on the conversation before it gets to the script? If not, have you tried it with Exists == False?

We have a very unique requirement from our reporting admins where they need specific codes associated with all system dispositions, as well as calls that hit an outbound predictive flow, and the customer hangs up before they are connected to an agent.

I have been tinkering with triggers that leverage a data action that inputs the codes to a....contact list...yes, a contact list.  That contact list is extracted by a third party system which uses the codes along with the conversation IDs to map interaction outcomes.  The only issue is when the customer, in that brief second, hangs up when traversing an outbound call flow associated with a predictive campaign.  I have attached a trigger I thought would work, yet every interaction initiates it.  I use a script to set the value for the attribute.  I was thinking that the conversation had to end before this trigger would analyze the conditions and take appropriate action.  If the customer hits the script, the attribute is updated, therefore the trigger should not initiate.  Anyone?