Botpress vs Voiceflow: Which should you build on in 2026?

Pricing and worked examples updated 19 September 2026 using the vendors’ public documentation. Figures are planning estimates in US dollars, not quotes. Voiceflow subscription prices and included balances must be checked in the account. Contents

• The verdict
• Botpress vs Voiceflow at a glance
• Why most comparisons are out of date
• Which should you choose?
• What each platform actually costs: three worked scenarios
• Pricing in detail
• Channels and integrations
• Building experience and collaboration
• Knowledge bases and agent behaviour
• Analytics and testing
• Data protection and hosting: a UK procurement checklist
• Alternatives worth a look
• How to run a trial that tells you something
• Getting it built properly

The verdict

Build on Botpress if your customers message you on WhatsApp, if a developer-led team wants deep integration work, or if you would rather buy conversations at a known rate than meter every token: it now bills by the conversation, with an AI-usage allowance included. Build on Voiceflow if the agent answers the phone, since voice on Botpress is an Enterprise-only channel, or if a mixed team of designers and developers will shape the conversation together. The cost comparison depends on both traffic and model use. Botpress sells conversation allowances with a limited amount of AI usage included. Voiceflow combines a subscription, included usage and optional add-ons. Its public documentation does not establish the plan price available to your account, so a fixed claim that one platform is a tenth of the cost would be misleading. The examples below separate what can be calculated from what still needs a quote. Pricing guides date quickly. Botpress changed its billing in May 2026, with older workspaces potentially retaining earlier terms. Voiceflow directs buyers to their dashboard for plan and bundle prices. Match any comparison to the actual workspace you intend to use.

Botpress vs Voiceflow at a glance

Pricing reviewed 19 September 2026; confirm account-specific terms before buying.

If the table extends beyond the screen, scroll sideways to view all columns.

Area	Botpress	Voiceflow
Entry point	BotpressFree: $0, 25 conversations, no top-ups or overages	VoiceflowFree plan: a one-time credit grant that does not renew, for evaluation only
First paid tier	BotpressPlus: $150 a month billed annually; 250 conversations and $25 AI usage included; check monthly billing separately	VoiceflowPro: check the current subscription price and included usage in Plans and Billing
Billing unit	BotpressConversation allowance with a proportional AI quota; not unlimited model use	VoiceflowCredits, included with the plan and consumed by messages, call minutes, speech and model tokens
Cost of extra volume	BotpressPacks of 100 conversations: $65 on Plus, $50 on Team; auto-recharge cannot be switched off	VoiceflowUsage draws down the included credits first; optional automatic top-ups buy more when the balance hits zero
Native messaging channels	BotpressWebchat from the free tier; WhatsApp and around ten other prebuilt channels, including Instagram, Messenger, Telegram, Slack and Teams	VoiceflowWebsite and telephony; other channels via the API
Voice	BotpressEnterprise plan only	VoiceflowBuilt in on paid tiers, with published telephony tooling
Team editing	BotpressThree seats on Plus, unlimited on Team; real-time collaboration, routing and role-based access from Team	VoiceflowReal-time editing; included editor seats depend on the plan, extra editors may cost more; viewers free
Self-hosting	BotpressNo; v12 sunset	VoiceflowPrivate cloud hosting at Enterprise; no documented self-managed deployment
Analytics	BotpressUsage and event analytics; Summary, Vision and Analytics Agents documented	VoiceflowCustomisable dashboard: resolution and deflection rates, CSAT, latency, credit usage, tool and knowledge-base usage, time and money saved
Testing	BotpressManual emulator in Studio; automated evals with assertions and LLM-as-judge via the developer ADK	VoiceflowBuilt-in test suite with scripted and AI-simulated conversations; scheduled automated runs via its test platform
Learning curve	BotpressSteeper, more control	VoiceflowGentler, more guardrails

Why most comparisons are out of date

Four shifts matter more than any feature list. Botpress sells conversations with an AI allowance. Its May 2026 announcement explains the move away from the previous billing model and says existing workspaces retain their former pricing. The current pricing page specifies $0.10 of included AI usage per conversation. Watch both the conversation count and AI meter; a long, expensive workflow can exhaust the allowance before the conversation count suggests it should. Botpress has repositioned around customer support. It now sells an AI-native helpdesk, Botpress Desk, alongside the Studio, on the same plans and conversation counts. Voiceflow’s plan price needs an account check. Its public pricing page offers a trial or sales enquiry, and the billing guide directs buyers to Plans and Billing. Do not apply the August plan figures to a new purchase without confirming them. Botpress v12 has been withdrawn from sale. Botpress says the self-hosted version older guides still recommend “has been officially sunset” and is no longer sold or supported for new deployments, with Botpress Cloud the only path for new commercial work. The open-source v12 code and releases remain publicly available on GitHub, so the determined can still download it; running an unsupported stack to save money is a different decision from the one this article covers, and not one we would make for a client.

