Contents
- Verdict
- What is Voiceflow?
- Best for, and not for
- Strengths and limits
- Pricing
- What people actually build with it
- What Voiceflow actually costs at small-business volume
- The gotcha: the price is only visible from inside the product
- What breaks in production, and how you find out
- What it connects to that you already run
- Voiceflow alternatives: what to pick instead, and when
- Migration and lock-in: can you get your work out?
- FAQ
Voiceflow is the most capable agent design tool of the five here and the least willing to tell you what it costs. As of August 2026 its pricing page shows no plan names, no prices and no allowances: two buttons, one for agencies and one for businesses, both leading to a demo. The mechanics are published in the docs, and they are good ones. Billing is credit-based at the organisation level, one credit per user message plus credits for the language model tokens your agent burns, and the docs' own conversion for self-serve accounts is 200 credits to the dollar. On our reference workload the credits come to roughly $56 a month. What you cannot know without logging in is the plan fee on top.
What is Voiceflow?
Voiceflow is a platform for designing and building AI agents and conversational assistants, with a visual canvas for mapping out flows. It started with voice and chat design and now supports LLM-powered agents deployed to web, messaging, and voice channels. It is often used by product and design teams collaborating on agent experiences.
Best for
Product and design teams collaborating on customer-facing chat and voice agents.
Not for
Anyone who needs to know the price before they build. If your buying process requires a number in a spreadsheet this week, Voiceflow will not give you one without a sales conversation.
Strengths
- The credit table is genuinely transparent about the meter itself: every model, speech-to-text and text-to-speech vendor has a published per-unit credit rate you can read before you build
- One credit per user message means the orchestration side of the bill is trivially forecastable from your conversation volume
- Credits are pooled across every workspace in the organisation, which suits agencies running several client agents
- Model choice is wide and includes cheap small models, so the token half of the bill is a lever you control rather than a fixed rate
- A per-conversation cost limit shipped on 30 July 2026: set a dollar ceiling and the session ends automatically when it is exceeded
- Environment protection, added the same day, locks production environments so only admins can merge or publish into them
- Viewers are free and unlimited on every plan, so stakeholders can watch a build without buying seats
Limitations
- No plan price, credit allotment or seat count is published anywhere public as of August 2026, so you cannot budget without a demo
- The Free plan's credit grant is one-time and does not renew, which the docs concede makes it unsuitable for production
- Two-part billing means a cheap plan can carry an expensive month if your prompts grew or your model changed
- Editor seats, phone numbers and concurrent call capacity are all separate add-ons, each with an unpublished price
- Auto top-ups prevent outages by buying credits automatically, which is convenient and also removes the natural stopping point on a runaway bill
- The self-serve to Enterprise gap is where the security features live, and Enterprise means an account manager rather than a checkout
- Agency and business paths are pitched separately, so the answer to a pricing question depends on which button you clicked
Voiceflow pricing
Voiceflow bills a monthly plan fee plus credit-based usage, with credits shared across every workspace in the organisation. Credits are consumed by orchestration and by model usage: one credit each time a user sends a message or a request hits the Conversations API, ten credits per minute of phone usage, and a per-1,000-token credit rate for every language model, which as of August 2026 runs from 0.0125 credits per 1,000 input tokens on the cheapest small model to 7.5 on the most expensive frontier tier. Voiceflow's own docs render those credit figures as dollars for self-serve accounts by dividing by 200, so one credit is $0.005. Four plans exist - Free, Pro, Business and Enterprise - and none of their prices, seat counts or credit allotments are published outside the product. Editor seats, extra phone numbers and extra concurrent calls are paid add-ons. Auto top-ups buy more credits automatically when the balance hits zero.
| Plan | Price | What you get |
|---|---|---|
| Free | Not published | One-time credit grant that does not renew, limited features, lower agent limit. Explicitly described in the docs as unsuitable for production (as of Aug 2026) |
| Pro | Not published | For individual builders. All language models, higher agent limit than Free, monthly credit allotment that resets each cycle |
| Business | Not published | Adds model fallback, priority support and more included editor seats |
| Enterprise | Custom | Unlimited product usage, SSO, private cloud hosting, custom credit allotments, account manager rather than self-serve billing |
| Credit rate | $0.005/credit | Implied by Voiceflow's own docs, which convert credits to self-serve dollars at 200 credits per dollar |
| Orchestration rates | 1 and 10 credits | One credit per inbound user message or Conversations API request; ten credits per minute of phone usage; no-reply messages free unless generative |
| Add-ons | Not published | Extra editor seats, extra phone numbers and extra concurrent calls, all billed monthly. Viewers are free and unlimited on every plan |
Pricing reflects public plans as of August 6, 2026 and can change. Check Voiceflow for the latest.
What people actually build with it
Voiceflow's centre of gravity is the designed conversation: a support or service agent whose behaviour is drawn as a flow, with deterministic branches where the business needs certainty and generative playbooks where it does not. That combination is what separates it from the pure question-and-answer tools, and it shows in what gets built.
Support deflection with a scripted escape hatch
The commonest build is a website widget answering product and policy questions from a knowledge base, with a deliberately scripted path for the three or four questions where a wrong answer is expensive. A returns agent, for example, answers freely about delivery times but drops into a fixed flow the moment a customer says the word refund, because the refund policy is a decision tree rather than a paragraph. The generative side handles the long tail, the scripted side handles the money.
The realistic outcome is a deflection rate rather than a resolution rate. A well-fed agent takes the repeat questions off the queue - opening hours, order status, where is my invoice - and the tickets that reach a human get harder on average, not easier. Plan for that in your staffing, because it changes what good looks like for your support team.
Voice agents that share a brain with the chat agent
Voiceflow bills phone usage at ten credits a minute on top of the model and speech costs, and the reason teams pay it is reuse: the same flow, the same knowledge base and the same tool calls serve the widget and the phone line. An appointment agent for a dental practice can confirm a booking over chat during the day and answer the same question by voice at seven in the evening without a second build.
This is also where the July 2026 cost limit per conversation earns its place. A voice session that hammers an expensive model can cost more than a long, quiet one, and a dollar ceiling per session is a cruder but far more reliable guardrail than watching a dashboard.
Agency builds across many client workspaces
Because credits pool at the organisation level and viewers are free, agencies use Voiceflow to run several client agents from one account, with white-labelling and client handoff tools that the pricing page names explicitly. The workflow is: build in a client workspace, share a viewer link for sign-off, publish through a protected environment, hand over.
The one it is genuinely bad at is back-office automation. Voiceflow is a conversation platform, and if the job is moving records between systems on a schedule with nobody talking to anybody, an automation platform like n8n or Make.com will do it for a fraction of the credits and fail more predictably.
Bottom line: Voiceflow is for conversations you want to design rather than merely train: scripted where a wrong answer costs money, generative everywhere else, reused across chat and voice.
What Voiceflow actually costs at small-business volume
Take the reference workload used across this whole batch: 1,000 support conversations a month averaging six turns, so 6,000 agent responses. On Voiceflow the meter splits in two. Orchestration is one credit per inbound user message, so 6,000 credits. Model usage is billed per 1,000 tokens at a published credit rate per model. Assume 2,500 input tokens per turn once the system prompt and retrieved context are included, and 200 output tokens - that is our assumption, not Voiceflow's. On a Claude Haiku class model at 0.25 credits per 1,000 input and 1.25 per 1,000 output, that is about 0.875 credits a turn, so roughly 5,250 credits.
Total: about 11,250 credits a month. At the 200-credits-to-the-dollar rate Voiceflow's own documentation uses to display self-serve prices, that is roughly $56 of usage. The honest and slightly maddening part is that this is not the bill. The plan fee sits on top and is not published, and nor is the credit allotment each plan includes, so we cannot tell you whether $56 of usage is covered by your plan or billed as top-ups.
The comparison below prices the identical workload on all five platforms in this batch. It is the single most useful thing on this page, because the units are not comparable until someone converts them.
| Platform | Billing unit | What the workload consumes | Realistic monthly cost |
|---|---|---|---|
| Voiceflow | Credits (1 per user message + tokens) | ~11,250 credits | ~$56 usage plus an unpublished plan fee |
| Botpress | Conversations (2+ messages) | 1,000 conversations | $670 on Plus with packs, $750 on Team, both billed annually |
| Chatbase | Message credits per agent response | 6,000-12,000 credits by model | $200 on Standard with top-ups, $400 on Pro |
| MindStudio | Flat plan plus tokens at provider cost | ~15M input, ~1.2M output tokens | ~$26 on a small model, no helpdesk layer included |
| Lindy | Credits per task, allowance unpublished | ~6,000 tasks | Not publishable; Max is $199.99 and overage bills at 2x |
Where the rest of the bill hides
Three line items sit outside the usage figure and each is a separate add-on with an unpublished price. Editor seats are the first: every paid plan includes some free ones and more are bought monthly, so a team of five builders is a different cost from a team of one. Extra phone numbers are the second, with one Voiceflow number included per workspace. Concurrent call capacity is the third, and it is the one people forget, because concurrency is about simultaneous calls rather than monthly volume. A business taking 300 calls a month can easily see five at once on a Monday morning.
None of those apply to a chat-only deployment, which is worth saying plainly: if you are running a website widget and nothing else, the usage figure plus the plan fee is your whole bill, and viewers are free and unlimited so stakeholders cost nothing to add.
The other thing the table cannot show is the shape of the risk. Voiceflow's usage is the most sensitive of the five to your own decisions, because both halves of the meter respond to what you build. Double your retrieved context and the token half of the bill doubles. Move a step from a small model to a frontier one and the same traffic can cost ten times more. That is a lever if you watch it and a trap if you do not.
Bottom line: Voiceflow's usage on 1,000 six-turn support conversations comes to roughly $56 of credits a month, which is the cheapest metered usage in this batch - but it is the only one of the five where the plan fee on top is a secret.
The gotcha: the price is only visible from inside the product
Voiceflow has taken the unusual step of publishing the meter in full and the price not at all. The credits pricing table in the docs lists every model, every speech vendor and every orchestration event with an exact per-unit rate. The pricing page lists nothing. The billing documentation is explicit about where the numbers live: you view current pricing for plans, add-ons and credit bundles by opening the Plans and Billing tab from inside your Voiceflow dashboard.
That has three practical consequences. First, you cannot compare Voiceflow against Botpress or Chatbase on a spreadsheet before committing time to a build, which is exactly when the comparison is cheapest to make. Second, anything you read elsewhere quoting Voiceflow plan prices is a figure from a previous pricing page and should be treated as stale until you have seen it in the product yourself. Third, procurement at any organisation with a purchasing process now has a demo call on the critical path.
The second-order gotcha is auto top-ups. They exist for a good reason: agents that run out of credits mid-month stop answering customers. But an automatic purchase every time the balance hits zero removes the one event that would otherwise force you to look at the bill. Turn them on for a production agent, and then set the per-conversation cost limit that shipped in July 2026 so a single runaway session cannot drain the balance that the top-up just refilled.
Bottom line: Voiceflow publishes exactly what each credit costs and refuses to publish what a plan costs, so budget the usage from the docs and treat the plan fee as an unknown until you have seen it inside the product.
What breaks in production, and how you find out
Voiceflow's failure modes are the ones common to every retrieval-grounded agent, plus two of its own that come from the credit model.
The knowledge base drifts and nobody notices
An agent grounded in your own content is only as current as that content. The classic production failure is a policy page that changed in March and a vector database that still holds the January version, so the agent answers confidently and wrongly. This is not a hallucination in the usual sense; the retrieval worked perfectly and returned stale truth.
The defence is process rather than product: own the list of source documents, decide who re-syncs them when they change, and sample real transcripts weekly against the current policy. Voiceflow's analytics and transcript access make the sampling easy; nothing makes the ownership question go away.
Cost moves without a pricing change
Because the model half of the bill is per-token, your costs move every time your prompts grow, your retrieval returns more context, or someone selects a better model to fix a quality complaint. None of those look like a pricing decision at the time. A month later the credit gauge is empty and auto top-ups have quietly bought the difference.
Two controls exist and both should be on from day one. The per-conversation cost limit ends a session once its spend passes a dollar figure you set, which catches the pathological case of an agent stuck in a tool-calling loop. Analytics gives you per-conversation cost so you can watch the average rather than the total - the average is what tells you something changed.
Publishing to production by accident
Multi-environment builds fail in a boringly human way: someone merges a half-finished flow into the environment carrying live traffic. Voiceflow shipped environment protection on 30 July 2026 for exactly this, letting you lock an environment so only admins or owners can publish or merge into it while everyone else keeps building and testing normally. Turn it on for Main before your first real customer arrives, not after.
The fourth pattern is escalation. Every support agent needs a clean route to a human, and the moment customers learn that saying the right word gets them a person, they use it. Instrument how often that happens and what preceded it. A rising handoff rate is the earliest honest signal that your agent has stopped being useful, and it shows up in transcripts long before it shows up in a satisfaction score.
Bottom line: The two Voiceflow-specific production risks are silent cost drift from prompt and model changes, and merging into a live environment; both have controls that shipped in July 2026 and both are off by default.
What it connects to that you already run
Voiceflow connects in three ways. Channels put the agent where your customers are, including a web widget and telephony through a Voiceflow phone number or your own. Tool calling lets the agent reach into your systems mid-conversation to check an order, look up a booking or create a ticket. And the API layer, including a Conversations API and a CLI, means an engineer can drive the agent from an existing application rather than embedding a widget.
For most businesses the practical pattern is the same as with any conversation platform: the agent handles the talking and hands structured data to something else that does the work. That something else is usually the automation platform you already run, whether that is Zapier, Make.com or n8n, and the connection is a webhook. It is worth designing that boundary deliberately, because it determines how much of your business logic lives inside a vendor and how much lives somewhere you control.
On the model side Voiceflow is genuinely open: the credit table covers OpenAI, Anthropic, Google and Groq models alongside speech vendors including Deepgram, ElevenLabs, Cartesia, Rime and AssemblyAI, and the August 2026 changelog added Soniox for speech to text. Business plans add model fallback, which matters more than it sounds when a provider has a bad afternoon.
Bottom line: Voiceflow talks to customers and hands the actual work to your automation layer through a webhook, so decide early how much business logic you are willing to keep inside the vendor.
Voiceflow alternatives: what to pick instead, and when
Voiceflow's closest rival is Botpress, and the choice between them is now mostly a choice about pricing philosophy rather than capability. Botpress publishes everything and bills by the conversation. Voiceflow publishes the meter and hides the plan. If you need a number today, that comparison is over before it starts.
The table prices each alternative on the same 1,000-conversation workload used above, so the columns are comparable.
| Alternative | Billing unit | Cost at the reference workload | Pick it instead when |
|---|---|---|---|
| Botpress | Conversation, AI spend bundled | $670-$750/mo billed annually | You need a published price and a hard number before you build |
| Chatbase | Message credit per response | $200-$400/mo | The job is documentation-grounded Q&A and you want it live this week |
| Intercom Fin | Per resolved outcome | Priced per outcome plus helpdesk seats | You already run the helpdesk and want deflection you only pay for when it works |
| n8n | Workflow execution | Low, self-hostable | The work is back-office rather than conversational |
| Autonoly | Managed workflows | Quoted per build | You want the agent built and run for you rather than designed in-house |
When to pick Botpress over Voiceflow
Pick Botpress if the buying decision needs a defensible cost forecast, if you want AI spend bundled into a single per-conversation price rather than metered separately, or if whitelabel webchat matters at the entry tier. Botpress puts branding removal on its $150-a-month Plus plan; Voiceflow does not publish where its equivalent sits.
Pick Voiceflow if the conversation design itself is the hard part. Its flow builder, environments and evaluation tooling are aimed at teams who will iterate on an agent for months, and that is a real difference in kind, not a feature checklist item.
When something else entirely is the answer
If your support already lives in a helpdesk, Intercom Fin's per-outcome pricing changes the risk profile: you pay when a conversation is resolved rather than when it happens, which is the friendlier shape when deflection rates are unknown. If your requirement is a chat widget trained on your documentation and nothing more, Chatbase gets there faster and cheaper. And if what you actually want is the back-office work behind the conversation, a workflow tool is the correct answer and no conversation platform will be.
Bottom line: Choose Botpress when you need a published price, Chatbase when you need a documentation chatbot this week, and Voiceflow when conversation design is the part of the project that will take months.
Migration and lock-in: can you get your work out?
The portable assets are the ones worth most and Voiceflow does not hold them hostage. Your knowledge base is your own documents, re-uploadable anywhere. Your transcripts are retrievable through the analytics API and the CLI. Your model relationships are with providers you can use directly. None of that is a switching cost.
What does not port is the flow. A designed conversation with branches, playbooks, global instructions, guardrails and tool definitions is a Voiceflow artefact, and rebuilding it elsewhere is a project rather than an export. That is true of every visual builder in this category, including Botpress, and it is the honest reason these platforms are sticky. The practical mitigation is to keep the conversation design itself - what the agent must say, must never say, when it escalates, what it does when it does not understand - in a document outside the platform. That document is the months of refinement. The flow is just its current implementation.
Two commercial details affect the exit. Cancelling is self-serve: you keep paid features until the end of the billing period and the account reverts to the free tier, with past invoices still accessible. Enterprise customers do not get that path and negotiate through an account manager instead, so on an annual contract the renewal date is your exit window.
The phone number is the asset that genuinely binds you, as on any voice platform. One Voiceflow number is included per workspace and more are add-ons; if the number is printed on anything, establish the porting terms before you print it. Bringing a number you already control is the cheapest insurance available.
Bottom line: Your documents, transcripts and model accounts all leave with you; the designed flow does not, so keep the conversation design in a document outside the platform.
Voiceflow FAQ
How much does Voiceflow cost?
As of August 2026 Voiceflow does not publish plan prices. Its pricing page shows two paths, one for agencies and one for businesses, both leading to a trial or a demo, and the billing documentation says current pricing for plans, add-ons and credit bundles is visible inside the product under Plans and Billing. What is published is the credit meter: one credit per user message, ten credits per minute of phone usage, and a per-1,000-token credit rate per model, with the docs converting credits to self-serve dollars at 200 to the dollar.
Does Voiceflow have a free plan?
There is a Free plan, but read the docs' own description before relying on it: it has limited features and a one-time credit grant that does not renew, and Voiceflow states plainly that it is not suitable for production usage. In practice it is an evaluation tier. That is a meaningful difference from a free plan with a monthly allowance, because your agent stops when the grant is spent and no reset is coming. Budget for a paid plan from the moment real customers can reach the agent.
What is a Voiceflow credit worth?
Voiceflow's credits pricing table displays self-serve costs by dividing the credit figure by 200, which puts one credit at $0.005. On that basis a user message costs half a cent of orchestration, a minute of phone usage costs five cents before model and speech charges, and 1,000 input tokens on a small model costs a fraction of a cent. The credit allotment included with each plan is not published, so you can price the usage precisely and the subscription not at all.
Voiceflow vs Botpress: which is cheaper?
On the reference workload of 1,000 six-turn support conversations, Voiceflow's usage comes to roughly $56 of credits, against $670 to $750 a month on Botpress depending on whether you sit on Plus with conversation packs or move to Team. That looks decisive until you remember Voiceflow's plan fee is unpublished and Botpress's price includes AI spend, unlimited agents and whitelabel webchat. The honest answer is that Botpress is the one you can budget and Voiceflow is the one you have to ask about.
What happens when Voiceflow credits run out?
Agents stop consuming credits, which for a live agent means it stops working. Voiceflow's answer is auto top-ups: enable usage-based billing, set a dollar amount, and additional credits are purchased automatically each time the balance hits zero, with nothing charged in advance. That protects the customer experience and removes the natural stopping point on a runaway bill, so pair it with the per-conversation cost limit added in July 2026, which ends any single session once its spend passes a ceiling you set.
Can Voiceflow do voice as well as chat?
Yes, and sharing one build across both channels is a genuine reason to choose it. Phone usage bills at ten credits a minute of orchestration on top of the model, speech-to-text and text-to-speech credits, with vendors including Deepgram, ElevenLabs, Cartesia, Rime, AssemblyAI and, since August 2026, Soniox. Each plan carries a concurrent calls limit that can be raised as a paid add-on, and one Voiceflow phone number per workspace is included with extra numbers billed separately.
How locked in are we with Voiceflow?
Your documents, transcripts and model provider relationships are all portable, and cancellation is self-serve with access continuing to the end of the billing period. What does not leave is the designed flow: branches, playbooks, global instructions, guardrails and tool definitions are platform artefacts and rebuilding them elsewhere is a project. Keep the conversation design as a written document outside the tool, because that document is where the months of refinement actually live.
Is Voiceflow worth it for a small team?
It is worth it when conversation design is the hard part of your project and you expect to iterate for months, because the builder, environments and evaluation tooling are the best of the five agent builders we reviewed in this batch. It is a poor fit when you need a documentation chatbot live this week, when your buying process needs a published price, or when the real work is back-office rather than conversational. Try Chatbase for the first case and a workflow tool for the last.
Can you build and run the agent for us?
Yes. Support deflection and booking agents are two of the builds we are asked for most, and the platform choice usually falls out of three questions: your conversation volume, whether the answers must be deterministic, and who will maintain it in six months. We scope it on a free automation audit, build it around the systems you already run, and hand it over with documentation you own plus a recurring plain-language report on what it handled and what it escalated.
Looking at alternatives? Voiceflow beats us outright on conversation design. If your project is a customer-facing agent that will be refined for months by a team that cares about how it sounds, its builder, environments and evaluation tooling are better than anything we would assemble. Where we differ is the shape of the job: Autonoly is aimed at recurring operational work that runs on a schedule with nobody watching, and at businesses that would rather have the thing built and handed over than learn a builder. We would also say plainly that a platform which will not publish its plan price makes the build-vs-buy conversation harder than it needs to be, and that is a fair reason to shortlist Botpress alongside it. See the Autonoly review.
