Genesys Cloud CX Pricing: CX 1–4 Plans and Costs

Genesys Cloud CX pricing starts at $75 per named user per month on an annual commitment for its US CX 1 edition. The other publicly listed editions are CX 2 at $115, CX 3 at $155 and CX 4 at $240 per user/month, also based on an annual commitment. These are platform license baselines, not complete contact-center budgets. Telephony services, AI Experience token consumption, extra channels, integrations, premium applications, onboarding and professional services can alter total spend. A buyer should compare the complete proposed operating model, not just the four headline numbers.

Official Genesys Cloud CX prices

The associated Genesys Cloud CX profile on Toollers is the intended software entity for this pricing guide. Its public URL is not independently accessible yet and should be verified after import.

We checked the live Genesys Cloud CX pricing page on October 28, 2026 UTC. Its named-license display uses US dollars per user per month with an annual commitment. The page includes a currency selector, so a buyer's region or final quote may differ. We have not verified that a buyer can pay each of those exact amounts month by month without a longer commitment; do not mistake the displayed monthly equivalent for an unrestricted monthly subscription. Custom enterprise proposals can also change details.

These yearly amounts multiply the published monthly equivalent by 12; they exclude tax, per-minute or consumption services, add-ons and services fees. The comparison is best understood as the recurring named-seat license baseline. For example, ten agents on CX 2 imply $1,150 in monthly-equivalent core licenses or $13,800 over twelve months before other charges. Whether payment is made upfront or under another negotiated invoice schedule must be confirmed in the signed order; a monthly-equivalent price does not establish a guaranteed monthly payment option.

Genesys Cloud CX 1: voice-first at $75

CX 1 is positioned for voice contact centers. Its published plan coverage includes calls, routing, speech-enabled IVR, outbound campaigns, reporting and unified communications. This is the most economical core package in the named-seat line, but it is not a generic all-channel package. The official comparison describes digital channels and omnichannel routing as add-ons for CX 1. If a business depends on web messaging, email queues or several asynchronous channels, it should price those options explicitly before selecting the cheapest core edition.

Consider CX 1 if your main operational problem is distributing calls reliably and supervising queue performance. Build a proposal that includes the actual number of named users, the telephone carrier and numbering model, inbound and outbound volumes, recording retention, role and reporting requirements, and any integration into customer records. A voice-first center with limited digital traffic may find CX 1 appropriate; an organization with extensive digital needs could find a higher edition simpler after add-ons are counted. No universal break-even point can be inferred from the public rate card alone.

Genesys Cloud CX 2: omnichannel at $115

CX 2 adds core digital channels, omnichannel routing, knowledge functionality and quality assurance and compliance capabilities. The difference from CX 1 is $40 per named user/month on annual commitment, or $480 per named user for a twelve-month period. For 50 licensed users, the basic premium is $24,000 over a year before additional charges. That arithmetic can guide budgeting but should be weighed against the cost of buying equivalent channels and quality workflows as separate modules or tools.

Teams managing voice, email, web messaging and social service should inspect CX 2 carefully. Confirm which third-party messaging channels need AI Experience tokens, whether SMS and WhatsApp transaction charges are separately billed and how a customer identity is shared across channels. Quality-review entitlements should be checked at the supervisor and agent role level. It may be possible to equip subsets of users with additional capabilities, but the signed quote should establish the permitted mix.

Genesys Cloud CX 3: workforce engagement at $155

CX 3 adds workforce management, forecasting, scheduling, employee performance and deeper speech and text analytics. The public named-seat price is $155 per user/month on annual commitment, which is $40 above CX 2 and $80 above CX 1. For operations where labor planning, staffing adherence and interaction-quality monitoring are core disciplines, that premium may replace standalone workforce tools or improve coordination. However, a feature being included does not guarantee it works without configuration, training and analyst time.

Before choosing CX 3, document who maintains forecasts, how shrinkage and exceptions are modeled, which quality criteria supervisors use and whether historical data can be imported. Ask how many people need the full package and whether other roles can use a lower edition or subset add-on. Gene­s­­ys pricing materials permit a variety of add-ons on lower editions; an account-specific entitlement matrix can reveal a more economical mix. Do not assume that adding an advanced WEM tier automatically lowers employee costs without a measured operational case.

