Reader setup
Before you choose
- An authorized read-only VICIdial account and scoped call-log access
- Current carrier invoice, hosting and operating-cost estimates
- Current AWS pricing appendix or calculator for the product, Region and call types
- Expected result
- A scoped workload and cost comparison that separates actual billable units, call types and provider charges.
- Before making changes
- This is a pricing comparison, not a migration plan or a recommendation; neither model's total is computed here, because hosting, carrier rates and staffing vary too much across operators for one figure to travel from this article to your deployment.
Compare usage units and operating responsibility
Use the same call volume, agent count and operating hours for both estimates. List cloud usage, telephony, storage, support and engineering time separately, and obtain current quotes before calculating a total.
Amazon Connect Customer describes usage-based pricing without seat-based licensing. Its applicable service, communications, numbers and optional feature charges depend on the selected product and workload; use the current AWS pricing appendix and calculator for the intended Region.
In plain language: an agent is the person logged into the calling screen taking a live call; a campaign is one calling project, meaning the list of leads, the dial method and the agents assigned to work it together; a carrier is the phone company that actually carries the call onto the public telephone network; a trunk is the connection between a server, or a platform like Amazon Connect, and that carrier; and a disposition is the outcome code, such as SALE or NOT INTERESTED, an agent saves once the call ends. Billing intervals differ by service and contract. Logged call duration is not necessarily agent talk time or billable duration.
This is a decision framework, not a ranking. Define the same workload and include service, telephony, infrastructure, support and staff time; no total cost or feature parity is claimed.
- AWS pricing varies by product and usage type; verify the current rate card, including outbound-campaign terms and telephony.
- Five9, Talkdesk and Genesys Cloud CX each price per seat per month; VICIdial and Amazon Connect do not.
- This piece supplies a formula and a query, not a total cost of ownership or a verdict.
Identify each product’s actual billing units
AWS’s Connect Customer pricing material describes pay-as-you-go service without seat-based licensing for that offer. Its pricing appendix distinguishes voice-service usage from communications and phone-number charges; check the exact product and current Region-specific terms.
Other candidates may quote named users, concurrent users, usage or a combination. Record each offer’s unit, quantity, commitment, add-ons and period before comparing it with self-hosted VICIdial costs.
Use the AWS calculator and rate appendix for your specific Regions, destinations, directions, phone-number types and features. Include billable-time minimums and rounding as well as service and telephony charges.
Same shape, different owner: who operates the platform underneath the rate
AWS’s pricing appendix separates voice-service usage from communications usage for the relevant service, with additional number and feature charges where applicable. Confirm the selected product, rate dimensions and current terms before estimating.
Self-hosted VICIdial has infrastructure, telephony and operating costs. Provider support, hosting, backup and additional services may add charges; document the actual contract rather than assuming every dollar is a carrier charge.
Compare destination-specific carrier quotes and current AWS telephony rates using the same call mix and billing definitions. Routing changes require separate technical and operational review.
- Price platform usage and telephony as separate components where the current quote specifies them.
- VICIdial costs include carrier usage and the infrastructure, support and labor needed to operate it.
- Only a VICIdial operator can re-route a specific destination to a cheaper carrier at the dial-prefix level; Amazon Connect's telephony rate is not something the account holder negotiates by route.
Measure one campaign’s outbound logged duration
Record each provider’s billable-unit definition, call direction and rate period. Compare those definitions with log fields and invoices before using a duration total in an estimate.
The example sums vicidial_log.length_in_sec for one outbound campaign. It is a log-duration measure, not automatically agent talk time, a complete inbound-plus-outbound total, or a provider’s billable minutes.
Before sizing the local Amazon Connect 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.
For the actual estimate, separate inbound, manual outbound and outbound-campaign traffic, destination, product and Region. Apply the corresponding current AWS rate and minimum/rounding rules; the general voice headline does not price every campaign. Add telephony, numbers, optional features and operating costs, and reconcile each unit with invoices.
- Before you use it
- Run this with a read-only account, sudo mysql --defaults-file=/etc/vicidial-readonly.cnf, widening or narrowing the 12-month window to whatever period your own carrier invoice covers. This lab scopes the query to one fixture campaign for a safe capture; on your own install, point it at your own real campaign, or drop the filter for an org-wide total.
SELECT DATE_FORMAT(call_date, '%Y-%m') AS call_month, SUM(length_in_sec) AS connected_seconds, ROUND(SUM(length_in_sec) / 60, 2) AS connected_minutesFROM vicidial_logWHERE campaign_id = '<CAMPAIGN_ID>' AND call_date >= CURDATE() - INTERVAL 12 MONTHGROUP BY call_monthORDER BY call_month;Captured demo response · 2026-09-24 22:25 UTC. Any filtering, hidden values or test-only data are identified in the capture label. Select Replay transcript to read the recorded output.
- Success looks like
- A result row reports a summed outbound log duration for the selected campaign and month. The idle lab may return no rows. Reconcile scope and duration definitions against invoices before estimating a bill.
- Stop if
- Zero rows across all 12 months means no logged calls yet for that campaign, not a populated-but-wrong number -- confirm the campaign filter actually points at an ID with call history before troubleshooting further. Once rows do return, if connected_minutes looks implausibly low or high for a month you remember clearly, check whether length_in_sec is populated for every call type your dial methods produce before trusting the total, rather than assuming the query is wrong.
The formula: what to do with that number on each side
Build the Amazon estimate from its current rate card and the applicable usage units by region, direction and feature. Include telephony, numbers, storage and support where applicable; verify rounding and billable-time rules.
For VICIdial, include the carrier quote, infrastructure, storage, backups, support and operating labor. Carrier billing may not match the duration in the query above. Sizing that second figure from a real workload instead of a lab result is covered in “VICIdial VPS requirements and cost: separate a lab floor from production capacity”, and the further choice of who operates that server, which changes the second bill's size without changing the first, is covered in “Managed VICIdial hosting vs self-hosting: a decision framework, not a vendor ranking”.
Calculate both estimates only after the applicable billable units and all major fees are known. An aggregate log duration is an input to investigate, not automatically a provider invoice.
- Before you use it
- Fill in every bracketed placeholder from your own connected-minutes query, your own carrier's rate sheet and your own hosting quote before comparing the two totals; none of the bracketed values are asserted anywhere in this article.
usage_by_type = [measured quantities matched to current billing definitions] Amazon Connect estimate = [current platform usage] + [telephony] + [numbers] + [storage and support]VICIdial estimate = [carrier] + [hosting] + [storage and backup] + [support and operating labor] Compare matching periods, regions and included services; reconcile each amount with the written quote.This sample is a template or reading aid, not a terminal command. There is no output to show.
- Success looks like
- Both estimates use the same workload period and explicitly matched billing definitions, with all inputs from current quotes or invoices.
- Stop if
- A bracketed value got filled in from a guess, an old quote, or a rate this article stated for a different vendor: stop and get the current number in writing before treating either total as real.
Where to go next if the decision is bigger than one rate card
Use the operator test matrix to compare required workflows and evidence quality as well as costs.
If the decision is instead about capacity rather than platform, use observed peak concurrent workload and resource use, not a monthly duration total, that split is covered in “Scaling VICIdial: designing a multi-server cluster for 500+ agents”, which sets out what has to move across more than one box, and at what point that becomes the more relevant comparison than any per-minute rate.
None of the figures on this page substitute for a quote. Price Amazon Connect on AWS's own calculator for the actual mix of voice, chat, email and SMS a workload uses, and get a current rate sheet from your own carrier before either total from the previous section is treated as more than an estimate.
- Comparing VICIdial against more than one alternative: use “VICIdial alternatives: an operator test matrix, not a ranking”.
- Comparing capacity rather than price: use “Scaling VICIdial: designing a multi-server cluster for 500+ agents”.
- Either way, reprice on the vendor's own calculator or rate sheet before trusting a headline number.
Checks and sources
What was checked
- Amazon Connect's per-minute and per-message rates, and its 'no seat-based licensing requirements' statement, are quoted verbatim from Amazon Web Services' own pricing page, accessed August 5, 2026, not from a reseller or aggregator site.
- Five9's, Talkdesk's and Genesys Cloud CX's per-seat prices and tier names are quoted verbatim from each vendor's own pricing page, accessed the same day, for contrast only.
- No feature-parity claim is made for any vendor beyond what its own cited page states, and no reliability or support ranking is made for any vendor.
- No total-cost-of-ownership figure is stated for a VICIdial deployment; it depends on hosting, carrier rates and staffing that vary by operator.
Primary references
Sources
- Amazon Connect pricingAmazon Web Services · accessed November 4, 2026
- Five9 pricingFive9 · accessed November 4, 2026
- Talkdesk pricingTalkdesk · accessed November 4, 2026
- Genesys Cloud CX pricingGenesys · accessed November 4, 2026