Written and maintained by Ersan Jahed Tabrizi · Updated November 11, 2026
The short answer
A small-business chatbot can start around $149 for a narrow Telegram FAQ flow, while a lead-capture or booking workflow commonly starts around $189-$249. A bot connected to a CRM, database, payment flow, private customer data, multiple languages, or an AI model needs a custom scope and can cost substantially more.
The useful question is not “How much is a chatbot?” It is “What exact customer task should this first version complete, and what must happen when the bot cannot complete it?”
Typical small-business chatbot budgets
| Scope | Practical starting range | What it normally includes |
|---|
| FAQ or menu bot | $149-$250 | Buttons, maintained answers, contact handoff, basic usage log |
| Lead-capture bot | $189-$350 | Qualification questions, consent notice, structured summary, admin alert |
| Booking or request bot | $219-$450 | Request flow, preferences, confirmation, calendar or human handoff |
| AI-assisted answers | $350-$900+ | Approved knowledge source, prompt rules, fallback, usage limits, monitoring |
| CRM or custom integration | Quote required | Authentication, field mapping, error recovery, testing, ongoing maintenance |
These are planning ranges, not universal market prices or binding quotes. Geography, taxes, hosting, paid APIs, platform rules, content preparation, and support expectations can change the total.
What changes the price most?
- Number of user paths: one clear flow is easier to build and test than many overlapping journeys.
- External systems: CRM, calendar, spreadsheet, email, payment, and database connections each add setup and failure handling.
- AI usage: the model bill may be small, but source preparation, guardrails, testing, fallback, and monitoring add work.
- Sensitive data: customer records, financial details, health information, or private documents require stronger security and may be unsuitable for a small fixed-scope project.
- Languages and content: every maintained language needs approved copy, testing, and a process for future updates.
- Support expectations: a handoff with a short defect window differs from continuous operations and content maintenance.
Monthly costs after launch
A simple Telegram bot may use a small hosting service and no paid messaging API. AI usage, databases, monitoring, email or SMS alerts, premium automation connectors, and high-volume infrastructure can create recurring fees. Ask who owns each account and who responds when an integration fails.
Total first-year cost = build + hosting + paid APIs + integrations + content maintenance + support
How to avoid paying for the wrong first version
- Choose one audience and one measurable customer task.
- Write the ideal flow from start to human handoff.
- Separate required features from ideas for later.
- Confirm third-party fees and account ownership.
- Agree on testing, revisions, source or deployment handoff, and support.
- Measure completion rate, qualified leads, response time, or staff time saved after launch.
Choose the right path
A focused Telegram bot is useful for menus, FAQs, lead qualification, requests, and group or channel automation. A shared WhatsApp inbox is better when several staff members need assignment, history, roles, tickets, and human conversation management. A larger website or application project needs a broader implementation scope.
