Genesys Cloud CX licence tiers explained: CX 1 to CX 4, add-ons and models

Genesys Cloud CX licensing has four layers, and it helps to separate them before comparing anything. The first is the base tier each user holds: Genesys Cloud CX 1, CX 2, CX 3 or CX 4, plus digital-only variants of CX 2 and CX 3 and a unified communications licence for people outside the contact centre. The second is add-ons, which give individual users capabilities from a higher tier without moving them up. The third is consumption: AI Experience tokens for certain AI features, and usage-based services such as telephony minutes, data storage and API calls, most of which sit inside a fair use allocation. The fourth is the licence model, which decides how users are counted and billed: named, concurrent or Hourly Interacting.

We are a Genesys referral partner and professional services company, and we do not sell licences. Commercial terms, including all pricing, come from Genesys or your reseller and are set out in your order form. What we do is help you work out which tiers, add-ons and model fit your operation, then design roles so the licences users actually consume match the ones you intended to buy. Genesys revises its packaging from time to time, so treat this guide as an explanation of the structure as published at the date shown, and confirm the detail with Genesys before you commit.

Each tier includes everything in the one below it. Genesys Cloud CX 1 is positioned for voice contact centres: inbound voice routing, speech-enabled IVR, callbacks, outbound voice campaigns, interaction recording, analytics and reporting, unified communications and knowledge. Genesys Cloud CX 2 is for omnichannel contact centres with quality assurance and compliance built in, adding digital channels such as web messaging, email and SMS, omnichannel routing and quality management evaluations. Genesys Cloud CX 3 adds full workforce engagement management: AI-powered forecasting and scheduling, capacity planning, adherence, employee performance tools such as gamification and coaching, and speech and text analytics.

Genesys Cloud CX 4 is positioned for organisations that want more AI included in the licence. It adds journey management, includes core Agent Copilot features without drawing on tokens, and includes an allocation of AI Experience tokens for every agent on top of the organisation's monthly allocation. Its published plan also lists virtual agents, social listening and engagement, Supervisor Copilot and Virtual Supervisor. The table summarises the capabilities Genesys shows for each tier; where a cell says add-on, the capability can be bought for that tier separately, and where it says tokens, use of the feature consumes AI Experience tokens.

If some or all of your users never handle voice, Genesys publishes two digital-only editions. Genesys Cloud CX 2 Digital covers digital channels, including web messaging, email, SMS and third-party messaging apps, with digital message routing, outbound campaigns, analytics, knowledge, and quality assurance and compliance. Genesys Cloud CX 3 Digital adds workforce engagement management and speech and text analytics, mirroring the step from CX 2 to CX 3. There is no digital-only equivalent of CX 1, because CX 1 is the voice tier, and none of CX 4 is published. A digital-only team that later takes calls needs a voice-capable tier, so check your channel roadmap before standardising on a digital edition.

People outside the contact centre are covered differently. Genesys offers a unified communications licence, named Communicate in the Genesys fair use policy, for employees who need calling, presence, chat and the directory but do not handle routed customer interactions. Back-office experts and colleagues who are consulted by agents are typical holders. The risk to watch is drift: if such a user is later given a role with contact centre permissions, their licence requirement rises to a CX tier, often without anyone noticing.

Add-ons let you avoid moving a whole population up a tier because a few people need one more capability. Genesys states that a digital add-on can be bought for a subset of CX 1 users, and a workforce engagement management add-on for a subset of CX 1 or CX 2 users. Other add-ons published on the Genesys pricing page are listed at the end of this section.

AI Experience tokens are the consumption unit for many AI features. Genesys measures each feature in its own unit, such as minutes or sessions for virtual agents, users for Agent Copilot and generated summaries for AI Studio, and converts that usage into tokens. Every organisation receives a monthly token allocation, which at the time of writing is larger for concurrent organisations than for named ones, and CX 4 adds tokens per agent. Usage beyond the allocation and any prepaid tokens is billed monthly in arrears, so token forecasting belongs in the business case for any AI feature. Telephony is separate from the tier: you can use Genesys Cloud Voice, or bring your own carrier with BYOC, where a monthly allotment of minutes is included under the fair use policy.

