AI customer support · Independent documentary review

Chatbase Review (2026): Pricing, Credits & Key Limits

By SmartCreatorHub · Published October 31, 2026 · Official sources checked October 31, 2026 · Lire en français

Chatbase is worth evaluating when you want a hosted AI support agent that uses your company’s knowledge, connects to business tools and hands difficult cases to people. The buying decision comes down to three questions: which plan supports your workflow, how many credits that workflow may consume, and what you can verify before customers depend on it.

Our verdict

A useful shortlist option for recurring support, with a budget and an owner. Start from one support journey with a known answer and a clear human fallback. Hobby can suit a modest public-knowledge deployment; Basic becomes relevant when you need its API, Helpdesk or other gated functions. A low-volume FAQ alone may not justify the subscription and maintenance.

Explore Chatbase Compare plans and requirements

Affiliate disclosure: we may earn a commission if you subscribe through our Chatbase links. This assessment uses official documentation; we have not run a hands-on Chatbase benchmark. Worked examples and the estimator below are illustrative calculations. Read our method.

What does Chatbase do, and who is it for?

Chatbase builds AI agents from business content and connects them to customer-facing channels and Actions. Its current scope includes website chat, email, messaging and voice, plus a Helpdesk. It is broader than a chatbot that answers questions about one PDF. Functions and integrations still depend on the plan. Official product scope.

Our assessment is strongest for a team that already has reliable help content and repeatable requests. The agent can become another way to use that material. If policies are missing, contradictory or changing without an owner, installing an agent adds another place where those problems reach customers.

Our assessment: start with the support job, not the feature count
Your situation	Why evaluate Chatbase?	What decides the purchase
A small public FAQ	An agent can answer recurring questions from maintained content.	Whether useful demand justifies subscription and upkeep.
A SaaS support team	Knowledge, connected workflows and escalation can share a process.	The required integrations, plan access and human coverage.
A store with order or billing requests	Actions can extend an answer into a connected task.	Identity checks, permitted operations and evidence of the outcome.
An occasional question on a quiet site	The maintenance may outweigh the benefit.	Whether a good FAQ and contact route already solve the problem.

A useful evaluation question is specific: “Can this agent answer our delivery-policy question, recognize when the order needs a person, and preserve the context?” “Can AI handle our support?” is too broad to produce a defensible result.

Chatbase pricing: choose the plan by the workflow

The paid grid checked on October 31, 2026 uses Hobby, Basic and Business, alongside custom Enterprise pricing. Some indexed pages still use Standard and Pro. Use the current purchase grid for plan names and entitlements. Dollar figures below are USD. Check the current pricing page.

Paid plans checked October 31, 2026; credits renew monthly
Plan	Monthly / annual billing	Included monthly credits	Decision-relevant access
Hobby	$40/month; $32/month billed yearly ($384/year)	700 message credits; 200 test credits	2 members; 5 Actions per agent; basic integrations.
Basic	$150/month; $120/month billed yearly ($1,440/year)	4,000 message credits; 500 test credits	3 members; 8 Actions; API, Helpdesk, voice and auto-resync.
Business	$500/month; $400/month billed yearly ($4,800/year)	15,000 message credits; 1,000 test credits	5 members; 12 Actions; advanced analytics, source suggestions and tickets as a source.
Enterprise	Custom quote	Custom usage and agreed terms	Evaluate for requirements such as SSO, custom permissions, SLAs and eligible HIPAA arrangements.

Each listed self-serve paid plan includes one agent and 40 MB of training content. Annual figures are an annual commitment expressed per month, not a monthly cancellation option. The annual totals above are our arithmetic from the displayed rates.

Which plan should a small team consider?

Start with the feature gate. A small credit requirement does not make Hobby suitable if your application needs the API or native Helpdesk. Conversely, a higher allowance alone does not establish that Business will improve answer quality. Choose the lowest plan that supports the whole journey, then estimate its usage and operational cost.

Free plan versus seven-day trial

