Genesys Cloud CX vs VICIdial: the license model is the decision

Compare the license model, not just the sticker price

Pick a representative workflow and have both products demonstrate it with fictional data. Compare the required licenses, integrations, support responsibilities and export format using current written terms.

Genesys describes named, concurrent and Hourly Interacting license models on its pricing page. The page checked November 4, 2026 says displayed prices assume annual commitment and usage-based charges may apply. Request a model-specific written quote for your region and requirements.

This is a licensing-model comparison, not a verdict. Genesys Cloud CX is a cloud contact-center-as-a-service (CCaaS) platform -- CCaaS being the general term for contact-center software sold as a hosted subscription rather than software you install yourself -- and CX in its name is short for customer experience. This article does not rank the two products, state a VICIdial total-cost figure, or claim what any Genesys tier includes beyond its published pricing and license terms; it compares how each vendor's licensing structure responds to a real staffing pattern, specifically a shift-based floor where headcount and simultaneous logins are two different numbers.

In plain language: an agent is the person logged into a contact center seat taking calls, whether that seat is a VICIdial agent screen or a Genesys Cloud CX desktop; a campaign is one calling project -- which leads get dialed, by which agents, under which settings; a carrier is the phone company that carries a call to the public telephone network; a channel is one simultaneous call path a system can carry; a disposition is the outcome code an agent saves after a call, such as SALE or NOT INTERESTED; and dial level is the predictive-dialing setting that controls how many lines a system dials per available agent, a VICIdial concept with no direct equivalent in a licensed-seat CCaaS platform.

• Read every Genesys figure from genesys.com/pricing yourself; this article dates every number to August 5, 2026.
• Confirm the current named and concurrent license rules in the written quote; the terms cited here are from August 2026.
• Measure your own distinct-agent and peak-concurrency numbers before either vendor conversation.

Compare Genesys tiers and license models

Genesys lists Cloud CX tiers and model-specific pricing on its official page. Select your currency, license model and required capabilities, then ask for a current written quote; displayed prices assume an annual commitment.

The page distinguishes named users, concurrent active users and Hourly Interacting usage. Its FAQ says named and concurrent models may not be mixed; confirm how this applies to your account and contract.

Do not apply a displayed named-user rate to a concurrent or hourly estimate. Ask for the specific unit price, term, minimums, feature inclusions and any usage charges.

• Reconfirm price, currency, and license-model wording against the live Genesys page before a purchase.
• Do not assume tier contents beyond price and license model from this article; that was not fetched here.
• Note that Hourly Interacting has no published rate, unlike the four named/concurrent tiers.

Named vs. concurrent: the question a dialer operator actually has to answer

Genesys describes named licensing as tied to an identifiable user and concurrent licensing as based on simultaneous active usage. Ask the vendor how reassignment, session accounting and billing periods work in your proposed contract.

That distinction is close to meaningless for an office running one eight-hour shift with little turnover, because named headcount and peak concurrency end up close to the same number anyway. It is not close to meaningless for a contact center running around the clock across time zones, or a business process outsourcer (BPO) with far more staff on the roster than seats filled at any one moment -- exactly the staffing pattern a predictive dialer is usually built for. There, named licensing prices the roster; concurrent licensing prices the busiest shift.

The pricing FAQ describes a concurrent premium and says named and concurrent models may not be mixed. Confirm the exact scope and rates in your written offer; use a verified roster and measured simultaneous sessions for the comparison.

WORKED EXAMPLE -- ONE 24-HOUR, THREE-SHIFT FLOOR Employees on payroll who take at least one call somewhere in the month: 90Highest number of them logged in at the same moment, any shift, measured not assumed: 40 Named-license math  A named license is assigned to a person, not a login slot, so it stays assigned whether  that person is on shift, on break, or off the clock entirely.  90 people who log in somewhere across the month need 90 named licenses, not 40, because  the license tracks the person, not the moment they are logged in. Concurrent-license math  A concurrent license is drawn from a shared pool for the length of one session and  returned to the pool at logout, so the pool only has to cover the busiest moment across  all three shifts, not the whole roster.  90 people sharing a 40-seat concurrent pool works, provided every shift's peak was  actually measured -- and Genesys prices a concurrent seat at a premium over the named  rate for exactly that flexibility. The crossover  Named licensing suits a floor where most of the 90 are logged in most of the time, so  the named count and the concurrent peak sit close together.  Concurrent licensing suits a floor where the roster is much larger than any single  shift's peak -- the normal shape of a three-shift operation with real turnover.  Named and concurrent models cannot be mixed on one Genesys account, so this is one  either/or choice for the whole floor, not a shift-by-shift one. 

• Compute your own distinct-agent and peak-concurrency numbers before naming a preferred license model.
• Remember Genesys does not mix named and concurrent on one account.
• Treat the concurrent premium as real but unpublished; get a current quote rather than assuming a multiplier.

The third option: paying for interaction time instead of a seat

Genesys describes Hourly Interacting as usage-based licensing for time spent actively handling customer interactions. Request its current unit price, rounding, eligibility, minimums and any additional charges; do not assume it has no other fees.

