Pricing based on the workflow, call volume, and support required.
Voice AI cost is not only a per-minute number. A production deployment may include agent design, system integrations, telephony, testing, reporting, and ongoing optimization.
Four published plans. Every price is quoted on a call.
Minutes are the published quota for each plan. The rate is set against the workflow, the call volume, and the level of support required, so every plan is priced in a conversation.
Plan quotas describe included minutes. The final quote also reflects implementation, usage, telecom, integrations, and support requirements.
A cost-effective solution for small businesses to manage their communication needs.
Ideal for growing businesses looking to enhance their communication capabilities.
A comprehensive plan designed to scale and support your business as it grows.
Customized for large operations needing tailored communication solutions.
Included with Essential, Growth and Pro.
- Call platform access
- Custom sales scripts and templates
- Unlimited voice agents
- Custom cloned voices
- Custom API integrations
- Zapier integration
- White glove onboarding
- Done for you service
- Custom business support
- Support via call and text
Enterprise is listed separately, with custom pricing, custom quotas, and enterprise support.
What determines your quote.
Implementation and support
Conversation design, integrations, testing, launch, call review, and ongoing optimization are scoped to the workflow and support level.
Usage and telecom
Call volume, voice, phone numbers, carrier costs, transfers, peak concurrency, and related third-party usage shape the recurring cost.
Enterprise requirements
Dedicated support, high concurrency, custom reporting, specialized security review, advanced integrations, multilingual workflows, or unusual telephony requirements are scoped separately.
What implementation and support can include.
Conversation and agent design
Call-flow mapping, prompts, persona, approved answers, objection handling, business rules, data collection, transfer language, and edge-case behavior.
API and workflow builds
System searches, record updates, scheduling, payment steps, webhooks, notifications, transfer logic, and custom actions required by the approved workflow.
Testing, launch, and optimization
Scenario testing, test calls, rollout support, call review, failure analysis, prompt and rule adjustments, and ongoing performance improvement.
What changes the price.
- Number of call workflows and agents.
- Inbound, outbound, or both.
- Monthly minutes, peak concurrency, campaign size, and call duration.
- Number and complexity of system integrations.
- Data collection, validation, payment, scheduling, and writeback requirements.
- Languages, voices, transfers, and human availability rules.
- Security, compliance, reporting, retention, and approval requirements.
- How much ongoing QA, scripting, and technical support the customer needs.
What we need to estimate a deployment.
Share the call type, monthly volume and peak concurrency, average call length, current phone and business systems, required actions, transfer destinations, languages, and the outcome you want to improve. A reliable estimate should separate implementation, recurring support, AI usage, and telecom.
Model your current phone operationCan we start with one workflow?
Yes. A focused first workflow makes it easier to estimate the work, test performance, measure results, and decide whether to expand.
Are integrations included?
The support package can include API and integration builds, but the scope depends on the systems, documentation, test access, required actions, and error handling. Third-party platform fees may remain the customer’s responsibility.
Why isn't pricing only a per-minute number?
Usage matters, but the workflow, model and voice requirements, support level, integrations, telecom, transfers, and commercial terms also shape the quote. The estimate should explain what is included rather than presenting a low platform-only rate.
Map one call workflow before you buy another AI tool.
Bring us a call type, sample recordings or scripts, call volume, current systems, and escalation rules. We will show what can be automated, what needs integration, and where a person should remain involved.