Which should you choose?

Choose Botpress if customers reach you on WhatsApp; if the work is support-ticket deflection and a bundled helpdesk appeals; if the agent needs to read from and write to several systems; or if conversation-based billing suits your support volume. Include the AI allowance and overage behaviour in that decision. Choose Voiceflow if the agent answers the phone, which Botpress reserves for Enterprise; if your volumes make paying per conversation painful; or if the builders are conversation designers rather than developers. Choose neither yet if you cannot name the specific enquiries you want deflected and say what share of your inbox they represent. The costly mistake is not picking the wrong platform. It is building a capable agent for a problem nobody had. Want a cost check before you commit? Send us your expected channels, monthly traffic and team size and we will estimate the likely Botpress and Voiceflow costs, and show you which assumptions could move the number.

What each platform actually costs: three worked scenarios

These examples separate the calculation from the buying decision. Botpress figures use annual-plan monthly equivalents. Voiceflow figures show usage at its published self-serve dollar rates; they are not complete invoices. Included balances, subscription fees, extra seats, taxes, implementation and third-party charges can change the amount payable.

1. A website chatbot handling 1,000 conversations a month

Assume six visitor messages per conversation: 6,000 messages. For the model calculation, assume one GPT-4.1 mini call per message, averaging 1,000 input and 300 output tokens, without priority processing.

Botpress: Plus includes 250 conversations. The remaining 750 require eight packs of 100: $150 + (8 × $65) = $670 a month on annual billing. This is a conversation-based subtotal, subject to AI usage staying within the allowance. It is not a spending cap.

Voiceflow: 6,000 messages at $0.005 cost $30 in orchestration usage. Six million input tokens at $0.0005 per thousand cost $3; 1.8 million output tokens at $0.002 per thousand cost $3.60. The modelled usage is therefore $36.60 before the subscription and other charges. Reconcile that usage with the balance included in your plan rather than automatically adding it all to the monthly fee. The published usage table is the source for these rates.

Run a small trial to replace those token assumptions with real measurements. Longer retrieved documents or repeated tool calls can change the comparison substantially.

2. A three-person team running a WhatsApp support agent

Assume 500 conversations a month. Botpress Plus has three seats and includes 250 conversations. Three extra packs give a subtotal of $150 + (3 × $65) = $345 a month on annual billing, subject to the AI allowance. WhatsApp provider charges are separate. If the team needs the routing and collaboration features of Team, compare its $750 annual-plan monthly equivalent against the actual requirement.

For Voiceflow, first scope the WhatsApp integration and maintenance work. Price the account’s plan and any extra editor seats, then estimate message and model usage. There is no defensible complete total without those inputs; compare implementation and running costs over the same period.

3. A voice receptionist handling 100 five-minute calls a month

That is 500 call minutes. Voiceflow’s published self-serve phone rate of $0.05 per minute gives $25 in phone-usage charges. Add the selected transcription, speech and model usage, then reconcile the total with the plan’s included balance and subscription. Extra phone numbers, concurrency and carrier arrangements may also affect the bill. The previous claim that this necessarily fits a $60 or $90 plan cannot be supported without an account check.

Botpress lists voice on Enterprise. Ask for a quote for the same call volume, concurrency and handoff requirements before comparing totals.

Pricing in detail

Botpress

The Botpress pricing page was checked on 19 September 2026. Annual-plan monthly equivalents are shown below. Confirm monthly billing and any legacy workspace terms separately.

• Free, $0: 25 conversations with no top-ups or overages. Treat it as an evaluation allowance.
• Plus, $150 a month billed annually: 250 conversations, $25 included AI usage and three seats. Additional conversation packs cost $65 per 100.
• Team, $750 a month billed annually: 1,500 conversations, $150 included AI usage and unlimited seats. Additional packs cost $50 per 100. Team adds routing, roles, team analytics and real-time collaboration.
• Enterprise, custom. Custom volume, SLA and security review, and the voice channel, which no lower tier offers.

A storage add-on at $40 a month adds 100,000 table rows, 1GB of vector storage and 10GB of file storage on Plus and Team. And watch the conversation definition before you model costs: at least two messages in the billing month, anonymous sessions counted separately, month-straddling conversations counted twice. Spam is the only stated exclusion.

Voiceflow

Voiceflow’s billing documentation separates the plan fee, add-ons and credit-based usage. Current subscription prices and included balances are shown inside Plans and Billing. The August figures previously quoted here should not be used as a current offer.

