Conversation usage
Estimate monthly voice-agent hours, seasonal campaigns and likely overage. The package allowance should follow real traffic rather than an arbitrary feature gate.
Esta página está disponible en inglés por ahora. Ver la página en inglés
Pricing
Voice AI pricing that grows with the workflow
Dring packages voice AI around the work you need to run, from support and sales to booking, logistics, healthcare, finance, HR, surveys and tool actions. Fit is shaped by usage allowance, concurrent call capacity, workflow breadth, handoff needs, analytics, support and integration depth.
Package fit
Size the package from the operation
There are no public numeric prices here. Choose the package shape that matches the operation first; the proposal then reflects the included voice-agent hours or usage allowance, concurrent call capacity and the workflow controls your team actually needs.
Peak concurrency
Size for the busiest useful window: how many calls should run at once, what happens when demand spikes and which conversations need live transfer.
Workflow depth
Count distinct agent types, systems, analysis fields and operating teams. A second workflow can require different tools, policies and quality tests even when call volume is unchanged.
Decision table
Compare the package logic
All package shapes share the same Dring platform. The difference is the operating scope around it. For the product detail behind the table, see the platform, telephony, analytics and Dring Connect.
| Starter | Professional | Business | Scale | Enterprise | |
|---|---|---|---|---|---|
| Best fit | One focused first workflow | A production workflow with richer call handling | Several workflows or teams | Growing operation with higher peaks | Largest or most complex operating scope |
| Usage and capacity | Entry allowance and focused concurrency | Broader allowance for one production line | More usage and concurrent calls | Higher-volume, higher-concurrency operation | Capacity scoped to the agreed operating model |
| Agent/workflow types | One starting type | One primary type | Multiple types | Multiple types across a growing operation | Multiple types across complex teams and processes |
| Live transfer and voicemail | Not the default package path | Available when the workflow requires it | Configured across approved workflows | Configured for broader routing needs | Complex routing and policy scope |
| Analytics depth | Core conversation analysis | Core plus management analysis | Core plus management analysis | Core plus management analysis | Core plus management analysis, with additional fields as scoped |
| Support and SLA | Standard support | Standard support | Standard support | Dedicated operating support | Dedicated support and enterprise SLA scope |
| Integrations | Standard API services | Mainstream CRM/helpdesk path available | Mainstream path plus separately scoped custom work | Broader integration scope | Complex or niche integration assessment |
| Models | Selected STT/TTS/LLM | Selected STT/TTS/LLM | Selected STT/TTS/LLM | Selected STT/TTS/LLM | Selected STT/TTS/LLM |
Included
Shared across every package shape
Models and reach
Selected STT, TTS and LLM components, after-call analysis, telephony and reach orchestration, and the voice library are shared across the scoped workflow.
Operations and assurance
Auto testing and monitoring, failover, guardrails, abuse protection and data isolation support the workflow from validation through production.
Handoff and actions
Human handoff, agentic actions and the agreed live-transfer or voicemail behaviour are part of the scoped operating design.
API and workflow services
The API, standard call-trigger, state/result query and result webhook services are included for the scoped workflow. Additional analysis fields can be defined.
Regression review and the operating cadence are agreed with the workflow. Mainstream CRM and helpdesk systems such as HubSpot, Salesforce and Freshdesk follow the same package logic; niche or heavily customised CRMs are assessed separately. Read about quality assurance, the Agent Factory, the voice AI operations snapshot and the 62-language customer service guide before choosing a fit.
FAQ
Questions before you choose
Which plan is right if we do not know our volume yet?+
Start with the first workflow you want to improve, then estimate monthly conversation time and the busiest concurrent window. Starter, Professional, Business, Scale and Enterprise increase operating room across usage, concurrency, workflow types, analytics, integration and support. We recommend the smallest tier that can run the real workload without hiding a critical requirement.
What is included in the monthly subscription?+
Your plan includes platform access, the agreed agent and workflow scope, an included usage allowance, analytics, testing and the support model stated in your proposal. Integrations, deployment and any additional capacity are made explicit before launch.
Can we start with one agent and upgrade later?+
Yes. A small, measurable first launch is often the fastest route to a larger deployment. You can expand as traffic, workflows, languages or teams grow, with the next plan based on production evidence.
What happens when demand changes month to month?+
We account for seasonality, peak hours and campaign windows. Your allowance, any rollover or additional capacity, and special campaign terms are stated in the proposal so there are no surprises when the pattern changes.
How are implementation and non-standard work priced?+
The package covers the agreed platform and operating scope. Mainstream CRM connections follow the same commercial logic, while a niche system, unusual customisation or other non-standard development is assessed before the proposal is final. The proposal separates included capacity, support and any additional work so the package can be reviewed without guessing.
Do partners have a separate commercial path?+
Partners start from the Dring subscription and commercial terms agreed for their track. Reseller margins and referral shares are scoped after we understand your customer base and delivery model. See the partner programme.
Turn the operating shape into a package brief
Once you know the first workflow, estimated monthly conversation time, peak concurrency, systems and analysis needs, submit the brief. With consent, Dring AI can call in about two minutes and qualify the remaining details.