Chatbase’s official summary still mentions Free, while the current public pricing cards emphasize paid plans with seven-day trials. We have not verified the Free sign-up path or exact quotas for a new account. Confirm what your account offers rather than relying on an old “50 credits” table or assuming the free option has disappeared.

Add-ons that can change the budget

Public add-on prices; use the applicable billing interval
Requirement	Advertised price	Budget implication
Additional usage	$40 per 1,000 message credits	Recharge purchases and any existing balance affect cash paid.
Another agent	$25 per agent/month	Budget beyond the single included agent.
Remove the Chatbase badge	$99/month	A small deployment can spend more on branding than on its base plan.
Extra storage	$25 per 10 MB/month	Check whether better source selection solves the need first.

Branding removal and a custom domain are different requirements: the workspace guide reserves the custom-domain add-on for Enterprise. Before packaging Chatbase for clients, establish the workspace arrangement, required agents and branding scope. Do not assume removing a badge provides a fully white-labelled platform.

Check Chatbase’s available plans

How Chatbase credits affect your real cost

A credit allowance is not a conversation allowance. Model selection affects the credit rate, an exchange can contain several AI replies, and Actions may lead to additional billable model requests. The current recommended-model table has tiers of 1, 2, 4 and 5 credits. Check the selected model’s rules, including its treatment of tools.

For planning, add the billable requests in your expected journey and multiply each by the applicable credit rate. The examples here assume a fixed rate throughout; they do not establish measured Chatbase consumption or imply that every Action always doubles the cost.

Illustrative credit budgetConversations × billable requests per conversation × credits per request

Three hypothetical workloads, before testing or other usage
Scenario	Explicit assumptions	Estimated credits/month
A modest FAQ	100 conversations × 2 requests × 1 credit	200
A longer support journey	300 conversations × 3 requests × 2 credits	1,800
That journey with extra tool-related work	300 conversations × 4 billable requests × 2 credits	2,400

The last example adds one assumed billable request per conversation. Usage rises by one-third, not by a universal factor of two. At six credits per conversation, Hobby’s 700-credit allowance covers 116 complete conversations arithmetically; it does not promise that real chats will follow that pattern.

A concrete budget comparison

In the 2,400-credit example, Hobby is short by 1,700 credits. Valued at $0.04 per additional credit, that is $68 of recharge consumption and $108 including the $40 base plan. This is an allocated cost, not a promise of a $108 invoice.

If your recharge configuration purchases blocks of 1,000, buying two blocks would cost $80: an illustrative first-month outlay of $120, with 300 recharge credits left. Basic is $150 before other charges, but may still be necessary for an API or Helpdesk workflow. Check the actual recharge settings and existing balance before treating either calculation as a bill.

The published recharge price is $40 per 1,000, and Chatbase says recharge credits do not expire. Subscription credits have a different expiry rule. All examples exclude tax, exchange rates, implementation work and any separate channel or provider charges. Recharge pricing.

What happens when credits run out?

The Chatbase FAQ documents renewal on the first of each month and an unavailable-agent message after exhaustion. Decide whether to enable auto-recharge, set a budget and monitor usage. An unattended credit meter can become a support-availability problem.

Knowledge quality determines what you can trust

Chatbase accepts websites, files, text, Q&A and Notion, with support tickets available under eligible arrangements. Uploaded PDF, TXT, DOC and DOCX files can be up to 20 MB each and must contain selectable text; a scanned PDF without a text layer needs preparation first. Data Sources requirements.

The guide documents weekly automatic resync for external sources on Basic, Business, Enterprise and legacy Pro. That is not a promise of instant updates whenever your website changes. Changes made directly to knowledge sources are processed separately from configuration drafts.

Our recommendation is to start with the smallest authoritative source set: current policies, approved product information and the questions support actually receives. Remove superseded versions and resolve conflicts before asking an agent to interpret them. More uploaded content can increase ambiguity when nobody owns its accuracy.

Example: a changed return policy

If a store changes its return window, record the effective date, replace the obsolete source and check the answer against the new policy. Then ask a question the source does not answer, such as an exception for an overseas order. A helpful-sounding exception is still wrong if the policy never authorized it.

