Preparing the Havio workflow view
Pricing
Included monthly minutes, defined agent limits, and clear rules for overages, transfers, failed calls, setup, support, and annual billing before launch.
Billing rules
Pricing should make the operating model clear before a buyer routes real calls: included usage, support path, retention, transfers, setup scope, and when custom terms apply.
Included minutes
Starter includes 200 minutes, Growth 1,000, and Scale 3,000. Enterprise volume is scoped from expected call traffic.
Overage rate
Standard extra usage is modeled at EUR 0.08 per additional minute unless a custom Enterprise term overrides it.
Failed calls
Calls that never connect to the agent because of carrier failure are not treated as handled calls. Completed test calls and short answered calls can count toward usage.
Transfers
The AI-handled part of a transferred call counts toward included minutes. Downstream carrier or destination charges are separate when they apply.
One AI receptionist for a focused missed-call or booking workflow.
Best first check: one phone line, one workflow, predictable call volume.
Multiple workflows for a growing team with CRM and calendar handoff.
Best fit: booking, lead qualification, CRM handoff, and team review.
Higher call volume, multiple locations, advanced routing, and more integrations.
Best fit: multiple locations, heavier routing, and operational reporting.
Custom volume, compliance review, support model, and integration requirements.
Best fit: security review, custom integration, volume, or procurement needs.
Plan fit starts from the actual call path: answer only, booking, lead qualification, transfer, CRM update, or multi-location routing.
Included minutes, overage, failed-call handling, transfer rules, and phone-number assumptions are clarified before live traffic.
A simple missed-call pilot needs a different support model than regulated workflows, custom integrations, or enterprise procurement.
Plan matrix
Use this table to compare usage, phone numbers, agents, integrations, setup, support, transfers, failed calls, taxes, telephony, retention, cancellation, and annual terms before a demo.
Prices exclude applicable taxes. Standard packages use the rules below; Enterprise terms can override usage, support, retention, uptime, telephony, and integration scope.
Plan decision
Minutes matter, but the real buying decision is the call workflow: booking rules, handoff quality, integrations, support, and review.
Estimate monthly calls, average duration, phone numbers, and active workflows before comparing plans.
Estimate plan fitCompare AI reception with missed-call loss, answering-service spend, and staff interruption cost.
Calculate ROIConfirm knowledge, fallback contacts, booking rules, disclosure, retention, and review ownership.
Run checklistBilling rules
Pricing should make the operating model clear before a buyer routes real calls: included usage, support path, retention, transfers, setup scope, and when custom terms apply.
Included minutes
Starter includes 200 minutes, Growth 1,000, and Scale 3,000. Enterprise volume is scoped from expected call traffic.
Overage rate
Standard extra usage is modeled at EUR 0.08 per additional minute unless a custom Enterprise term overrides it.
Failed calls
Calls that never connect to the agent because of carrier failure are not treated as handled calls. Completed test calls and short answered calls can count toward usage.
Transfers
The AI-handled part of a transferred call counts toward included minutes. Downstream carrier or destination charges are separate when they apply.
Phone numbers
Each plan includes a defined number of phone numbers. Extra numbers and requested porting work are scoped separately before activation.
Setup and support
Standard setup is included for packaged workflows. Complex routing, custom integrations, or enterprise support are scoped separately.
Annual terms
Monthly plans are available for standard packages. Annual terms may be available when a buyer wants a longer commitment.
Pricing FAQ
A good voice-agent price page should make the usage rules inspectable. These are the questions buyers should confirm before comparing Havio with answering services, developer APIs, or enterprise call platforms.
For signed agreements, the order form controls plan-specific limits. Public pricing explains the buying model and the questions that should be settled during setup.
Pricing is based on the agreed plan shape: included monthly minutes, active workflows or agents, phone numbers, integrations, support, and any scoped onboarding. The buyer should confirm whether a pilot uses forwarded calls, a Havio number, or a connected telephony account before comparing totals.
Failed-call treatment is confirmed before launch. A technical failure, abandoned caller, blocked number, transfer attempt, and completed conversation can have different billing rules, so the plan review should define what appears in usage reports.
Transferred calls can include AI handling time plus the handoff path. Havio scopes this before launch so the customer knows whether transfer minutes, attempted transfers, and human callback tasks are counted differently.
The plan should define included minutes, overage rules, alert thresholds, and when a move to Growth, Scale, or Enterprise is cleaner than paying for unpredictable overflow.
Usually yes. Most teams start with conditional forwarding for missed, busy, overflow, or after-hours calls so callers keep using the number they already know.
Standard workflow setup is included in the packaged launch path. Complex routing, custom integrations, multi-location rollout, regulated workflows, or procurement-heavy requirements are scoped before launch.
Month-to-month customers can cancel according to the public refund and cancellation policy. Customers should request needed exports of call summaries, transcripts, configuration, and billing records within the stated export window.
Recording and transcript availability depends on the plan, region, consent language, and retention settings. The launch checklist should decide whether recordings are enabled, how long summaries stay available, and who can review them.
Next step
Bring monthly call volume, average duration, current phone setup, and the first workflow you want to automate.