• Work Automation, for routing workitems such as back-office tasks, on all tiers
• Customised analytics, adding data warehousing, external data import and further dashboards
• CX Cloud from Genesys and Salesforce, and Unified Experience from Genesys and ServiceNow
• Hourly Interacting licences for occasional users, on all tiers
• Bring Your Own Interactions, for analysing interactions from external sources, listed for CX 3
• AppFoundry Marketplace applications and integrations, some of which are licensed separately by their providers

Under the named model, anyone who logs in during the billing period is a billable user, however briefly they were logged in, and each user is billed at the highest licence level assigned to them in that period. If more users log in than you have licences for, overage applies. Under the concurrent model, Genesys bills for the peak number of simultaneous users in the billing period, ignoring peaks shorter than 30 minutes to allow for shift changes, and again at the highest licence level users held. Concurrency is calculated within a single Genesys Cloud organisation, not across several, and if you choose concurrent then all your CX users are licensed as concurrent. Genesys states that the two models cannot be mixed, and that concurrent licences carry a premium that reflects the flexibility they give.

Hourly Interacting is intended to run alongside a named or concurrent subscription rather than replace it. A user is placed on it through a role carrying the Billing > User > hourlyInteracting permission, and is then counted only for time spent communicating or interacting, against their CX tier and any qualifying add-ons. Users with administrative or supervisory permissions are disqualified and revert to full monthly metering. Organisations still on the legacy Hourly Logged In model, which counts all logged-in time, must move to named or concurrent to use it.

In Genesys Cloud, a licence is not just a line on a contract; it follows from what a user is allowed to do. Automatic licence assignment is on by default, each role has an associated licence that reflects the permissions in it, and the licence a role uses corresponds to the highest-tier permission it contains. When you give someone a role, you are also giving them its licence. Billing then counts the highest licence level each user held during the period. One quality or workforce management permission added to a shared agent role can therefore lift an entire voice team from CX 1 to a higher tier.

That makes role design a licensing decision. We design roles by persona, keeping capabilities that drive a higher tier out of default and shared roles unless every holder needs them, and we review licence attribution after role changes and before renewals. Our App Suite includes a Permissions Auditor for this: it traces each user's tier to the permission and role responsible, sets that beside the licence Genesys has assigned and inferred, and lets an administrator rehearse a role change before making it in production. QVCCS uses it in licence reviews; the change itself always goes through the organisation's own change control.

Most organisations of any size end up with a mix of tiers rather than one. The practical method is to start from personas, not features: list each group of users, what channels they handle, whether they are forecast and scheduled, whether their interactions are evaluated, and which AI features they will use. Then map each group to the lowest tier, or tier plus add-on, that covers it, and test the result against your roadmap for the length of the contract.

Some patterns recur. A voice-only team with no workforce management stays on CX 1. A blended team that will be forecast and scheduled usually belongs on CX 3, while a voice team that only needs scheduling may be better on CX 1 with a WEM add-on. Supervisors, workforce planners and quality analysts often need a higher tier than the agents they support, because their permissions do. Where AI is central to the plan, compare the tokens your forecast usage would consume on CX 1 to CX 3 with what CX 4 includes. The steps we follow are:

1. Group users into personas by channel, workforce engagement and AI needs
2. Choose named or concurrent from rostering patterns, and identify Hourly Interacting candidates
3. Map each persona to the lowest tier, or tier plus add-on, that covers it
4. Forecast AI token consumption and telephony usage against fair use allocations
5. Design roles so each persona's permissions match its intended licence
6. Audit attributed against assigned licences after go-live and before every renewal