AI phone assistant costs: software and integration

The following selection is not a complete market survey or a product test. It illustrates why base price, included usage and overage belong together.

The table shows the published monthly amount, included minutes and price of an additional minute for four plans from itellicoAI and sipgate sona, checked on 26 September 2026.

Sources: itellicoAI pricing and sipgate sona pricing. sipgate explicitly states that VAT is additional. The retrieved itellicoAI page does not state the tax basis equally clearly; confirm it in the quote or checkout before making a tax-normalised comparison.

itellicoAI also notes possible extra charges for premium providers, models, recordings and other premium features. These figures therefore describe the published base calculation, not necessarily the final bill. Telephone connections and required integrations also need to be identified in every offer.

A trial allowance can help assess the voice, intake and settings. It does not necessarily cover an ordinary month of business use. Check whether minutes are one-off or recurring, whether there is a hard limit and which actions are available in the free scope.

A free plan may suit a genuinely limited workflow within its conditions. Once concurrent calls, business-system connections or particular support are required, the complete entitlement matters. A free demonstration also does not replace acceptance on your actual telephone route.

Treat implementation and internal work as separate items. Even when the software has no setup fee, someone must define knowledge, ownership and failure handling. That work does not disappear because account creation is quick.

Use the same structure for each offer: software base charge, billable overage, additional telephony, ongoing support and internal follow-up work. Show one-time implementation separately or allocate it transparently over a stated comparison period.

For a plan with included minutes, a simple calculation is the base charge plus the positive excess of billable minutes over the allowance, multiplied by the overage rate. This applies only if the contract actually bills that way. Bundle sizes, rounding and other rules must be added where relevant.

The table lists six cost components of an AI phone assistant with the question each one raises for the proposal.

Clearly mark anything you do not yet know as unresolved. An empty field should not silently become zero euros in a purchasing decision. Telephony and operational support can differ substantially between apparently similar products.

Synthetic usage using the published itellicoAI base tariffs: At 1,600 billable minutes, Growth calculates as €99 plus 600 × €0.12, or €171. Professional remains €199 because usage is within its included allowance. Tax treatment and possible additional services are excluded from this illustration.

At 2,500 minutes, the same base calculation gives €279 for Growth and €249 for Professional. The cheaper plan in the first scenario is therefore not necessarily cheaper at a higher volume. Capacity and features can also affect the choice; this arithmetic is only one part of selection.

The table summarises this synthetic base calculation for the two published itellicoAI plans, excluding tax and possible additional services.

Two scenarios. Model at least an ordinary month and a busy month. For seasonal businesses, an annual view may be more meaningful than extrapolating a quiet period. Check when plan changes take effect and whether a longer commitment introduces different terms.

Peaks. Do not use an average month to hide operational peaks. A business can have modest annual usage while still needing reliable capacity during a short daily rush. That is both a cost and service-design issue.

Call groups. Group calls by purpose and duration. A short opening-hours question differs from rescheduling an appointment through several clarifications. Do not multiply all existing calls by the length of the supplier's shortest demonstration.

Synthetic profile: 200 information calls at one minute, 150 callback requests at two minutes and 100 appointment enquiries at four minutes produce 900 minutes. If clarification extends the final group to six minutes, the total rises to 1,100. Conversation and process design directly influence usage.

Waiting and transfer time. Ask whether waiting for another system or time after transfer to a person is charged. The answer depends on the product and telephone route. An assistant that remains connected during a long transfer may be billed differently from what the buyer expects.

Call logs. Use actual call logs where lawfully available, but inspect their meaning. A carrier's total connection duration may include ringing or human handling that will not correspond exactly to the AI provider's billable metric. Keep the assumptions visible.

A thousand monthly minutes can be spread evenly or concentrated in a few peaks. A plan can offer enough total usage while supporting too few simultaneous calls. Estimate overlap and decide what is acceptable when capacity is exhausted.

The business might route excess calls to staff, a managed callback process or another telephone destination. Those alternatives must actually exist. “Always available” is not a precise service description if a capacity or spending limit can stop the assistant.

