Bookbag vs Botpress at a glance
| Feature | Bookbag | Botpress |
|---|---|---|
| Model | Buy — finished ecommerce support agent | Build — developer platform for custom agents |
| Built for ecommerce | Yes — Shopify-first | General-purpose; ecommerce is something you build |
| Engineering required | None | Yes — flows, integrations, testing, maintenance |
| Time to go live | Under a day | Weeks for a production-quality agent |
| Native order actions | Track, return, exchange, refund, subscriptions | Built via integrations you configure and maintain |
| Help desk / shared inbox | Included on Growth and above | Not included — integrate a separate tool |
| Pricing model | Flat plans, 1 credit = 1 AI reply | Plan plus metered usage; restructured May 2026 |
| Customisation ceiling | Configuration within ecommerce workflows | Very high — a genuine strength |
| Channel deployment | Chat, email, WhatsApp, IG, Messenger, Slack; voice higher up | Extensive, via the integration hub |
| Ownership | Vendor maintains the agent | You own the agent and its upkeep |
| Best fit | Stores with an ordinary support queue | Teams with engineering capacity and unusual requirements |
Why ecommerce teams choose Bookbag over Botpress
A finished product, not a toolkit
Ecommerce support flows are the product rather than something you draw. Connect the store and the agent already understands orders, fulfilments, returns, and subscriptions — no flow design, no integration build, no maintenance.
No engineering time in the total cost
The real cost of a build platform is developer weeks up front and hours every month after. Bookbag is live in under a day with no developer, and stays live without one.
Native ecommerce actions across three platforms
Order tracking, returns and exchanges with label generation, refunds inside merchant-set caps, subscription changes, product recommendations, and cart recovery work on Shopify, WooCommerce, and BigCommerce.
Help desk included
A shared inbox with routing, availability rules, and full transcript and order context on escalation is part of the product on Growth and above, rather than a separate tool you integrate.
Pricing you can forecast
Free, $30, $110, $350, and custom Enterprise, with one credit per AI reply on any model and a merchant-set spend cap. No metered usage model to model against engineering time.
Pricing compared
Flat monthly plans: Free ($0, 50 credits), Starter $30 (600 credits), Growth $110 (5,000 credits, 5 seats, help desk and all messaging channels), Scale $350 (15,000 credits, 15 seats), Enterprise custom. One credit is one AI reply on any model. No developer time required to launch or maintain.
Botpress restructured its pricing in May 2026, moving billing from incoming messages to conversations, bundling AI spend into plans, and offering unlimited bots, with workspaces created before mid-May staying on the previous model. We could not load botpress.com/pricing when checking in July 2026, so we are describing the model rather than quoting rates — check the current page directly, and if you are an existing customer, confirm which model your workspace is on. Note also that the subscription is usually the smaller half of the cost; engineering time is the larger.
Comparing subscriptions misses the point of a build-versus-buy decision. The dominant cost of a build platform is developer weeks to launch and developer hours to maintain, and that recurs every time an API or a policy changes. For an ordinary ecommerce support queue, a finished agent is cheaper in total cost and considerably faster.
Choose Bookbag when
- You run a store with an ordinary support queue and want it working next week
- You do not have engineering capacity to spend on building and maintaining an agent
- You want order actions, a help desk, and channels as one product
- You want predictable pricing without modelling engineering time alongside it
- Nobody on your team wants to own a chatbot codebase
Choose Botpress when
- You have engineering capacity and want full control over agent behaviour
- Your workflow is genuinely unusual — bespoke fulfilment, homegrown order systems, unconventional rules
- You are embedding an agent into a product rather than running customer support
- You need deployment flexibility that a hosted support product cannot offer
- The agent is a strategic asset you want to own rather than rent
Switching from Botpress
Moving from Botpress to Bookbag is less a migration than a decommissioning. Your knowledge sources move straight across — import the same content into Bookbag's training panel, connect your store with OAuth, swap the widget or channel connections, and configure escalation rules. Order actions work immediately, so the integrations you built in Botpress get retired rather than ported. Before switching, take an inventory of what your Botpress agent does that is genuinely unusual: if the answer is nothing beyond standard ecommerce support, the switch is a straight simplification and you get the engineering time back. If there is something genuinely bespoke, plan where that logic lives afterwards.
Frequently Asked Questions
Ready to switch from Botpress?
Join the ecommerce teams resolving more tickets, answering 24/7, and turning support into a revenue channel with Bookbag.