Failure PatternDecision layer

The Brevn Conversation Cap Trap: Why Agencies Fail With Brevn on High-Traffic Client Sites

Symptom: Client sites on the Basic plan (300 conversations/mo) hit the ceiling by the third week of the month, and the widget stops answering visitors until the next billing cycle. Root cause: The pricing ladder is volume-gated, not seat-gated: Basic caps at 300 conversations/mo, Starter at 1,500, Business at 6,000, and the top tier at 20,000. Agencies quote the $19 entry price to win the deal, then watch a moderately trafficked local site exhaust the allowance before the retainer's first invoice clears.

By InnovaAI ResearchPublished

Website Chatbots
How do you recognize it?
  • •Client sites on the Basic plan (300 conversations/mo) hit the ceiling by the third week of the month, and the widget stops answering visitors until the next billing cycle.
  • •Lead counts reported in the Brevn dashboard diverge from what clients see in their own CRM, because agents never configured the lead export on Starter or higher.
  • •Agency account managers discover a client has been running three separate Brevn agents on the same site, each crawling the same pages and producing conflicting answers.
  • •Clients on WordPress ask why the bot still quotes last quarter's pricing, because the Basic plan only auto re-crawls every 14 days and nobody triggered a manual re-crawl.
  • •Delivery teams field support tickets about the Brevn-branded dashboard appearing in client-facing screenshots, since white-label branding is not available.
Why does it happen?
  • •The pricing ladder is volume-gated, not seat-gated: Basic caps at 300 conversations/mo, Starter at 1,500, Business at 6,000, and the top tier at 20,000. Agencies quote the $19 entry price to win the deal, then watch a moderately trafficked local site exhaust the allowance before the retainer's first invoice clears.
  • •Manual re-crawl is a Starter-and-above feature, and even there it is limited to one per month. Agencies that onboard a client on Basic inherit a 14-day content refresh cycle, which is too slow for any business that changes pricing, hours, or service areas seasonally.
  • •Brevn has no white-label layer. Every client-facing dashboard, email alert, and widget footer carries Brevn branding, so agencies selling a 'proprietary AI assistant' retainer have to explain the third-party name or hide the dashboard entirely.
  • •Multi-site management is unified in one inbox, which encourages agencies to pile every client into a single Brevn account. When one client's crawl misfires or an agent is misconfigured, the blast radius touches every other client in that workspace.
How do you fix it?
  • •Audit each client's actual monthly conversation count in the Brevn analytics view, then move any site trending above 80% of its plan allowance up one tier before the next billing date.
  • •On Starter and above, schedule the one permitted manual re-crawl for the day after any client publishes pricing, menu, or service-area changes, and log that date in the client's delivery calendar.
  • •Consolidate duplicate agents: delete redundant Brevn agents on the same domain, keep one trained knowledge base per site, and re-point the widget script tag to the surviving agent.
  • •Set lead export on every client account above Basic and route it to the client's CRM or a shared inbox, so the agency's reported lead count matches what the client can verify.
Brevn decision recordBrowse the Academy

More on Brevn

More for Website Chatbots