Genesys Cloud CX 4: AI emphasis at $240

CX 4 is listed at $240 per named user/month on annual commitment. The current pricing page highlights journey management, Agent Copilot and an additional allocation of 30 AI Experience tokens per named agent, with other capabilities from lower editions. The increment from CX 3 is $85 per user/month, or $1,020 per year per licensed named user. Its value depends on actual AI consumption, agent-assistance workflows and any reduction in separately purchased credits or modules, none of which can be determined from the price card alone.

AI economics deserve a specific model. The public page also advertises a base allowance of 250 AI Experience tokens per organization/month for named-license setups, while indicating 350 for concurrent-license setups. It uses an additional per-agent allocation for CX 4. That is not a promise that every bot, summary or interaction is free. Buyers should obtain the token schedule and unit consumption for virtual agents, predictive routing, copilots, speech analytics and message types under their chosen arrangement. Ask if token balances expire, whether overages are automatic and how administrators track them.

Named vs concurrent vs hourly-interacting licenses

These models change the cost denominator and should never be combined in a simple per-seat comparison. A named license is assigned to an identifiable individual. If 100 different people need access, that can mean 100 named users even when only 45 are active during a particular shift. A concurrent license is based on simultaneous use; the vendor says a premium applies to reflect the higher relative value. Importantly, the official FAQ states that named and concurrent license models may not be mixed as ordinary license types.

The hourly-interacting model charges for time actively handling interactions, making it potentially relevant to intermittent seasonal support roles. The public page does not give enough information to calculate a reliable universal hourly equivalent. Procurement should request included time, minute-rounding rules, eligibility, idle-time treatment, minimum commitments and management-role costs. A company that operates twelve-hour overlapping shifts could have very different economics from a day-shift operation with the same total headcount. Only a role- and concurrency-based comparison reveals whether a licensing model is attractive.

How to compare licensing scenarios responsibly

Model three staffing scenarios: typical weekday operations, peak seasonal demand and a realistic downturn. Include total employee identities, peak active users, paid supervisors, part-time agents and trainees. For a named-user illustration, 25 CX 1 users imply $1,875 in monthly-equivalent licenses, 25 CX 2 users $2,875, 25 CX 3 users $3,875, and 25 CX 4 users $6,000. These are arithmetic scenarios, not customer quotations. A concurrent-license scenario requires a separate vendor rate that includes its premium; using $75 as a concurrent license rate would be an unsupported calculation.

Digital-only editions and add-on packages

Genesys additionally presents digital-oriented Genesys Cloud CX editions. These should be discussed when teams expect few voice interactions, but they are not necessarily cheaper than every voice-inclusive option after functional requirements are considered. Use the official digital pricing information and obtain a current regional quote. Verify whether digital-only users may transfer interactions to voice licensed agents, how messaging providers are billed, and whether omnichannel analytics are consistent with the voice team.

Among likely add-ons are selected channel expansions, advanced AI options, CRM integrations, bot integrations, telephony services, partner applications and professional services. The plan matrix is explicit that CRM and case-management integration is not automatically a no-cost core inclusion just because the marketplace exists. Request a line-item list for software entitlements, usage allowances, one-time implementation and ongoing support; otherwise a nominally comparable quote could omit the most expensive part of deployment.

AI tokens, communication usage and variable costs

Cloud contact-center software has more cost drivers than a conventional SaaS subscription. Voice calls use carrier connectivity, call destinations, numbers and often recording storage. Digital messages may involve provider charges, messages sent or high-volume third-party interaction rules. AI can consume tokens for virtual agents, routing, assistance and analytics. A partner integration can charge its own subscription. Without a full expected-usage model, the least expensive license tier can produce the higher total bill if a center adds many paid channels and token-intensive workflows.