What Chatbase tests prove—and what they do not

Chatbase’s testing feature runs conversations with a simulated customer and an AI judge. You define the success criterion and can assert expected Actions. By default, Actions return simulated success; Live mode is limited to supported read-only operations. Write Actions and Custom Actions cannot run live in these tests. Testing behavior and limits.

A passing refund scenario is not evidence that money moved. Read the transcript and Action results, and distinguish a mocked response from a real operation. A production acceptance check needs evidence from the connected system as well as the chat.

Tests also need a credit budget

Test credits are shared across agents in the account, and message credits can be used after that allowance runs out. Hypothetically, 20 scenarios repeated three times, with four agent replies at two credits each, need 480 credits. With Hobby’s 200 test credits unused, 280 would come from production; Basic’s 500 would cover that simplified example.

Our starting evaluation would check a known answer, a missing answer, conflicting information, a failed Action and the human fallback. These are proposed checks, not tests we performed. Judge the answer and the outcome separately.

Drafts and rollback: understand the boundary

The October 30 changelog announces drafts and version history. Supported configuration changes can be prepared before publication, and the Playground uses the draft. However, version restoration is not a complete snapshot of everything affecting the agent. Documented version scope.

A short change-control map from the version guide
Change	Documented treatment	What to check
Instructions, Actions and Procedures	Supported changes are staged in a draft.	Test the intended setup and inspect what will be published.
Data Sources and training	Take effect separately; restoring a version does not revert them.	Keep a source-change record and recheck knowledge.
App connections, channel on/off and security settings	Outside the draft/restoration boundary.	Validate these directly after a change.
API configuration updates	Go live immediately rather than waiting in a draft.	Do not assume the dashboard publication step protects them.

For a policy-sensitive agent, keep two records: the published configuration and the source material available at that time. Otherwise, restoring yesterday’s instructions may still leave today’s changed policy in place. That is an operational reason to document the rollout, not merely a new feature to list.

Human handoff: a live person or a ticket?

Chatbase offers two distinct routes. Escalations creates a ticket for asynchronous follow-up in an already configured helpdesk. Chatbase Live Chat routes to a person in the enabled Chatbase Helpdesk in real time; the AI stops handling the conversation while the customer waits.

Someone needs help now

Use the live route only where it is supported and your team can respond. Check where the request arrives, whether the person receives the context and what the customer sees while waiting.

The request can wait

A ticket can provide a more honest next step. Explain what happens next and collect the details the team needs, rather than suggesting a person has already joined.

The native Live Chat guide lists Chat Bubble, Help Page, Center Stage, email, Instagram, Messenger and WhatsApp. Slack is not on that list. General channel availability must not be read as support for every Action on every channel.

Our practical buying check is an out-of-hours request. If nobody is available, does the user get a clear follow-up route? A bot that can technically escalate has not solved the staffing question.

Data privacy and the work behind private Actions

Chatbase says connected customer data is not used to train models and describes encryption in transit and at rest. Its security page reports SOC 2 Type II compliance and HIPAA support for eligible Enterprise workspaces. These are the vendor’s statements; we have not independently examined its audit report. Security and compliance scope.

The privacy policy describes US processing. “Not used for training” does not mean “stored only in Europe.” Retention, transfers and deletion are separate questions to review in the Data Processing Agreement for your use case.

A public FAQ and account access are different projects

A delivery-policy answer can use public knowledge. An answer about a customer’s invoice needs trustworthy identity and authorization. Chatbase documents signed-token identity controls, while Custom Actions can connect the agent to APIs or other behavior. The existence of a visual builder does not establish that your private-data workflow is ready.

Define which records the customer may access, which operations the agent may request and how the backend rejects invalid requests. Record an error path and a human fallback. This work belongs in the deployment budget alongside the subscription.

Chatbase pros and cons: our assessment

Reasons to shortlist it

