Pricing guide

For a small website, the real price is the first limit you hit.

A plan can look cheap until replies, conversations, seats, AI resolutions, source limits, actions, handoff, or branding removal become the paid part.

Editorial pricing-meter board showing small-website chatbot costs, message usage, seats, and handoff limits.

Short answer

For a small website, the cheapest-looking chatbot is not always the cheapest usable setup. One tool may charge around message credits, another around support conversations, another around users, and another around AI resolutions.

Start with the job. If you only need website answers, message credits and source limits matter most. If you want live support handoff, seats and conversation limits matter. If the bot is meant to qualify leads, trigger actions, or sit inside a support inbox, add-ons and workflow limits can matter more than the headline plan price.

If your main worry is what gets expensive later, read the companion guide to AI chatbot pricing traps. If your main question is which meter grows first, use the scenario guide to AI chatbot scaling costs. If you need a deeper explanation of the units before you shortlist, read message credits vs conversations. If source coverage is the first gate, check which AI chatbots can answer from your website.

Buying frame

Compare the unit, not just the monthly price.

A small site with a few hundred questions a month has a different cost profile from a support desk where AI resolves customer conversations. These weights are editorial guidance for checking pricing, not product scores.

Pricing weighting

What changes the bill

The cost drivers we check before turning pricing into buyer advice.
Usage unit clarity Core check
Low-volume fit Small sites
Handoff cost Seats/inbox
Source limits Docs/data
Overage risk Watch closely
Add-on pressure Production gap

First-Limit Math

Find the first limit that would make the cheap plan stop working.

A small-site pricing check should start with the first limit you are likely to hit, not the lowest monthly number on the page. For one website that might be message credits. For another, it might be seats, live-chat handoff, AI actions, branding removal, or source capacity.

Step 1

Name the job

Decide whether the chatbot is answering website questions, capturing leads, handing off support, or running actions.

Step 2

Translate the job into a billing unit

Map that job to the thing the vendor charges for: message credits, billable conversations, AI resolutions, seats, source size, actions, or visitors reached.

Step 3

Estimate the first busy month

Use a realistic month of traffic, support questions, handoffs, and team members instead of the quietest week on the site.

Step 4

Check the failure mode

Find out whether the tool auto-bills, asks for a manual top-up, stops replying, removes branding only on a higher tier, or needs another product for handoff.

Step 5

Pick the first plan that survives the limit

Choose the lowest plan where the likely first limit does not break the workflow you actually need in production.

Pricing units

The terms that actually matter.

These units are not interchangeable. Treat them as clues about what the vendor is built to sell: a trained website bot, a source-controlled AI agent, a support desk, or a broader customer-service workspace.

Message credits

FastBots, Chatbase

The allowance used when the bot replies or consumes model output.

Check: Model choice can change the credit burn, so one visitor question is not always one unit of cost.

Billable conversations

Tidio

A support conversation volume unit, closer to customer-service workload than source-only FAQ usage.

Check: Compare it against your support volume, not against another tool's message-credit count.

Lyro AI conversations

Tidio

Tidio's AI-agent conversation allowance for Lyro.

Check: This can sit beside Customer Service and Flows limits, so check the bundle you actually need.

Per-user seats

ChatBot.com / Text

The support-workspace price is tied to each user on the plan.

Check: A low entry price can change quickly when more staff need access.

AI resolutions

ChatBot.com / Text

AI-handled conversations that end without the customer asking for more help.

Check: Overage packages matter if the AI starts handling meaningful support volume.

Training size

FastBots, Chatbase

How much website, document, or knowledge-base material the bot can use.

Check: Small brochure sites may be fine on low limits; consultant, ecommerce, or documentation-heavy sites may not be.

Tool notes

Where each tool gets expensive or useful.

The numbers below were checked on official pricing pages on June 6, 2026. Use them as a buying frame, not as a permanent price table.

FastBots

Checked price signal

Free, then $39/mo or $33/mo billed annually for Essential

Best when

Small sites that want a straightforward trained chatbot with concrete message-credit and crawl-page limits.

Check before choosing

Advanced models use more credits per reply, so heavy AI usage can burn allowance faster than the headline message number suggests.

Check FastBots

Chatbase

Checked price signal

Free, then $32/mo billed annually for Hobby

Best when

Source-heavy sites that care about controlled knowledge, AI actions, and clear training-size limits.

Check before choosing

Costs can move through message credits, AI actions, extra agents, and branding removal rather than one simple chatbot price.

Check Chatbase pricing

Tidio

Checked price signal

Starter shows $24.17/mo on the annual view; Growth starts at $49.17/mo

Best when

Teams that want AI plus live chat, ticketing, support handoff, Flows, and a broader customer-service setup.

Check before choosing

Tidio pricing mixes billable conversations, Lyro AI conversations, and Flows visitors reached. Check the product mix before comparing it with a lightweight FAQ bot.

Check Tidio pricing

ChatBot.com / Text

Checked price signal

$25/user/mo monthly or $19/user/mo annually for Essential

Best when

Support teams that want an AI agent inside a broader Text workspace with inbox, ticketing, workflow automation, and business channels.

Check before choosing

