Genesys Pricing: Genesys Cloud CX Pricing per Seat and the 15 Agent Dialer Minimum

Genesys publishes list prices, which puts it ahead of most of the contact center market, but the published number is only one of three licence models it sells and it is not the number that decides your bill. Genesys Cloud CX lists at $75, $115, $155 and $240 per named user per month billed annually, and all four tiers include outbound campaigns. The figure that actually gates outbound teams sits in the documentation rather than on the pricing page: Genesys recommends at least 15 agents in a predictive dialing campaign. All figures read from genesys.com/pricing and the Genesys Cloud Resource Center on September 3, 2026.

Genesys is one of the few enterprise contact center vendors that will show you a price without a sales call. Five9 publishes two of its five tiers. NICE publishes nothing. Convoso publishes nothing. So the fact that genesys.com/pricing renders four tiers with dollar figures next to them is genuinely useful, and it is worth understanding properly rather than copying the smallest number into a budget line.

Three things on that page and in the documentation behind it change the arithmetic. Here they are in the order they will hit you.

How much does Genesys Cloud CX cost?

Four tiers, priced per user per month on annual billing. The page rendered these figures in US dollars on September 3, 2026, with a currency selector offering USD, CAD, GBP, EUR, JPY, AUD, NZD and ZAR.

Tier	Price per user/month, billed annually	What Genesys says it is for	Outbound campaigns included
Genesys Cloud CX 1	$75	Voice contact centers and associate users	Yes
Genesys Cloud CX 2	$115	Omnichannel, with quality assurance and compliance built in	Yes
Genesys Cloud CX 3	$155	Omnichannel with full workforce engagement management	Yes
Genesys Cloud CX 4	$240	Teams that want more AI, including 30 AI Experience tokens per named agent	Yes

The useful detail for an outbound team is in that last column. Outbound campaigns are listed as included on every tier, including CX 1 at $75. So are voice and digital interaction recording, screen recording, speech-enabled IVR, predictive routing, Agent Copilot, speech and text analytics, and a native voicebot. The step from CX 1 to CX 2 buys digital channels, omnichannel routing, quality assurance and knowledge management. Those are real capabilities, and a team whose entire job is dialing a list may not use any of them.

At 15 agents, that $40 per seat difference is $600 a month, or $7,200 a year. Worth checking whether you need it before it lands in the contract.

One caveat on all four numbers: every tier button on the page says "Get custom pricing". The list price is a starting point for a negotiation, not a checkout price.

Genesys named, concurrent and hourly licensing

This is the part of the page most summaries skip, and it is the single most valuable thing on it. Genesys offers three licence types, and describes them in its own words as follows.

Licence type	Genesys' description	Who it suits	Published rate
Named	License tied to a specific, identifiable user	Teams where every rep needs their own persistent login	Yes: $75 to $240
Concurrent	License based on simultaneous active usage	Multi-shift operations, where 60 staff never exceed 20 on the phone at once	Not published
Hourly Interacting	Charges only for time spent handling interactions	Campaigns that run part of the day, or seasonal and overflow work	Not published

The $75 to $240 figures are Named prices. Concurrent and Hourly Interacting are offered as licence types with no rate on the page, so you have to ask for them, and plenty of buyers never learn they exist.

Work out whether they matter for your operation before the call. A named seat bills for the whole month regardless of use. An outbound campaign that dials four hours a day, five days a week, is on the phone for roughly a fifth of the hours in a month. If Hourly Interacting is priced anywhere near proportionally, that is the difference between paying for capacity and paying for calls. It is also the closest thing in the enterprise market to how per-minute AI voice platforms bill, which we broke down across nine of them on our AI voice agent pricing page.

Concurrent licensing has its own trap, and Five9 documents it more plainly than Genesys does. Five9's pricing page states that its prices are per concurrent user, and separately that its workforce engagement tooling is offered on a named basis, so when named seats required exceed concurrent seats sold, the difference is sold as add-ons. Fifty concurrent platform seats spread across 120 staff can therefore mean 120 workforce licences. Ask the same question of any concurrent quote you receive.

Does Genesys have a predictive dialer, and how many agents does it need?

Yes, and it documents six outbound dialing modes: Preview, Progressive, Power, Predictive, Agentless and External calling. The one to read carefully is Predictive, because Genesys attaches a minimum to it.

From its own dialing modes article: "Due to the difficulty of calculating average handle time, after-call time, idle time, and contact rate for a small sample size, we recommend using at least 15 agents in a campaign using the predictive dialing mode." For Power mode the same article recommends at least 10 to 15 agents.

Then it adds the caveat that catches blended teams: "If agents log in to other campaigns, they are not 'whole agents' in any one campaign. For example, if 20 agents log in to both Campaign A and Campaign B, each of these campaigns effectively have only 10 agents, which is under the recommended minimum for an accurate predictive algorithm."

Read that as a purchasing constraint and the price list changes shape. Fifteen CX 1 seats at $75 is $1,125 a month, or $13,500 a year, before a single minute of carrier traffic. Fifteen CX 4 seats is $3,600 a month, or $43,200 a year. The $75 headline is real, but it is not what predictive dialing on Genesys costs.

Configuration	Monthly, named licences	Annual	Note
15 x CX 1 at $75	$1,125	$13,500	The practical entry point for predictive dialing on Genesys
15 x CX 2 at $115	$1,725	$20,700	Adds digital channels and quality assurance an outbound-only team may not use
15 x CX 4 at $240	$3,600	$43,200	Includes 450 AI Experience tokens a month on top of the base org allocation
30 x CX 1 at $75, two campaigns	$2,250	$27,000	What it takes for both campaigns to clear the 15 whole-agent recommendation