A hosted agent workflow covering knowledge, connected tasks and human support.
Several model-cost tiers to evaluate against a bounded workload.
Documented testing and version controls that help structure a rollout.
Public documentation detailed enough to expose important operating limits.

Trade-offs to budget for

Credits do not translate into a fixed number of resolved conversations.
Required features can force a higher plan at low traffic.
Knowledge maintenance and private integrations need an owner.
Mocks, rollback exclusions and staffing require checks beyond the feature list.

These are conclusions from the documented workflow. They are not a measured ranking against other agents. In particular, this review establishes neither a support-resolution rate nor that a more expensive model will improve your own outcomes.

When to consider an alternative

If your main job is messaging operations with campaigns and contact management, compare the operating model in our Heyy.io review. Both products cover more than simple Q&A; choose by the journey and its limits, rather than calling one “multichannel” and the other “knowledge only.”

If the real requirement is sales pipelines and a broader CRM process, use our HubSpot vs HighLevel comparison to assess that separate decision. If your existing helpdesk already handles the journey well, evaluate its agent option before adding another knowledge base and inbox to maintain.

For a quiet site, a clear FAQ and reliable contact form may be the more useful starting point. The right comparison includes the staff time to keep either solution accurate.

Final verdict: is Chatbase worth it?

Shortlist Chatbase when recurring support has become a maintained workflow, not an occasional question. Its documented combination of knowledge, Actions, testing and human support makes it worth evaluating. Start with one journey, choose a plan that enables it and compare the observed credit use with a budget you can sustain.

Commit only when the answer is grounded, the important Action has a verifiable result and the customer has a clear path to a person. Those checks will tell you more than the number of features or an unqualified promise to automate support.

Evaluate one real support journey

Bring a known question, an exception and an escalation case. Compare what the account actually offers with the requirements in this review.

Explore Chatbase and check current plans Revisit the credit estimate

Affiliate link. Free access, trials and paid entitlements should be confirmed in your account.

Chatbase review FAQ

Is Chatbase worth paying for?

It is worth evaluating when a recurring support workflow needs company knowledge, connected Actions and a human fallback. Choose the plan by required features and measured usage. For an occasional FAQ, a separate agent subscription may add little value.

Does Chatbase have a free plan or just a trial?

Chatbase still mentions a Free plan in its official summary, while the current public pricing cards emphasize paid plans with seven-day trials. We have not verified new-account Free access or its exact current quotas. Do not treat Free and the paid-plan trial as the same offer.

Are 700 credits enough for 700 conversations?

Not generally. At two credits per billable model request and three requests per conversation, 700 credits cover 116 complete conversations. That is illustrative arithmetic, not measured capacity; model choice, Actions and conversation length change the result.

Can I use the API on Hobby?

The current pricing comparison lists API access on Basic and Business, not Hobby. If the API is required, choosing solely by a low credit requirement can lead to the wrong plan.

Does Chatbase support human handoff?

Yes. Escalations opens a ticket for later follow-up, while Chatbase Live Chat routes to a person in the enabled Helpdesk in real time. The channel must be compatible and a staffed team is needed for an immediate response.

Does restoring a version restore the old knowledge sources?

No. Data Sources and training are outside the documented restoration scope. Restoring agent configuration therefore does not restore the previous knowledge base. Keep a separate record of source changes.

Does removing Chatbase branding include a custom domain?

These are separate requirements. Branding removal is a paid option; the workspace documentation restricts the custom-domain add-on to Enterprise. Check the arrangement your agency or brand actually needs.

How we researched this review

We checked Chatbase’s official pricing, guides, changelog and policy pages on October 31, 2026, and compared the questions they answer with the buying decisions a support team faces. We also reviewed competing coverage to identify information that needed a current primary source.

This is a documentary review. We did not create a product account, run customer conversations, perform a live refund or measure accuracy, speed or a time saving. The calculations and recommendations are our analysis. Our editorial approach explains how we distinguish documentation, observations and affiliate relationships.

Sources

Official sources checked October 31, 2026. Pricing and account entitlements can change. Documentation links below support the specific facts discussed above.