ChatBot review

ChatBot is a hosted SaaS application for configuring and deploying customer-facing chatbots. It sits between a company’s customer support or ecommerce stack and the channels where customers ask questions. A team trains an AI agent on website pages, help-center content and product documentation, then deploys it through a website widget or supported messaging integrations.

The product handles common questions, product recommendations and sales conversations, with a handover path to human agents for more complex chats. Its analytics cover resolutions and sales attributed to chatbot conversations. The vendor describes setup as no-code and says a website URL can build a knowledge base within minutes. That makes ChatBot a managed business application rather than a chatbot library or self-hosted server. It is designed for teams that want to configure an agent and connect existing channels, not for developers assembling a conversational system from model APIs, storage and application code.

The homepage links to API & Developers resources and an MCP resource, alongside a Setup Guide, Help Center, templates and Academy. It does not identify a programming language, SDK, CLI, API protocol or webhook interface, so confirm SDK support and integration mechanics in the vendor’s documentation before planning a custom build.

The named integration surface is primarily product integrations: Facebook Messenger, Twilio SMS, Klaviyo, WhatsApp, WordPress, Shopify, WooCommerce and Slack. The chatbot itself can also be deployed as a website widget. These connections fit teams adding chat to an existing support or ecommerce workflow; the homepage does not explain which features are available through each integration or how they authenticate. ChatBot says agents can be trained from a website, help center and product docs, then configured with skills and workflow automation. For a custom stack, check the API & Developers documentation for supported operations, authentication, event delivery and versioning before making ChatBot a core dependency.

There is no free plan. ChatBot offers a 14-day trial, then Essential starts at $19 per user monthly with annual billing or $25 with monthly billing. Essential includes one AI Agent and 10 AI resolutions per month, plus 120 per year. Growth costs $79 per user monthly with annual billing or $99 monthly; it includes 10 agents and 200 AI resolutions monthly, or 2,400 yearly. Annual billing cuts the per-user price by about 24% versus monthly billing.

The main production constraint is the resolution allowance: Essential and Growth include 10 and 200 monthly, respectively. An extra package of 50 AI resolutions costs $49.50 on either plan. Growth also raises included workflow executions to 1,000 and offers more campaigns and tracked visitors. Enterprise pricing is custom and includes flexible usage limits, dedicated account support, SSO, audit logs and a white-label widget. Compare the per-user charge and resolution allowance against expected chat volume before rollout.

ChatBot is presented as a hosted service, not as a self-hosted chatbot server. The vendor doesn't publish an open-source license or a self-hosting path, so teams that require source access or deployment inside their own infrastructure should treat it as a poor fit unless the vendor confirms otherwise.

The agent depends on the knowledge sources, skills, workflows and integrations configured in ChatBot. Before adopting it, ask how to export conversation histories, agent configuration, training sources and analytics, and whether those exports preserve a usable format. The product’s named channels and integrations can reduce switching friction at the customer-facing edge, but they do not guarantee that agent behavior or workflow logic can move to another platform. Plan a migration around rebuilding the bot and validating its answers unless the vendor confirms a portable export.

The published plans put concrete limits on AI resolutions, campaign impressions, workflow executions and tracked live visitors. Growth raises those allowances, while Enterprise offers flexible scaling and usage limits. The vendor lists SOC 2 Type 2, SLAs, SSO and audit logs for Enterprise; confirm the exact SLA, data handling terms and compliance scope with the account team before relying on it for regulated or business-critical support.

The vendor’s homepage describes deployment across several channels and handover to staff, but teams should verify channel-specific behavior, escalation routing and what happens when usage allowances run out. The vendor doesn't publish rate limits or uptime figures on the cited product pages, so ask about them during procurement. Reddit discussion is sparse: one commenter in an ecommerce thread said the service was fine but moved support chats to Telegram over cost and team workflow concerns. Another commenter praised using live chat on their site, but did not clearly identify ChatBot.