Botpress review

Botpress is a hosted AI-native customer support platform, not a library or a self-hosted server. It provides an application for building AI agents and a helpdesk option, Botpress Desk, that can manage tickets on its own. Teams can also connect Botpress to an existing helpdesk, keeping their current ticket system in place.

The platform targets support work that needs more than an answer from a knowledge base: agents can update account details, issue refunds and coordinate actions across systems. The workflow can resolve a ticket end to end or pass it to a human with conversation history, account details and attempted troubleshooting. That puts Botpress between a customer-facing channel and the systems a support team uses to act on requests. The homepage describes building agents with natural language and connecting via OAuth. It also links an API Reference, but teams should check the current docs to understand how that interface maps to their application architecture.

Botpress presents agent building as a natural-language workflow and says teams can connect via OAuth. Its homepage links to Documentation and an API Reference, and lists integrations, channels, LLMs, Knowledge Bases and Tables as platform areas. Those are the integration surfaces the vendor names publicly on its homepage; it does not identify a protocol, programming language, SDK or CLI there. Confirm supported SDKs and API patterns in the vendor’s docs before planning a production integration.

For an implementation, map each agent action to the systems it must update, then verify the OAuth permissions and failure behavior for those connections. The product’s core workflow depends on safely coordinating actions such as changing a record and closing a request. Check how your existing helpdesk connects, what data Botpress needs, and how an agent’s handoff is represented in your ticket queue. The homepage says no engineering resources are needed to go live, but that is a vendor claim; custom integrations and production controls still need technical review.

The Free plan costs $0 and includes 100 conversations per month, 3 seats, 3 AI agents, 1,000 table rows and 100MB of vector and file storage. Plus is $150 per month when billed annually, with 250 conversations, 3 seats, unlimited AI agents, $25 of AI usage and 100,000 table rows. Team is $750 per month when billed annually, with 1,500 conversations, unlimited seats and agents, $150 of AI usage and 500,000 table rows. Monthly billing prices for Plus and Team are not published.

Conversation overages use packs: $65 per 100 on Plus and $50 per 100 on Team. That makes conversation capacity a separate cost to model alongside AI spend. Plus and Team storage add-ons cost $40 per month for 100,000 table rows, 1GB of vector storage and 10GB of file storage. Paid plans automatically purchase $10 AI spend credit grants when usage reaches 95% of the AI spend limit. Enterprise pricing is custom, with custom conversation volume and storage. The pricing page does not list an open-source option.

Botpress’s homepage describes an AWS-hosted service with automatic scaling and says it requires no maintenance. The vendor does not publish a source-availability or licence statement on the homepage, so teams should not assume the current product can be self-hosted or modified under an open-source licence. Ask Botpress directly about deployment options and contractual rights before making those requirements part of an architecture plan.

The homepage also does not explain data export or migration formats. That matters because agent behavior, workflows, tables and helpdesk records can become part of a support operation’s day-to-day process. Before launch, confirm how to export conversations, customer records and agent configuration, and whether those exports can be used outside Botpress. Without those details, the work required to migrate away is uncertain; plan for an exit path rather than assuming a portable configuration.

Botpress says its infrastructure runs on AWS with automatic scaling, and describes SOC 2 compliance, GDPR compliance and penetration testing by KPMG. The homepage also says agents use escalation rules and fallback logic, with context passed to a human. Those are vendor claims; production teams should review the Trust Center, security terms, uptime SLA availability and the exact escalation behavior for their deployment. The homepage does not publish a rate limit or detailed service-level figures.

Capacity planning needs to account for conversation caps, AI usage and storage, not just seats. Test failure paths for OAuth connections and downstream systems: an agent that changes a record or issues a refund needs a clear outcome when an action fails. Reddit discussion is limited and mixed. One r/Chatbots poster who says they like Botpress reports that costs can build even during active development. That is a user report, not a general cost estimate, but it makes usage monitoring and budget alerts worth checking before rollout.