Request a capacity test and documented outcome. Budgeting should consider both the higher entitlement and the consequences of delayed or lost calls. Those consequences are specific to the business; generic supplier revenue claims do not establish them.

Deliverables. Implementation is reviewable when its outputs are described: approved conversation rules, maintained knowledge, routing, destination fields, permissions, failure paths and passed acceptance cases. Choosing the assistant's voice does not mean you have set up a system that makes and saves calendar bookings.

Integration operations. For integrations, ask about exact operations: find a contact, create a task, book an appointment, change an existing booking or read a status. Each additional write operation has prerequisites and tests. Showing a CRM logo does not fully specify the work the supplier will deliver.

Documentation and changes. Agree which documentation is handed over and who can change the configuration later. If every knowledge correction requires a paid project, ongoing costs change. If internal staff can maintain it, they still need time and clear instructions.

Acceptance boundary. Specify the acceptance boundary. A service that creates a draft for human approval delivers a different result from one making a confirmed transaction. Both can be useful, but their prices should be compared alongside that difference.

Synthetic project budget, not a modernagents price list: Offer A includes €2,400 setup, €180 monthly software and usage, and €120 monthly support. Twelve months total €6,000. Offer B includes €600 setup, €220 monthly usage and €80 support, totalling €4,200.

The table sets the two synthetic offers side by side.

Equivalent work. The comparison is useful only when both cover the same work. If A delivers confirmed calendar bookings while B only emails requests, the outputs differ. Show remaining staff work beside the annual total.

Remaining staff work. If B requires five extra staff hours a month at an assumed internal rate of €40, this example adds €2,400. That rate is illustrative. Use your own cost assumptions and avoid presenting every saved minute as a cash saving the business will actually realise.

Recurring administration. Include recurring administration consistently. Knowledge maintenance in one offer should not be compared with a second offer that excludes it while silently assuming the work is free. The purpose is to identify the full workload, not to make either quote appear artificially cheaper.

Cost per completed request. Measure cost per correctly completed suitable request. Divide relevant total costs by work actually completed, not by every call answered. Callback intake and autonomous appointment booking may need different outcome measures.

Synthetic comparison: €400 monthly cost divided by 200 usable work items gives €2 each. If only 100 are usable without correction, the same calculation gives €4 per immediately actionable result. Agree the definition before the trial.

Reachability. Evaluate improved reachability separately from time savings. A previously missed call may have value, but that depends on whether it becomes a genuine order or useful service outcome. Answering the call alone does not prove additional revenue.

Released staff time. Consider whether staff time is released at useful moments. Reducing interruptions during site work or patient reception may improve service even when the total number of paid staff hours stays the same. Describe that operational value honestly rather than forcing every benefit into a wage reduction.

Usage export. Agree which usage information can be exported. Reconciliation needs the billing period, chargeable minutes, tariff, additional features and any connection charges. Personal conversation content is normally unnecessary for this purpose; a traceable billing identifier may be sufficient.

Differences. Compare the invoice with expected usage and investigate differences promptly. Rounding, lengthy transfers, an enabled premium feature or a different call profile may explain them. Do not change the plan before understanding the cause.

Alerts and limits. Record who receives consumption alerts and what happens at a limit. A budget warning without an available owner protects neither spend nor telephone continuity. The price comparison therefore continues through the first operating month, when its assumptions can be checked against a real bill.

Confirm number country and provision, international connection segments, currency and tax treatment. UK or Swiss offers may use sterling or francs and different service conditions. Converting currencies does not by itself make two contracts comparable.

Review commitment, cancellation, exports, number portability and continued access to knowledge and configuration. The business should understand how it retains its public contact point and operational information when changing services. Specific rights need contractual confirmation.

To obtain a useful proposal, provide a call profile, routing plan, permitted tasks and required destination actions. A supplier can then build a traceable total-cost calculation. Without those inputs, a precise implementation price is more likely to be an assumption than a sound basis for selection.

These pages cover the service overview and the related decisions about AI phone assistant costs:

• AI phone assistants: functions and boundaries
• Compare AI receptionists for small businesses in Europe
• AI phone assistant or human answering service?
• Testing an AI phone assistant in Austria: acceptance guide

Discuss it with modernagents.