Create a cost spreadsheet with assumptions for monthly calls, total minutes, geography, queue staffing, conversation channels, outbound volume, retained recordings, CRM integration and AI events. Each line should identify its rate basis: named license, concurrent user, billed hour, telephony minute, bot event, AI token, stored media or one-time service. Do not copy free allowances across regions and editions unless confirmed for the exact contract. Ask the vendor which metering dashboards are exposed, how alerts work, and whether there are spending caps or preapproval controls for cost overruns.

Genesys Cloud CX free trial and free plan

The vendor offers a Genesys Cloud free-trial request with no credit card required according to the page. A representative contacts prospects to assess fit, and availability is restricted to specified AWS regions and countries. The trial page says qualifying users can access inbound call, email and message flows, but it does not provide a universal guarantee of unrestricted seats, countries or production telephony use. A free evaluation is not a permanent free plan, and there is no verified always-free core CX 1–4 production edition.

The uploaded Toollers record references a GCX Activate evaluation with a specific ten-user and ten-minute call limit. Those detailed limits are not established by the current public trial page we checked. Treat them as legacy or account-specific terms until Genesys confirms them in writing. Buyers should ask for trial duration, feature availability, permitted carrier setup, call minute and message limits, AI token availability, data export and expiry handling. A qualified pilot can prevent a larger procurement error, but it will not cover every integration and compliance scenario without purposeful test design.

Sample license budgets by team size

To illustrate scale without pretending to quote total cost, consider a company with 10 named agents: license-only monthly equivalents are $750 on CX 1, $1,150 on CX 2, $1,550 on CX 3 and $2,400 on CX 4. For 50 named agents, the respective figures are $3,750, $5,750, $7,750 and $12,000. For 100 named agents, they are $7,500, $11,500, $15,500 and $24,000. Each is an arithmetic multiplication of a vendor list rate by a hypothetical fixed headcount.

Annualized license-only budgets are twelve times those figures and may be paid under a contractually specified invoice schedule. Neither the monthly equivalents nor the annual totals include PSTN access, carrier transfers, extra AI tokens, messaging fees, support services, development, implementation or taxes. These examples should be copied into a quotation comparison only with prominent exclusions. A mixed shift operation may require less concurrent capacity than named identities, but the concurrent rate is not public in the same simple form, so do not calculate savings without a direct proposal.

Contract questions, support and procurement risk

Before signature, reconcile the order form with the published rate card. Confirm commitment length, billing frequency, true-up provisions, minimum paid seats, regional currency, renewal dates and any increase rights. Identify what happens if agents leave, if usage falls below forecast or if a new team needs a different edition. Ask whether implementation and ongoing support are vendor-delivered or partner-delivered, who owns configuration changes and how support service levels vary by contract. Public prices alone do not establish refunds, cancellation treatment or contract amendment rights.

For telephony migrations, confirm number-porting responsibility, carrier outage response, emergency call obligations, data-processing agreements and exit options. Recording storage, retention, deletion and export should be explicitly quoted. If the center handles sensitive customer records, security and legal sign-off should occur before loading real data into a trial tenant. Document every excluded service so that competing vendor proposals can be compared on equivalent scope and risk.

Which Genesys Cloud CX plan offers the best value?

CX 1 is the simplest candidate when voice routing is primary and optional digital channels are limited. CX 2 is often the more relevant starting point for support operations with significant chat, email and digital demand. CX 3 is worth evaluating when forecasting, scheduling and formal quality processes are required. CX 4 deserves attention when extensive agent assistance and AI usage can be demonstrated and costed. None is inherently the best buy without assessing workflows, user roles, other software commitments and total usage.

Pricing methodology and final recommendation

We recommend treating the four public rates as the first row of a more complete cost model. A credible quote should explain why the selected edition is required, list every user and privilege category, quantify telecom and digital traffic, model AI allowance and overage exposure and identify all service charges. Compare alternative ticketing or chat products only if they satisfy the actual voice and workforce requirements; a much cheaper help-desk license can be a poor substitute for an enterprise contact center.

Frequently asked questions

Sources and verification notes

Related Genesys Cloud CX articles

Review · Alternatives