The AI cost story includes per-user seats, included AI resolutions, and automatic 50-resolution packages when limits are reached.

Check ChatBot.com

Buyer scenarios

Pick the plan around the job.

01

Simple website answers

Check: Message credits and source size

Start with how many questions the site gets and how much approved content the bot needs to read.

02

Lead capture or quote intake

Check: Message credits, forms, actions, and integrations

Price the first useful workflow: ask better questions, capture details, and hand off to a person.

03

Live support handoff

Check: Seats, inbox features, billable conversations, and AI resolutions

A support workspace can be worth paying for, but it should be compared as a workflow, not as a cheap chat widget.

04

Automation beyond answers

Check: AI actions, Flows reach, Zapier/Make paths, and add-ons

Treat actions and downstream automation as production work. Test before the bot books, bills, or promises anything.

Buying checklist

Before you pay for a plan.

A useful pricing comparison should make the likely monthly bill clearer. It should not turn changing plan tables into a fake universal winner. When you know the job and need a starter tier, use the small-business chatbot plan picker.

  • Estimate volume: How many real visitor questions, support conversations, or lead forms do you expect?
  • Check the unit: Are you buying replies, conversations, users, resolutions, actions, visitors reached, or source capacity?
  • Check handoff: Will one person manage the inbox, or does the whole team need seats?
  • Check overages: What happens when the allowance runs out?
  • Check production add-ons: Branding removal, extra bots, custom domains, automations, or extra credits may change the real plan.

Sources checked

Official pricing sources.

Pricing was checked against official vendor pages on June 6, 2026. Recheck before relying on exact plan amounts or packaging.

FAQ

AI chatbot pricing for small websites: common questions.

Which chatbot plan fits a low-traffic small website best?

There is no single answer because the cheap-looking entry plan is not always the usable one. For a brochure site with mostly source-trained Q&A, FastBots Essential and Chatbase Hobby are the two starter plans to inspect first. For a support-led store with live chat and inbox needs, Tidio Starter is the natural first check, and Lyro is a separate add-on on top of that. If the team already runs on a per-seat help-desk model, ChatBot.com by Text lists Essential at $19 per user/month billed yearly, with 1 AI Agent, 10 AI resolutions, an AI Copilot, inbox and ticketing system, workflow automation, and business channels. Pick around the workflow, not the headline figure.

Reviewed · Sourced from ChatBot.com pricing

Does removing the chatbot vendor's branding cost extra?

On most tools, yes. Branding removal is a common upsell rather than a feature included in the entry plan. Chatbase sells a branding add-on whose pricing page tagline says it will remove the Chatbase branding from your deployed agents. FastBots gates branding control behind higher tiers and notes a Premium-plan option to hide FastBots branding on widgets. If the chatbot needs to look like part of the brand from day one (consultant, agency, ecommerce), price the branding step explicitly. See the companion AI chatbot pricing traps guide for how branding removal interacts with other usage meters.

Reviewed · Sourced from Chatbase pricing , FastBots pricing

How useful are the free chatbot tiers for a real small website?

Free tiers are useful for a one-week test, not for a production launch. Chatbase 's Free plan lists 50 message credits/month and 0 AI Actions per AI agent — usable for a demo, but the action limit alone blocks Shopify or CRM workflows. Tidio 's pricing page documents 50 Lyro AI Agent conversations (one-off) on the Starter tier, which is a non-renewing allowance. Free tiers are great for proving the concept and showing internal stakeholders, but the budget for the first real month needs to assume a paid plan on whichever tool clears the trial.

Reviewed · Sourced from Chatbase pricing , Tidio pricing

Does the model the chatbot uses change the monthly bill?

Yes, on platforms that bill in message credits. FastBots documents this directly: GPT-4o = 5 Message credits per response, while GPT-4o Mini = 1 Message credits per response. That means a chatbot pointed at a frontier model can consume credits five times faster than the same chatbot pointed at a small model, with no change in visitor volume. Before settling on a plan, decide which model the chatbot will actually use in production and stress-test the credit burn against a realistic month of replies.

Reviewed · Sourced from FastBots pricing

What happens when a small chatbot hits its monthly allowance?

Overage behaviour differs sharply between vendors and is the most under-priced part of a small-site comparison. ChatBot.com automatically tops up: when you hit your monthly limit, Text automatically adds 50 more resolutions, and anything used gets billed at your next renewal. FastBots takes the opposite approach, saying you can easily buy more credits to add to your account or just upgrade to a higher plan with more message credits. Auto-billing pack overages are convenient but can produce a surprise invoice; manual top-ups give cost control but can break the bot during a busy period. Decide which behaviour fits the team before signing.

Reviewed · Sourced from ChatBot.com pricing , FastBots pricing

Decision recap

If this, then that.

  • Pick FastBots Essential — for a brochure site that mostly needs trained answers from approved pages and files.
  • Pick Chatbase Hobby — if source control, custom actions, and clearer training-size limits matter early.
  • Use Tidio Starter — if live chat, ticketing, and support handoff sit alongside the chatbot from day one.
  • Use ChatBot.com — if a per-user help-desk model with AI resolutions matches how the team already works.
  • Test on a free tier — only for a one-week demo; the first real month should assume a paid plan.