The short answer
Most chatbot integration projects cost between $8,000 and $35,000 for a bot wired into your website, calendar, and CRM, with subscription widgets running $0 to a few hundred dollars a month for FAQ-only setups. Adding voice, SMS, or multiple systems pushes a quote toward the high end. Hourly rates run $100 to $250.
"How much does a chatbot cost" gets a different answer depending on what you mean by chatbot. A subscription widget that answers FAQs from your website copy is close to free. A bot that checks your calendar, books the slot, and creates the lead in your CRM is a scoped project, typically $8,000 to $35,000 depending on how many systems it touches. We wrote about what that wiring involves in chatbot integration services explained; this post is about the number itself, what moves it, and what a fair 2026 quote should include.
What actually drives chatbot integration cost up or down?
Four variables explain most of the spread between a $500 widget and a $30,000 build.
Number of systems connected. A bot that only talks does not need to be expensive. The moment it has to check availability, write a CRM record, or open a helpdesk ticket, each connection is its own piece of API work, and the cost scales with how many systems it has to reach agreement with.
Channel. Text chat on a website is the cheapest surface to build for. Adding SMS or a phone-based voice agent means real-time speech handling and a different integration path into your phone system, which is meaningfully more engineering than a chat window.
Knowledge grounding. A bot that answers from a handful of FAQ pages is quick to set up. One that has to read your live pricing, inventory, or policy documents accurately, and stay current as those change, needs a grounding layer that gets rebuilt into the quote.
Handoff and monitoring. Rules for when a conversation routes to a person, plus a way to review transcripts after launch, add build time up front but are what keeps a bot from drifting once it is live. Skipping this line is the most common way a cheap quote turns into an expensive redo.
What do the common price bands cover?
Treat these bands as what the 2026 market charges rather than a published rate card. A real number comes from your own conversation volume and the systems the bot has to reach.
| Tier | Typical range | What it usually covers |
|---|---|---|
| Widget | $0 to $500/mo, or $1,500 to $5,000 one-time | FAQ-only bot on your website, scripted or lightly trained on your existing copy |
| Core build | $8,000 to $18,000 | Website chat wired to calendar and CRM, single language, basic handoff rules |
| Multi-system build | $18,000 to $35,000 | Adds helpdesk or order lookups, SMS or voice, deeper grounding, transcript monitoring |
| Enterprise | $45,000+ | Multiple brands or languages, compliance requirements, custom escalation workflows |
Two notes on the table. First, a widget is a legitimate answer for a lot of businesses, not a downgrade; a bot that only fields "what are your hours" does not need CRM wiring, and paying integration-tier money for that is money spent on nothing. Second, ongoing cost after launch is rarely zero. Assume a line item for keeping the bot working when a connected tool ships a breaking change, whether that takes the form of a light monthly watch or a rate you can call on as needed.
Widget or integrated build: how do you tell which one you need?
The test is what happens at the end of a good conversation. If the visitor still has to call or email you to finish the job, the bot is a widget doing everything a widget can do, and paying more will not change that. If the bot itself books the meeting, files the lead, or resolves the ticket, that requires wiring into the tools where the work actually lives, and that is what pushes the price into the Core or Multi-system bands.
The stakes of getting the channel right are higher than they look. Gartner's research projected that chatbots would become the primary customer service channel for roughly a quarter of organizations within five years of its 2022 report, putting that shift squarely in the 2027 window we are now approaching. A channel that is about to carry a quarter of an industry's service volume is worth wiring into the systems that make it useful rather than leaving it stuck at "call us."
We scope chatbot integration as a fixed quote after mapping which conversations the bot should own and which systems it needs to reach. The service page sets out how that mapping session runs.
What should a real chatbot integration quote include?
Before signing anything, the document in front of you should name every system the bot connects to, what it is allowed to do in each one without a person approving it, what happens when it cannot answer, and what monitoring exists once it is live. It should also state a price that holds unless the scope changes.
If any of those are missing, you have an estimate, not a quote, and chatbot estimates have a habit of growing once the CRM connection turns out to be more involved than a form field suggested.
FAQ
How much does chatbot integration cost for a small business?
A scoped build for a small business usually falls between $8,000 and $35,000, and a single-website, single-CRM job sits at the bottom of that. A widget-only FAQ bot can cost a few thousand dollars or be handled entirely by a $0 to $500 per month subscription tool.
Is chatbot integration a one-time cost or an ongoing one?
Both. The build itself is a one-time project, but the bot depends on APIs from tools you do not control, and those change. Price in some form of aftercare, whether that is a light monthly watch or a rate you can call on. If a quote carries no ongoing line at all, ask who is watching the bot once it ships.
Why does connecting to my CRM cost more than the chat window itself?
Because the chat window is a UI and the CRM connection is where the business logic lives: matching a caller to an existing record, deciding what counts as a qualified lead, handling what happens when two systems disagree about a customer's status. That work is invisible to a visitor and is most of what a Core-tier quote is actually paying for.
Can I just start with a subscription widget and upgrade later?
Yes, and for many businesses that is the right sequence. A widget answers the "does this help at all" question cheaply. Once you know which conversations are common enough to be worth automating end to end, that scope becomes the spec for the integrated build, which tends to produce a tighter quote than starting from a blank page.