AppFoundry: The Genesys Marketplace Experience

For the purposes of this post, let's assume I have PartnerOrgA who have a pairing with ClientOrgA.  PartnerOrgA has added a particular product to their reseller WHITE list.

Changes have happened that means PartnerOrgA has been brought out by PartnerOrgB and all clients, including ClientOrgA need to be paired with PartnerOrgB.  However in PartnerOrgB, the AppFoundry product ClientOrgA has been using is on the GREY list - as that is the requirement for other clients of PartnerOrgB.  At some point in time, PartnerOrgA's Genesys Cloud organisation will be closed and deleted.

How can you ensure that the product ClientOrgA is using - which was added while they were paired with PartnerOrgA - continues to run, and continues to be billed based on the WHITE list configuration?

Is there some mechanism behind the scenes for the AppFoundry team to mix grey/white list tags against a product based on client?  ie ClientOrgA still needs to use product and the commercial agreement is white list base, but ClientOrgB - a new or existing client of PartnerOrgB has commercial agreements in place based on grey list?

I suspect the same question comes up where a client moves from one Genesys partner to another, not necessarily part of the same or a taken-over entity.  How is this managed to remove impact both operationally and financially?

------------------------------
Vaun McCarthy
------------------------------

For the purposes of this post, let's assume I have PartnerOrgA who have a pairing with ClientOrgA.  PartnerOrgA has added a particular product to their reseller WHITE list.

Changes have happened that means PartnerOrgA has been brought out by PartnerOrgB and all clients, including ClientOrgA need to be paired with PartnerOrgB.  However in PartnerOrgB, the AppFoundry product ClientOrgA has been using is on the GREY list - as that is the requirement for other clients of PartnerOrgB.  At some point in time, PartnerOrgA's Genesys Cloud organisation will be closed and deleted.

How can you ensure that the product ClientOrgA is using - which was added while they were paired with PartnerOrgA - continues to run, and continues to be billed based on the WHITE list configuration?

Is there some mechanism behind the scenes for the AppFoundry team to mix grey/white list tags against a product based on client?  ie ClientOrgA still needs to use product and the commercial agreement is white list base, but ClientOrgB - a new or existing client of PartnerOrgB has commercial agreements in place based on grey list?

I suspect the same question comes up where a client moves from one Genesys partner to another, not necessarily part of the same or a taken-over entity.  How is this managed to remove impact both operationally and financially?

------------------------------
Vaun McCarthy
------------------------------

Hi, 

We cannot mix grey/white list for an individual product 

For the purposes of this post, let's assume I have PartnerOrgA who have a pairing with ClientOrgA.  PartnerOrgA has added a particular product to their reseller WHITE list.

Changes have happened that means PartnerOrgA has been brought out by PartnerOrgB and all clients, including ClientOrgA need to be paired with PartnerOrgB.  However in PartnerOrgB, the AppFoundry product ClientOrgA has been using is on the GREY list - as that is the requirement for other clients of PartnerOrgB.  At some point in time, PartnerOrgA's Genesys Cloud organisation will be closed and deleted.

How can you ensure that the product ClientOrgA is using - which was added while they were paired with PartnerOrgA - continues to run, and continues to be billed based on the WHITE list configuration?

Is there some mechanism behind the scenes for the AppFoundry team to mix grey/white list tags against a product based on client?  ie ClientOrgA still needs to use product and the commercial agreement is white list base, but ClientOrgB - a new or existing client of PartnerOrgB has commercial agreements in place based on grey list?

I suspect the same question comes up where a client moves from one Genesys partner to another, not necessarily part of the same or a taken-over entity.  How is this managed to remove impact both operationally and financially?

------------------------------
Vaun McCarthy
------------------------------