Chatbase focuses on customer-experience agents that use a business’s own information. It is relevant when visitors repeatedly need help finding support instructions and the company wants a conversational route to that knowledge. The practical strength is the combination of company sources, a website-facing experience and options for connected actions and human escalation.
This guide is researched from official documentation, not a hands-on product review. The strongest first project is a narrow support job with an owner: explain the published account process, point to the right instruction and pass unresolved questions to the team. That scope makes both the value and the maintenance requirement easier to understand.
Where Chatbase fits well
A business with a useful help collection can make that information easier to reach without rewriting every answer manually. Begin with the questions support already receives, then organize approved sources around those tasks. Delivery instructions, service availability and onboarding steps are plausible starting areas when the business can keep them current.
Connected actions may support a more complete service, but choose each action deliberately. Explaining an account setting is different from changing private account information. Confirm the current integration, plan and authorization requirements before enabling an action that affects a customer’s account.
What the support workspace gives you
- One maintained answer collection. Use approved business pages and files to help visitors find a useful instruction.
- A route beyond an answer. Actions can collect an enquiry, call a connected service or pass a request to a person. Configure operations the service actually supports.
- A way to improve the service. Review conversations, inspect credit usage and run simulated scenarios before changing the customer-facing setup.
For a first release, prepare five recurring questions, one source owner and one human handover. That gives the team a concrete service to evaluate.
Current plans and buying considerations
The official pricing snapshot reviewed on 14 October 2026 listed Hobby at US$40 month to month, Standard at US$150 and Pro at US$500. The advertised annual monthly equivalents were US$32, US$120 and US$400; those figures describe annual billing. Confirm the full payment, tax and selected term at checkout.
| Plan | Includes | Useful when | Limit to check |
|---|---|---|---|
| Hobby | One agent; 700 monthly message credits; two members; 10 MB of sources; five actions per agent. | A narrow support assistant can work from a maintained source set. | Required integrations and the model-specific cost of a real conversation. |
| Standard | One agent; 4,000 credits; three members; 20 MB; eight actions. Adds source resync, API, helpdesk, voice and advanced integrations. | The service needs connected support or scheduled source updates. | Confirm the actual integration, permissions and handover behaviour. |
| Pro | One agent; 15,000 credits; five members; 40 MB; twelve actions. Adds advanced analytics and source suggestions. | A larger service needs the extra capacity or analysis tools. | Additional agents and branding removal remain separately priced add-ons. |
Message credits are model-dependent. Measure a representative conversation, including follow-up questions and review work, rather than promising one completed answer per credit. Monitor usage and alerts: the agent can stop responding when usable credits run out. Any automatic recharge is a separate spending choice.
The source documentation describes supported files and automatic processing of changes. Scheduled source resynchronization has plan-specific conditions. Keep a source owner and confirm an important policy change reaches the assistant through the actual configured update path.
Choose the feature that completes the service
- Describe the complete route from the visitor’s question to an answer or a human.
- Check the specific connection and source-update route that service requires.
- Trial ordinary questions, an uncertain answer and a failed handover before expanding the deployment.
What to prepare before launch
Create an approved source pack and a short acceptance question set. Include straightforward questions, ambiguous wording and a request outside scope. Define the human handover and keep the ordinary contact route visible. Review the final widget on phone and desktop so it does not cover the action the visitor came to complete.
Measure useful resolutions, unnecessary handovers and source gaps alongside credits. A polished answer that sends someone to an obsolete instruction still needs correction. Review early conversations to improve the knowledge collection and assign a named person to keep it current.
Continue with the detailed workflows
Use our website-support workflow to plan scope, sources, answers and escalation. The pricing guide explains how credits, seats, source room and integrations affect the subscription decision. Together they provide a route from a support problem to a maintained service without assuming that a larger plan automatically creates better answers.
Chatbase is a strong candidate when the company’s knowledge is valuable and the recurring difficulty is helping visitors find and use it. Start with one clear support task, prove the handover and expand from reviewed demand.
Plans & costs
Compare the full commitment and the work each plan includes. Recorded observations are not a current checkout quote.
AI tools
USD · US / global observations
Chatbase · Hobby — monthly
- Initial term & commitment
- Initial term amountUS$40.001 month termPublished base monthly subscription rate; additional usage and tax are separate.
- Renewal
Check local tax at checkout
Price observed 2026-10-14
Plan details & sources
A focused website-support agent with a limited monthly workload.
700 message credits; 1 AI agent; credits used depend on the selected model.
Choose another option if: Choose a higher tier when required integrations or usage exceed this plan.
Global USD pricing page; checkout country and tax not selected · Check local tax at checkout
Renewal: Future renewal amount and any additional usage should be checked before subscribing.
Check local tax at checkout
Prices checked 2026-10-14Official price source ↗Observed 2026-10-14
Official price evidence ↗Chatbase · Standard — monthly
- Initial term & commitment
- Initial term amountUS$150.001 month termPublished base monthly subscription rate; additional usage and tax are separate.
- Renewal
Check local tax at checkout
Price observed 2026-10-14
Plan details & sources
Support workflows that need integrations and a larger credit budget.
4,000 message credits; API, helpdesk integrations, voice and automatic source updates as listed.
Choose another option if: Check the selected model and action consumption before estimating traffic.
Global USD pricing page; checkout country and tax not selected · Check local tax at checkout
Renewal: Future renewal amount and any additional usage should be checked before subscribing.
Check local tax at checkout
Prices checked 2026-10-14Official price source ↗Observed 2026-10-14
Official price evidence ↗Chatbase · Pro — monthly
- Initial term & commitment
- Initial term amountUS$500.001 month termPublished base monthly subscription rate; additional usage and tax are separate.
- Renewal
Check local tax at checkout
Price observed 2026-10-14
Plan details & sources
A larger established support workload.
15,000 message credits; expanded capacity; credit consumption varies by model.
Choose another option if: Do not treat the allowance as a fixed number of completed conversations.
Global USD pricing page; checkout country and tax not selected · Check local tax at checkout
Renewal: Future renewal amount and any additional usage should be checked before subscribing.
Check local tax at checkout
Prices checked 2026-10-14Official price source ↗Observed 2026-10-14
Official price evidence ↗Recorded prices can change. Check eligibility, taxes and the current full bill with the provider. Different currencies and services are shown separately.
Sources and verification
Editorial review 2026-10-19. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- Chatbase current plansChecked Plan capacities, actions, included agent, integrations and separately priced additions.
Limits: Official public documentation rechecked 19 October 2026. Describes documented capabilities, not tested account entitlement, product performance, final checkout or conversion results. - Chatbase product informationChecked Customer-experience agents trained on business sources, connected actions and escalation to a human.
Limits: Official documentation reviewed on the stated date. Plan boundaries can change; this is not a hands-on product test. - Chatbase source collectionChecked Supported source inputs and automatic processing; scheduled resynchronization depends on plan.
Limits: Official documentation reviewed on the stated date. Plan boundaries can change; this is not a hands-on product test. - Chatbase usage and alertsChecked Model-dependent usage, alerts and exhausted-credit behaviour.
Limits: Official public documentation rechecked 19 October 2026. Describes documented capabilities, not tested account entitlement, product performance, final checkout or conversion results. - Chatbase actionsChecked Connected actions, human handoff and procedures-only setting; availability is channel- and integration-specific.
Limits: Official documentation checked on 18 October 2026; vendor documentation is not an independent performance test. No checkout, account entitlement or live product test was performed. - Chatbase TestsChecked Mock/live boundaries and separate test credits. No live write operation is proven by a simulated test.
Limits: Official documentation checked on 18 October 2026; vendor documentation is not an independent performance test. No checkout, account entitlement or live product test was performed.