Free provides a one-time evaluation allowance. Paid plans include usage, and extra editor seats or phone capacity can add to the bill. Viewers are free. Check the included seats before assuming that every additional team member costs extra.

Its usage table has separate self-serve and Enterprise views. The examples above use the self-serve dollar amounts. Do not mix those with the Enterprise credit figures or assume that a displayed usage subtotal is the final invoice.

What happens when you run out

The two platforms have taken opposite positions, and it is worth understanding which risk you are buying. On Voiceflow, with automatic top-ups disabled, exhausting the balance can stop the agent replying mid-month. Enable automatic top-ups and Voiceflow “automatically purchases additional credits when your balance hits zero”, with nothing charged in advance. Top-ups off risks an interruption in front of customers; top-ups on prevents that but lets spending continue until someone notices. On Botpress you no longer get that choice on paid plans. Auto-recharge cannot be turned off; instead you get usage warnings as you approach quota and a notification for every pack purchased. Packs recur month to month until you remove them in billing settings, and unused pack conversations expire at month end rather than rolling over. The Free tier is the mirror image: hard-capped, with no overages at all. So on Voiceflow the failure mode is a silent agent, and on Botpress it is a growing invoice. Whichever you choose, give someone responsibility for watching the number.

Channels and integrations

If your customers message you on WhatsApp, this section decides the question on its own. Botpress ships webchat from its free tier and offers official prebuilt integrations for around ten conversational channels, including WhatsApp, Instagram, Messenger, Telegram, Slack, Microsoft Teams, Discord, Viber and SMS, with a wider hub covering CRMs, Notion, Google Sheets and Gmail and an SDK for building your own. Counts drift as the hub grows, so check the hub rather than quoting a number, and check the pricing page for which channels sit on which tier. The exception, and it is a large one, is voice. Botpress lists the voice channel on Enterprise only, so a self-serve customer who wants the agent to answer the phone has no route to it. Voiceflow covers the website and telephony natively on paid tiers; its other channels are reachable through the Conversations API, which means development time and ongoing maintenance rather than a switch. For a UK retailer where a meaningful share of enquiries arrives through WhatsApp or Instagram, that gap is the whole argument, and it points at Botpress. For a business whose customers ring rather than type, it points just as firmly the other way.

Building experience and collaboration

Both give you a visual builder, branching, variable capture and custom code where the drag-and-drop runs out. Voiceflow is the easier first day. In our own builds, non-technical people reached a working prototype faster, and independent user reviews tend to score its interface higher. Real-time collaborative editing is part of the product on paid plans, with five workspace roles; editors are billable, viewers free. Botpress asks more of you up front and gives more back later: finer control over logic, structured data and custom events. In our experience a non-developer needs a few weeks, not an afternoon, to become properly competent; treat that as our observation rather than a measured figure. There is no per-seat charge, which becomes a real advantage as a support team grows, but simultaneous editing, routing and role-based access all arrive together at Team. The honest framing is not which is easier, but who is building. Give Voiceflow to a conversation designer or a marketing manager. Give Botpress to someone comfortable reading API documentation.

Knowledge bases and agent behaviour

Both platforms train an agent on your own content, use vector storage, accept documents and URLs, and answer from that material. Botpress goes further with its Autonomous Node, which hands the model the decision about when to search the knowledge base, call an API or escalate, rather than making you draw every branch. It also documents a family of specialised agents, including Summary and Vision Agents for conversation summaries and image understanding. For enquiries you cannot predict, this behaves noticeably better than a flowchart; it also makes testing harder, because the agent’s path is no longer fixed. Whichever you pick, the knowledge base is where projects quietly fail. An agent trained on a PDF from 2023 will answer confidently and wrongly, and no amount of prompt tuning fixes stale source material. Sort the content before you build the bot.

Analytics and testing

Received wisdom has aged badly here, in both directions. Analytics. Voiceflow’s dashboard is no longer the afterthought older reviews describe. Its current documentation describes a customisable dashboard whose widgets include resolution and deflection rates, customer satisfaction, evaluations, chats, interactions and unique users, latency, credit usage, playbook, tool and knowledge-base usage, and estimated time and money saved. Transcripts capture full chat and voice history with logs, metadata, custom properties and evaluation results. Botpress documents usage and event analytics plus an Analytics Agent. If your project needs to justify itself to a finance director, both can now produce something presentable; test the specific report you need during the trial. Testing. Voiceflow ships a proper test suite: scripted test conversations, AI-simulated users acting out a scenario, exact-response and LLM-as-judge checks, routing and tool-call checks, batch execution and saved past runs. The Studio Tests tab is manually triggered, but its separate test platform adds scheduled runs that execute without anyone pressing a button, on one-off or recurring cron-style schedules. Botpress is no longer manual-only either: its developer toolkit ships automated evals that simulate conversations and assert on responses, tool calls, state and workflow progression, including LLM-as-judge scoring and a dedicated regression type, though this is a code-and-CLI workflow rather than a no-code screen. The old claim that neither platform has a regression suite is now wrong in both directions. Voiceflow’s testing is the more accessible for non-developers; Botpress’s is the more automatable for engineering teams.

