Series: ISV Applications

The AppFoundry partners enjoy the following benefits within Genesys Cloud, including unique product(s), permission(s), license(s), public deployment of embeddable framework implementation, branded installation card, and billing automation. Once the ISV application is approved, Genesys Cloud product management provides the following:

• Product: Represents a feature-gating mechanism for installing your ISV application.
• Permission: Represents a gating mechanism, per user, to your ISV application.
• Installation Card (Optional): Represents a Genesys Cloud installer of your ISV application.
• Public Deployment of Embeddable Framework (Optional): Represents a public-interactions window for embedding in a public web application. For example, CRM.
• License (Optional): Represents a billable item in the Genesys Cloud Billing system derived from a unique permission per user of the ISV Client application.

Each component enables enablement, billing, and/or installation automation for your ISV application.

The types of billing are as follows:

ISV client applications—usage type

The two types of usage parts available for the ISV application AppFoundry partners are as follows:

• Site license: Quantity always equals one.
• User license: Usage is based on a logged-in user (Named/Concurrent/Hourly) to Genesys Cloud and the presence of the ISV applications’ unique permission (translates to a Genesys Cloud License)

ISV client applications—metered type

The two types of metered parts available for the ISV application AppFoundry partners are as follows:

• Metered sum usage: Ideal for unit types, including minutes, API hits, visits, interactions, storage gigs, and more.
• Metered high water mark: Ideal for unit types without much fluctuation, including wallboards.

ISV client applications—mimic type

The mimic part available for the ISV application AppFoundry partners is as follows:

• User license: Usage is based on the base agent license (Named/Concurrent/Hourly) count of the entire Genesys Cloud organization. The mimic type is ideal for the ISV applications whose consumption matches the base agent license count of the Genesys Cloud organization in a 1:1 ratio.

ISV parts guidelines

For simplicity, Genesys parts follow strict guidelines for automation from customer purchase and consumption to customer invoicing. To avoid complications and delays, the ISV AppFoundry partners must follow the following guidelines:

Standard offering guidelines

1. Equate a singular Genesys Cloud Site License (aka Usage Type) within Genesys Cloud only to a singular SKU.
   • Supported example: ISV Site License ABC with only a singular SKU regardless of any Genesys Cloud user commitment.
   • Unsupported example: ISV Site License ABC with one SKU for Genesys user commitment of 100, and another SKU for Genesys Cloud user commitment of 250 and above.
2. Equate a singular Genesys Cloud User License (aka Usage Type) within Genesys Cloud only to a singular grouping of Named/Concurrent/Hourly parts, and apply discounting to a singular SKU for volume discounts.
   • Supported example: ISV License ABC is tabulated as a Named, Concurrent, or Hourly User, where each license is associated with a unique part.
   • Unsupported example: ISV License ABC has one set (Named/Concurrent/Hourly) of SKUs for user commitment quantity of up to 100 and another set (Named/Concurrent/Hourly) of SKUs for user commitment of 250 and above.
3. Equate a singular metered resource from a metered-type application within Genesys Cloud only to a singular price per unit.
   
   • Supported example: ISV Metered ABC offering has a singular SKU for metered usage (metered sum or metered highwater) of the same offering, regardless of volume commitment. A volume commitment is set on the SKU.
   • Unsupported example: ISV Metered ABC offering has multiple SKUs for metered usage (metered sum or metered high water mark) of the same offering based on volume commitment.

Combination offering guidelines

Genesys Cloud supports offerings that require or offer multiple parts.

A few examples of these types of offerings are as follows:

1. A single offering is offered in two separate consumption models.
   • Equate a singular Genesys Cloud User License (aka Usage Type) within Genesys Cloud only to a singular grouping of Named/Concurrent/Hourly parts, and apply discounting to a singular SKU for volume discounts; OR
   • ISV Metered ABC offering has a singular SKU for metered usage (metered sum or metered highwater) of the same offering, regardless of volume commitment. A minimum volume commitment is set on the SKU.
2. A single offering has a required part (aka site license) and one of the following optional or required components:
   • Named/Concurrent/Hourly SKU.
   • Metered SKUs.