Compare the vendor’s definition of interaction time with your verified workload and carrier billing. Logged call duration alone is not necessarily the same billable unit.

VICIdial's side: no seat license, a hardware ceiling instead

VICIdial charges nothing per seat, per name, or per concurrent session, because there is no license to buy: it is self-hosted, open source software, and every agent who logs in does so against capacity the operator already owns. There is no named-versus-concurrent decision to make on the VICIdial side, because there is no license model of any kind -- the trade a VICIdial operator makes instead is owning the server, the carrier relationship, patching, backups, security, and upgrades in exchange for not paying anyone per seat.

That does not mean VICIdial capacity is unlimited; it means the ceiling moves from a licensing model to a hardware one. The configured Asterisk RTP range is one possible media constraint; CPU, network, codec processing, carrier limits and other resources can also limit capacity. The width of that range is a per-install setting, not a published constant -- check rtpstart and rtpend in /etc/asterisk/rtp.conf on your own server before assuming a number for it.

A media-port range is a technical resource constraint, not a count of licensed people. The relationship between calls, channels and ports depends on the call path and configuration. The guide titled Scaling VICIdial: designing a multi-server cluster for 500+ agents works through what happens once a single box's ceiling is not enough -- splitting database, dialer, and Asterisk roles across multiple servers rather than raising one number on one box -- which is the self-hosted answer to the same problem a Genesys buyer solves by paying for more concurrent licenses.

• Confirm your own rtpstart/rtpend and firewall range on your own server; this article does not assume a number for either.
• Record rtpstart, rtpend and the corresponding firewall policy. Any change needs a tested network and media plan; moving both endpoints upward does not necessarily enlarge the range.
• Treat the multi-server cluster guide as the next step once one box's ceiling is the real constraint.

Use outbound log counts as context, then measure session overlap

The named-versus-concurrent decision, and the VICIdial capacity-versus-headcount question right alongside it, both come down to the same two measurements: how many distinct people log in over a representative period, and the highest number of them logged in at the same instant. Guessing either number in a vendor conversation is how an operator ends up licensed for the wrong shape of staffing.

vicidial_log can count users associated with outbound call rows in a window; it cannot establish total roster size or simultaneous logins. Use a verified roster and session-interval data for licensing, and keep raw customer activity private.

For the local Genesys comparison inventory, if the linked option file is root-owned mode 600, an authorized administrator can start the client with sudo mysql --defaults-file=/etc/vicidial-readonly.cnf, then run SELECT CURRENT_USER(), DATABASE(); and confirm the intended read-only account and schema before these queries. Do not expose or copy its credentials.

1. Obtain complete authorized login and logout intervals for the representative period, including sessions spanning its boundaries.
2. Merge overlapping intervals for the same user, sort session start and end events, and treat each interval as start-inclusive and end-exclusive.
3. Track the simultaneous count after each event; the maximum is the observed peak. Record collection gaps and do not claim an exact peak if sessions are missing.
4. Use a verified roster for named licenses; compare both quantities with the vendor’s written licensing rules.

SELECT COUNT(DISTINCT user) AS distinct_agents_last_30_daysFROM vicidial_logWHERE campaign_id = '<CAMPAIGN_ID>'  AND call_date >= DATE_SUB(NOW(), INTERVAL 30 DAY); SELECT DATE_FORMAT(call_date,'%Y-%m-%d %H:00') AS hour_bucket, COUNT(DISTINCT user) AS agents_active_this_hourFROM vicidial_logWHERE campaign_id = '<CAMPAIGN_ID>'  AND call_date >= DATE_SUB(NOW(), INTERVAL 30 DAY)GROUP BY hour_bucketORDER BY agents_active_this_hour DESCLIMIT 5;

• Run both statements against a read-only account, not a production write account.
• Scope both queries to the same rolling 30-day window before comparing the two numbers.
• On your own install, replace the fixture campaign filter with your real one before trusting either count.

What to weigh next, without a vendor verdict

Request model-specific named, concurrent and Hourly Interacting prices and conditions. Compare them with dated self-hosted hosting, carrier, storage, support and staffing costs over the same period.

If you are weighing what it costs to own that server yourself, the guide titled VICIdial VPS requirements and cost: separate a lab floor from production capacity works through the same sizing question a VICIdial operator faces before any licensing conversation. If owning the box is the part you would rather not do, the guide titled Managed VICIdial hosting vs self-hosting: a decision framework, not a vendor ranking sets out the same trade-off Genesys's Hourly Interacting option gestures at -- paying someone else to carry the operational load -- without turning it into a marketing comparison.

Neither path is stated here as cheaper, more reliable, or better supported than the other. Measure your own distinct-agent count and peak concurrency first; that pair of numbers is what makes a named-versus-concurrent quote, or a self-hosted capacity plan, mean something instead of a guess.

• Decide whether you are pricing a roster (named), a peak shift (concurrent), or a server (VICIdial) before requesting a quote.
• Read the linked hosting and capacity guides before assuming self-hosting is automatically cheaper.
• Revisit this comparison whenever your shift pattern changes materially, not just once at signup.