Over the last few weeks, I spent some time building a customer support bot using Botpress to see how it stacks up against the growing wave of AI support platforms.. Here is my Botpress review after building a unique support bot.
Botpress gets recommended a lot for teams that want more control than simple chatbot builders but don’t want to build everything from scratch.
After testing it with AI customer support workflows, knowledge base content, escalation paths, and API integrations, I came away impressed in some areas and frustrated in others.
If you’re considering Botpress for customer support, here’s what I found.
1. The Visual Builder Makes Complex Flows Easier Than Expected
One of Botpress’ biggest strengths is its workflow builder.
Unlike many AI chatbot tools that hide everything behind prompts, Botpress gives you a visual flow editor where you can map conversations step-by-step.
The Verdict: For support teams that need approval paths, escalations, routing logic, and custom workflows, the visual interface is significantly easier to manage than writing endless prompts.
2. It’s Powerful, But Definitely Not “No-Code”
Botpress markets itself as accessible, but I wouldn’t classify it as truly no-code.
The moment you need API calls, CRM integrations, custom actions, or advanced logic, you’ll quickly find yourself working with variables, expressions, and JavaScript snippets.
The Verdict: Non-technical teams can build simple bots. More advanced customer support automation usually requires someone with technical skills.
3. My Botpress Review Found that Knowledge Base Responses Are Good
I connected a fairly large support knowledge base and tested common customer questions.
For standard FAQs, the answers were accurate and fast.
Where things became inconsistent was when customers asked multi-part questions or referenced information scattered across multiple documents.
The Verdict: Botpress performs well when the knowledge base is clean and structured. If your documentation is messy, expect inconsistent answers.
4. Integrations Are Both a Strength and a Weakness
- Botpress supports integrations with many external systems.
- The flexibility is impressive.
- The challenge is that flexibility often means more setup work.
The Verdict: You can connect almost anything, but don’t expect plug-and-play integrations for every workflow. Some implementation effort is usually required.
5. Testing and Debugging Takes More Time Than Expected
Building the bot was relatively straightforward.
Making it reliable was the difficult part.
We spent a surprising amount of time testing edge cases, retraining responses, adjusting workflows, and fixing unexpected conversation paths.
The Verdict: Building the first version takes days. Building a production-ready support bot takes considerably longer.
6. Costs Can Increase as Usage Grows
This section of the Botpress review should nor surprise. At first glance, Botpress pricing seems reasonable.
However, once usage scales and you start adding more conversations, integrations, and AI consumption, costs can rise faster than many teams expect.
The Verdict: Small teams will likely find it affordable. Larger support operations should model costs carefully before committing.
7. Human Handoff Requires Careful Design
One area I always evaluate is escalation.
When the AI cannot solve a problem, how well does it transfer to a human?
Botpress supports handoffs, but they require thoughtful workflow design.
The Verdict: If you don’t configure escalation paths properly, customers can get stuck in loops or receive repetitive answers.
The TLDR Takeaway of My Botpress Review
Who Botpress is for: Technical teams, agencies, and organizations that want significant customization and control over how their support automation works.
Who may struggle with it: Teams looking for a completely managed, plug-and-play support solution with minimal setup and maintenance.
What I liked most: The flexibility. You can build almost any workflow you can imagine.
What I liked least: The amount of testing, maintenance, and technical effort required to keep everything running smoothly.
For organizations with development resources, Botpress can be extremely powerful.
For teams primarily focused on customer support automation rather than bot development, there are now AI-native platforms worth evaluating as well.
- Botpress gives you maximum control.
Has anyone else deployed Botpress in production? How much time did you spend maintaining it after launch, and would you choose it again today?
Views: 0
I highlighted the part where you talked about Botpress making complex workflows easier and its flexibility, it also seems that for human handoff if carefully designed the module should work just fine. Therefore would you recommend Botpress as a go-to option for small businesses starting out and looking to grow?
I tested Botpress a while back, and the testing/debugging part is what stood out to me also, Building the initial flow is fairly easy, but getting it to behave consistently with real customer questions takes a lot more work than the demo makes it seem. it’s flexible, but I’m of the opinion, teams should factor in the maintenance time before calling it a truly no-code solution.
I really like the point about AI support needing to be more than just automation, the balance between faster responses, personalization, and knowing when a human should step in is what can actually make these systems valuable, a very practical take on what good AI customer support should look like.
The flexibility of Botpress sounds great, especially for teams that need custom workflows. I like that the review also points out the less obvious part: keeping the bot reliable can take a lot of time and testing. For a small team, that maintenance effort is definitely something I’d consider before choosing it
It being ‘no code’ isn’t an issue. Atleast you don’t have to code for some of the simpler instructions.
I would say that distinction gets overlooked with tools like Botpress.
The flexibility is good, especially when you need custom workflows and integrations, but every additional layer of customization can also create another thing to test, monitor, and maintain. For me, the real measure of a support platform isn’t how quickly you can build the first version, but how reliably it handles edge cases and escalates to humans months later.
people definitely underestimate the technical skills needed once you past the basics
Based on my experience, I’ve found that with tools like Botpress, it’s easy to get the first version working. The real effort you’ll need to put in is in the maintenance part. There is a constant need to update your knowledge sources, fix broken integrations, workflows adjustments, failed conversation reviews and even fine tuning the human handoff logic especially when you have new edge cases.
For Botpress, flexibility is good as long as you have someone technical who’s doing the maintenance. But, for a support bot, I’d go for a more managed platform since I want the ongoing workload to be as low as possible.
The testing and maintenance part stood out to me. Getting something working is easy keeping it reliable is the real challenge.
This is probably the biggest trade-off with customizable AI tools: more control usually means more responsibility.
I would say that the biggest trade off with Botpress is just what you highlighted. Versatility comes with maintenance. It seems like a powerful option for teams with technical resources but for enterprises that simply want trustworthy customer support automation, the setup and ongoing testing could surpass the advantage. The human handoff and knowledge base performance would likely be the areas I’d pay the most focus on before utilizing it in production.
[…] do they fail? With what? How does Botpress solve this […]
[…] asked a question outside the predefined flow, the experience often broke down. Most chatbots, like Botpress, were designed to answer questions, not actually solve customer […]