Data protection and hosting: a UK procurement checklist

Both are North American companies processing conversation data that will frequently contain personal information. Both publish Data Processing Agreements with UK-relevant transfer terms. Certification is evidence of security practice, not proof of UK GDPR compliance; you still have to do the work below. Before you deploy either with UK personal data:

1. Read the DPA and check how it takes effect. Voiceflow’s is incorporated into its standard terms rather than signed separately; Botpress publishes its own. Larger deployments should still get contractual confirmation in writing, and an agency operating the agent for a client should map the full controller, processor and subprocessor chain first.
2. Confirm roles. In the normal case you are controller and the vendor is processor for conversation data; Botpress’s DPA also makes it a controller of usage data. Record this in your Article 30 register.
3. Check transfer safeguards. Both DPAs incorporate Standard Contractual Clauses with UK-specific provisions. Confirm the version you sign includes them.
4. Get the subprocessor list. Voiceflow’s sits in its DPA annexes; Botpress’s in its DPA schedules. Diarise the change-notification window so objections are possible.
5. Ask about hosting and residency. Voiceflow offers private or custom cloud hosting at Enterprise only. Ask both vendors, in writing, where your conversation data rests, and put the answer in the contract.
6. Set retention deliberately. Botpress documents 30 days for logs, 90 days for conversations, messages and events, and indefinite retention for files unless an expiry is set, with earlier deletion via its APIs. Voiceflow commits to deletion on request; confirm retention specifics for your plan in writing.
7. Test deletion. Run a subject-access and erasure drill before go-live, covering conversations, files, recordings and knowledge sources.
8. Decide what the bot may hear. Health data is special-category data under UK GDPR; children’s data attracts extra protection, and financial data is sensitive in the everyday sense even though it falls outside Article 9. Treat all three with care, and design the agent to deflect them rather than collect them.
9. Map the third parties. Whichever LLM, speech and telephony providers you actually configure will receive conversation data. Name them in your privacy notice.
10. Consider a DPIA. Automated conversations with the public at scale, voice recording, or anything touching vulnerable users will often justify one. It is cheaper than the alternative.

Alternatives worth a look

These two are not the only options, and for some briefs both are the wrong shape. If all you need is a website agent answering questions from existing content, a simpler knowledge-base tool such as Chatbase gets there in an afternoon. If the real job is triaging support tickets, the automation built into your existing helpdesk may beat bolting a platform onto the front of it, and Botpress Desk is now competing for exactly that ground. If the agent is voice-first at serious volume, compare the specialist voice platforms before settling. If you need full control of hosting and data, open-source frameworks remain the route, at the cost of maintaining them. And if the work is internal rather than customer-facing, the agent tooling built into products like ChatGPT Work and Claude Cowork may cover it without a bot-building platform at all.

How to run a trial that tells you something

A fortnight of structured testing will answer the question better than any comparison article, including this one. Pick your twenty most common real enquiries and use those, not invented examples. Build the same agent on both platforms; it is a day’s work and settles arguments no spec sheet can. Send a small slice of real traffic, then read the usage figures, because estimating costs before you have data is guesswork. Test the handoff to a human properly, including out of hours. Read fifty transcripts start to finish. Try deliberately awkward questions, including ones you would rather the bot refused to answer. And set your Voiceflow tests to run on a schedule, so the suite keeps checking the agent after you stop thinking about it. Budget for a small paid month on both. Voiceflow’s free plan is a one-time credit grant, and Botpress’s free tier lists 25 conversations with no top-ups, so neither will carry a fortnight of real traffic. One oddity to watch: Botpress’s own sources disagree on whether testing in the Studio emulator consumes your allowance. Its emulator documentation says those conversations are not saved and do not count against quota, though AI operations do, while its pricing material has suggested otherwise. Watch your workspace meter during the trial rather than assuming either way.

Getting it built properly

The platform choice is the easy part, and it matters less than people expect. What separates an agent that deflects support tickets from one that irritates customers is the quality of the content behind it, a clean escalation to a person, and somebody reading the transcripts every week and fixing what they find. That last part is the one nobody budgets for, and it decides whether the project is still running in a year. It is also where our AI and automation work tends to earn its keep. Not sure which way your numbers point? Send us your expected channels, monthly traffic and team size, and we will estimate the likely Botpress and Voiceflow costs before you commit to a build. No charge, no obligation: tell us about your project.