Genesys Cloud - Main

I would create a trigger that looks for that inbound queue or queues and have a workflow to look for the wrap-up code on the conversation.  You can then run a data action to look for the contact in the contact lists and then mark as not callable.  You will need several data actions to accomplish this and you will probably have to have all calls for those queues go through the workflow, so check for the wrap-up right up front and let all other calls exit out of the workflow.  

I would create a trigger that looks for that inbound queue or queues and have a workflow to look for the wrap-up code on the conversation.  You can then run a data action to look for the contact in the contact lists and then mark as not callable.  You will need several data actions to accomplish this and you will probably have to have all calls for those queues go through the workflow, so check for the wrap-up right up front and let all other calls exit out of the workflow.  

True if you are mixing contacts amongst several list.  Then you would need a way to know what campaigns where the contact is used.  

I would create a trigger that looks for that inbound queue or queues and have a workflow to look for the wrap-up code on the conversation.  You can then run a data action to look for the contact in the contact lists and then mark as not callable.  You will need several data actions to accomplish this and you will probably have to have all calls for those queues go through the workflow, so check for the wrap-up right up front and let all other calls exit out of the workflow.  

An alternate route would be to use the trigger concept Robert mentioned and add an entry into a DNC table via API (DNC must be assigned to each campaign). That would prevent further calls to that number without having to mine all the contact lists and attempt to update records. 

DNC records can be permanent or configured with an expiration date.

True if you are mixing contacts amongst several list.  Then you would need a way to know what campaigns where the contact is used.  

I would create a trigger that looks for that inbound queue or queues and have a workflow to look for the wrap-up code on the conversation.  You can then run a data action to look for the contact in the contact lists and then mark as not callable.  You will need several data actions to accomplish this and you will probably have to have all calls for those queues go through the workflow, so check for the wrap-up right up front and let all other calls exit out of the workflow.  

An alternate route would be to use the trigger concept Robert mentioned and add an entry into a DNC table via API (DNC must be assigned to each campaign). That would prevent further calls to that number without having to mine all the contact lists and attempt to update records. 

DNC records can be permanent or configured with an expiration date.

True if you are mixing contacts amongst several list.  Then you would need a way to know what campaigns where the contact is used.  

I would create a trigger that looks for that inbound queue or queues and have a workflow to look for the wrap-up code on the conversation.  You can then run a data action to look for the contact in the contact lists and then mark as not callable.  You will need several data actions to accomplish this and you will probably have to have all calls for those queues go through the workflow, so check for the wrap-up right up front and let all other calls exit out of the workflow.