Botpress Rule: Adopt When Conversation Volume, Not Seat Count, Drives the Support Bill
Should our agency standardize client support automation on Botpress, or is a per-seat helpdesk still cheaper for the clients we serve? Adopt Botpress when a client's support cost scales with conversation volume and the agency can absorb overage at $65 per 100 conversations, not when the client's need is a small fixed team answering a predictable ticket count.
By InnovaAI ResearchPublished
“Should our agency standardize client support automation on Botpress, or is a per-seat helpdesk still cheaper for the clients we serve?”
Adopt Botpress when a client's support cost scales with conversation volume and the agency can absorb overage at $65 per 100 conversations, not when the client's need is a small fixed team answering a predictable ticket count.
Agencies sell the retainer on the Plus plan's $150/mo sticker without modeling conversation overage, so a client with spiky ticket volume quietly consumes the margin at $65 per 100 conversations; the fix is to size the tier against measured monthly conversation counts before quoting, and to build an overage clause into the client contract.
Botpress prices by conversations rather than seats: Free covers 100 conversations and 3 seats, Plus at $150/mo includes 250 conversations with unlimited AI agents and white-label webchat, and Team at $750/mo includes 1,500. That structure rewards agencies serving clients whose ticket volume is high but whose human headcount would otherwise grow, and the Plus tier's white-label webchat plus custom domain Help Center is what makes resale as a retainer viable. The trade-off is overage: $65 per 100 conversations means a client that blows past its included volume erodes the margin the agency priced into the retainer.
- •The agency carries 5 or more support-heavy clients (ecommerce or SaaS) where ticket volume, not headcount, is the cost driver
- •A pilot client's monthly conversations fit inside the Plus plan's 250 included conversations, or the Team plan's 1,500, before overage applies
- •The client needs end-to-end resolution (refunds, account updates, multi-step workflows) rather than FAQ deflection alone
- •The agency wants to resell support automation under its own brand, which requires the Plus plan's white-label webchat and custom domain Help Center
- •Client channels include WhatsApp, Instagram, Slack, or Messenger alongside webchat, so multi-channel deployment matters
More on Botpress
- StrategyWhy Botpress Turns Support Retainers Into Margin Instead of Headcount
- ConceptBotpress Conversation Ceiling
- Decision FrameworkBotpress: Buy vs Skip (Support Automation Retainer Fit)
- Failure PatternWhy Agencies Fail With Botpress in Support Retainers: The Conversation Overage Trap
- Implementation BlueprintBotpress White-Label Support Resale Build (6-8 days)
- Operating ProcedureBotpress Pilot Client Agent Deployment (Onboarding)