Genesys Cloud - Main

Has anyone played with this and have comments on what you think about it?  I personally have found it not very impressive.  I assume the idea here is that you can have a list of a large amount of contacts and then use filters from that to feed other contact lists.  Not sure how this saves anything over just filtering as you import from your source.  Am I missing something like some really good documentation?

I looked at it briefly. It's going to save us a few extra clicks for us on creation. One time I selected the wrong zone column in my list and saved it. This looks like it will help prevent those types of human errors. 

I'm a little disappointed that we still need to upload a list to create the contact list object. I'd rather be able to use the template to create the object  with zero records and then upload the list with leads later. That way, I can create the campaign ahead of the go live even if the list isn't generated yet. I currently have to use a dummy list every time and then remember to clear it before uploading the production leads or create the list through the api. 

The importing with the filters isn't something that we'll probably use, but it seems usefully for customer moving to GC who previously uploaded one list in their old system and used filters to dial on  multiple campaigns from the single list. Instead of the customer needing to split their lists manually/programmatically pre-upload, they can use this to automatically split it to new lists. It helps work around the only one campaign dialing on a list at time. 

Has anyone played with this and have comments on what you think about it?  I personally have found it not very impressive.  I assume the idea here is that you can have a list of a large amount of contacts and then use filters from that to feed other contact lists.  Not sure how this saves anything over just filtering as you import from your source.  Am I missing something like some really good documentation?

I looked at it briefly. It's going to save us a few extra clicks for us on creation. One time I selected the wrong zone column in my list and saved it. This looks like it will help prevent those types of human errors. 

I'm a little disappointed that we still need to upload a list to create the contact list object. I'd rather be able to use the template to create the object  with zero records and then upload the list with leads later. That way, I can create the campaign ahead of the go live even if the list isn't generated yet. I currently have to use a dummy list every time and then remember to clear it before uploading the production leads or create the list through the api. 

The importing with the filters isn't something that we'll probably use, but it seems usefully for customer moving to GC who previously uploaded one list in their old system and used filters to dial on  multiple campaigns from the single list. Instead of the customer needing to split their lists manually/programmatically pre-upload, they can use this to automatically split it to new lists. It helps work around the only one campaign dialing on a list at time. 

Has anyone played with this and have comments on what you think about it?  I personally have found it not very impressive.  I assume the idea here is that you can have a list of a large amount of contacts and then use filters from that to feed other contact lists.  Not sure how this saves anything over just filtering as you import from your source.  Am I missing something like some really good documentation?

Has anyone played with this and have comments on what you think about it?  I personally have found it not very impressive.  I assume the idea here is that you can have a list of a large amount of contacts and then use filters from that to feed other contact lists.  Not sure how this saves anything over just filtering as you import from your source.  Am I missing something like some really good documentation?