Note the last row. Because agents split across campaigns count as partial agents in each, a team running two simultaneous predictive campaigns needs roughly 30 dialing reps, not 15 that switch between them. Our math, on Genesys' published figures, on September 3, 2026.

That is a hiring plan as much as a software decision, and it is the part that gets underestimated. Staffing 15 to 30 dialing seats in a market with high contact center turnover means running a continuous funnel of applicants, which is its own operational load before anyone touches the dialer. Software that reads every inbound resume against the criteria you set takes more time out of that process than any pacing algorithm will give back.

Why the 15 agent minimum exists: abandonment is regulated

A predictive dialer places calls before a rep is free, using a model of handle time and contact rate to guess when one will be. Genesys describes its version as a patented stage-based algorithm fed by average handle time, after-call time, idle time, the stage setting on the agent script and historical contact rate. Guess high and reps sit idle. Guess low and a live person answers with nobody to talk to.

That second failure has a legal ceiling. Under the FTC's Telemarketing Sales Rule at 16 CFR 310.4(b)(1)(iv), a call counts as abandoned if a person answers and is not connected to a sales representative within two seconds of completing their greeting, and the safe harbor requires abandoning no more than three percent of all calls answered by a person, measured over a single campaign if it runs under 30 days, or separately over each successive 30-day period. Three percent is a small budget to run a guessing algorithm against with a thin sample.

Which is why Abandon Rate appears as a configurable campaign property on Power and Predictive campaigns in Genesys and not on Preview or Progressive. Progressive dials one contact per available agent and offers a precise mode that reserves the agent before placing the call, which Genesys notes decreases abandonment risk further because reserved agents cannot be pulled onto an inbound call mid-dial. Preview eliminates abandonment entirely, at the cost of being the least efficient mode.

If you have fewer than ten dialing reps, the honest read is that progressive or power will give you most of the throughput with structurally less exposure. We set the two side by side in predictive dialer versus power dialer.

The escape hatch worth knowing about: External calling mode

Genesys' sixth dialing mode is one almost nobody discusses, and it is revealing. In Genesys' description, External calling exists so that "the Outbound campaign uses a third-party desktop dialer for Telephone Customer Protection Act (TCPA) compliance". The rep reviews the contact record inside Genesys, copies the number, dials it with a separate tool, then returns to Genesys to wrap up.

Genesys lists the downsides itself: it is the least efficient mode, the preview timer cannot be enabled, and there is a "lack of call-detail tracking and recording of calls dialed with a third-party desktop dialer". So it is a legitimate configuration for teams whose counsel wants a human finger on every dial, and it gives up call recording and call detail to get there. Worth knowing it is available, and worth knowing what it costs you operationally before someone proposes it as the compliance answer.

What the licence does not include

Three cost lines sit outside the per-seat figure and all three are easy to miss in a first budget.

Telephony is the obvious one. Genesys notes that usage-based pricing may apply, and carrier minutes, DID rental and the numbers you dial from are their own line whichever contact center platform you buy.

AI consumption is the newer one. Genesys Cloud CX 4 includes 30 AI Experience tokens per named agent per month, on top of a base allocation the page describes as 250 named and 350 concurrent tokens per organization per month, with additional tokens available separately. That is a consumption meter living inside a per-seat contract, which means your forecast needs two models rather than one. If usage climbs, the seat price stops being the whole story.

Storage and retention is the quiet one. Recording retention, transcript access and what happens to the archive at the end of the contract are worth pinning down in writing, because in this category they are frequently tier features rather than settings.

Who Genesys Cloud CX is right for

Genesys is a strong fit if you already run, or are about to run, a real contact center: inbound and outbound blended, 15 or more agents on the phone, workforce management to schedule, quality assurance to run, and a genuine need for omnichannel routing. Its outbound documentation is among the most honest in the market, and the fact that it publishes both list prices and its own dialing-mode minimums says something about how it sells.

It is the wrong fit if you have six SDRs and a list. At that size you are paying enterprise per-seat pricing for a pacing algorithm Genesys itself tells you will not have enough data to work. A small-team dialer priced per agent from one seat is a better match, and we put the published prices side by side, including the deployment models, on cloud based auto dialer and hosted predictive dialer pricing and by dialing mode on predictive dialer software.

And if the constraint is not pacing at all but the number of conversations six reps can physically have in a day, the seat-count question has a different answer. An AI SDR that holds the outbound conversation itself has no agent queue to pace against, so there is no 15 agent floor, no concurrency licence to size, and no three percent abandonment budget to manage. That is a different product from a dialer, and it is worth pricing as one.

How we sourced these figures

Tier prices and licence types were read from genesys.com/pricing on September 3, 2026, rendered in US dollars. Dialing modes, the 15 agent and 10 to 15 agent recommendations, the whole-agent caveat and the External calling description were read from the Genesys Cloud Resource Center articles on dialing modes and campaign properties by dialing mode the same day. The Five9 figures were read from Five9's own pricing page on September 1, 2026. The abandonment rule is 16 CFR 310.4(b)(1)(iv). Every arithmetic line labelled as ours is our own calculation on those published figures, and vendors change prices without notice, so check the source page before you sign anything.