# Botable

> Botable is an AI-powered Telegram bot builder. You describe a bot in plain
> language; Botable writes the code, provisions a database, deploys it, and keeps
> it running 24/7. Changes are made by chatting, not by editing files.

## Pages

- [Botable: create Telegram bots with AI](https://botable.io/): Home. What Botable is, how a bot gets built from a plain-language description, and what you can build.
- [Features](https://botable.io/features): Every capability: AI build and edit by chat, managed 24/7 hosting, per-bot SQLite database, live logs, natural-language analytics, Telegram Stars payments.
- [MCP connector](https://botable.io/mcp): Connect Botable to Claude, Cursor or any MCP-capable agent. The agent describes a Telegram bot; Botable writes it, gives it a database, hosts it and keeps it running. Install commands per client.
- [Pricing](https://botable.io/pricing): 5 free credits on signup, then 2 a day. Pro from $20/month and Business from $49/month, with monthly credits from 100 to 1,600 chosen per plan. Hosting is never metered separately.
- [Botable 1000](https://botable.io/1000bots): A thousand working Telegram bots we built with Botable, across twenty-five kinds of everyday thing: lists, habit trackers, quizzes, converters, booking forms. Open any of them in Telegram, or tap Remix and get the same bot under your own name.
- [Telegram bot build guides](https://botable.io/telegram-bots): Thirty-one guides covering the bot types people build most, each with its command surface, build steps, failure modes, and a copy-pasteable prompt.
- [Telegram bot how-to guides](https://botable.io/guides): Twenty-five practical guides to the Telegram Bot API: tokens, BotFather, group permissions and privacy mode, webhooks, rate limits, payments, analytics.
- [Botable video guides](https://botable.io/guides/watch): Twenty screen recordings of Botable itself, building a bot, working with the agent, analytics, broadcasts, Stars payments, Mini Apps, each with a full transcript.
- [Telegram bot builders compared](https://botable.io/compare): Ten comparisons of ways to build a Telegram bot, ManyBot, Chatfuel, SendPulse, Botpress, automation platforms, and writing it yourself. Compared on architecture; no competitor pricing published.
- [Frequently asked questions](https://botable.io/faq): Answers on getting started, bot capabilities, credits and billing, the technical stack, and data isolation.
- [About Botable](https://botable.io/about): What Botable is, how it works under the hood, who runs it, and how to reach a person.
- [Contact](https://botable.io/contact): Support email and Telegram channels, with what each one is for and what to include.
- [Affiliate program](https://botable.io/affiliate): Earn 3 credits when a referred friend creates their first bot, plus 25% of every payment they make, for life.
- [Terms of Service](https://botable.io/terms): The agreement governing use of Botable. Effective 31 March 2026.
- [Privacy Policy](https://botable.io/privacy): What data Botable collects, why, how long it is kept, and your rights. Effective 31 March 2026.
- [Refund Policy](https://botable.io/refund): Refund terms for credits and subscriptions. Effective 12 May 2026.

## Build guides, what to build

- [Crypto price bot](https://botable.io/telegram-bots/crypto-price-bot): A Telegram crypto price bot answers price questions inside a chat. You send a ticker, it replies with the live quote and 24-hour change. Describe that behaviour to Botable in plain language and it writes, hosts, and runs the bot for you.
- [Customer support bot](https://botable.io/telegram-bots/customer-support-bot): A Telegram customer support bot answers the questions you get most, sorts the rest into topics, and escalates anything it cannot handle to a person. Describe your topics and your canned answers to Botable and it builds the whole flow.
- [Quiz bot](https://botable.io/telegram-bots/quiz-bot): A Telegram quiz bot asks a question, offers answers as buttons, scores the reply, and keeps a running leaderboard. Describe your categories and scoring rules to Botable and it builds the question flow, the score table, and the leaderboard.
- [Weather bot](https://botable.io/telegram-bots/weather-bot): A Telegram weather bot returns current conditions and a forecast for a city name or a shared location pin. Describe the format you want, temperature, wind, rain chance, and Botable builds the bot, wires the weather API, and hosts it.
- [News bot](https://botable.io/telegram-bots/news-bot): A Telegram news bot pulls headlines from a feed or news API and delivers them by topic, on demand or on a schedule. Describe your topics and delivery time to Botable and it builds the subscription table, the fetcher, and the digest.
- [Reminder & todo bot](https://botable.io/telegram-bots/reminder-bot): A Telegram reminder bot turns a sentence into a scheduled message. You write "remind me to call the bank at 4pm", it parses the time, saves the task, and messages you then. Describe the phrasing you use and Botable builds it.
- [Group manager bot](https://botable.io/telegram-bots/group-manager-bot): A Telegram group management bot greets new members, states the rules, removes spam, and gives admins moderation commands. Describe your rules and what should happen when they are broken, and Botable builds the whole moderation flow.
- [Booking bot](https://botable.io/telegram-bots/booking-bot): A Telegram booking bot shows your open slots, takes a reservation in a few taps, and reminds both sides before it starts. Describe your hours, slot length and cancellation rules, and Botable builds the availability logic with them.
- [Poll & survey bot](https://botable.io/telegram-bots/poll-bot): A Telegram poll bot collects votes in a group and shows the tally as it changes. A survey bot asks a sequence of questions and stores each answer. Describe which you need, and whether votes are anonymous, and Botable builds it.
- [Translator bot](https://botable.io/telegram-bots/translator-bot): A Telegram translator bot detects the language of a message and returns it in the language you want. In a group it can mirror every message so a multilingual room reads as one conversation. Describe your language pairs and Botable builds it.
- [AI assistant bot](https://botable.io/telegram-bots/ai-assistant-bot): A Telegram AI assistant bot answers questions in a chat, keeping enough conversation history to follow up. Describe its subject, its tone, and what it should refuse, and Botable builds and hosts it with those boundaries in place.
- [Store & payments bot](https://botable.io/telegram-bots/store-bot): A Telegram store bot shows a catalogue, holds a cart, and takes payment inside the chat using Telegram Stars. Describe your products and what happens after payment, and Botable builds the catalogue, the cart, and the order records.
- [Notification bot](https://botable.io/telegram-bots/notification-bot): A Telegram notification bot pushes alerts into a chat from something else, a webhook, a scheduled check, an API. Describe what should trigger a message and who should get it, and Botable builds the endpoint and the routing.
- [RSS feed bot](https://botable.io/telegram-bots/rss-feed-bot): A Telegram RSS bot watches feeds and posts new items into a chat or channel. You add feed URLs, it remembers what it has already sent, and it delivers only what is new. Describe your feeds and cadence and Botable builds it.
- [Captcha bot](https://botable.io/telegram-bots/captcha-bot): A Telegram captcha bot verifies new members before they can post. It restricts each joiner, asks for one tap or a simple answer, and unrestricts whoever passes. Describe the challenge and the timeout, and Botable builds it.
- [Paid access bot](https://botable.io/telegram-bots/subscription-bot): A paid access bot sells membership to a private channel or group. It takes payment in Telegram Stars, issues a single-use invite link, and removes the member when the subscription lapses. Describe your tiers and Botable builds it.
- [Lead generation bot](https://botable.io/telegram-bots/lead-generation-bot): A Telegram lead generation bot replaces a contact form with a short conversation. It asks a few qualifying questions, stores the answers, and routes the promising ones to a person. Describe your questions and Botable builds the flow.
- [Anonymous feedback bot](https://botable.io/telegram-bots/anonymous-feedback-bot): An anonymous feedback bot lets people send a message to admins without their name attached. The bot receives it privately, strips the identity, and forwards the content. Describe your moderation rules and Botable builds it.
- [Giveaway bot](https://botable.io/telegram-bots/giveaway-bot): A Telegram giveaway bot collects entries, checks that each entrant meets the conditions you advertised, draws winners, and announces them with proof the draw was fair. Describe the entry rules, the prize count and the closing time, and Botable builds the entry table and the draw for you.
- [Referral bot](https://botable.io/telegram-bots/referral-bot): A Telegram referral bot gives every user their own tracked link, records who arrived through it, and credits the referrer once the person they invited does something real. Describe the reward and the action that unlocks it, and Botable builds the tracking, the fraud checks and the leaderboard.
- [Expense tracker bot](https://botable.io/telegram-bots/expense-tracker-bot): A Telegram expense tracker bot logs spending from a single message, "12.40 lunch", categorises it, and reports totals on request. Describe your categories and currency and Botable builds the ledger and the reports.
- [Habit tracker bot](https://botable.io/telegram-bots/habit-tracker-bot): A Telegram habit tracker bot asks whether you did the thing, records the answer with one tap, and keeps a streak. Describe your habits, the times to ask, and how a missed day is handled, and Botable builds it.
- [Inventory bot](https://botable.io/telegram-bots/inventory-bot): A Telegram inventory bot tracks what you have, logs what moves in and out, and warns before a line runs out. Describe your items and reorder points, and Botable builds the stock table and the alerts.
- [CRM bot](https://botable.io/telegram-bots/crm-bot): A Telegram CRM bot keeps contacts, notes and follow-ups where your conversations already happen. Add a contact in one line, log what was said, get reminded to chase. Describe your pipeline stages and Botable builds it.
- [Stock market bot](https://botable.io/telegram-bots/stock-market-bot): A Telegram stock bot quotes tickers on demand, tracks a watchlist, and alerts on price moves. Unlike crypto it has to respect market hours and delayed data. Describe your tickers and thresholds and Botable builds it.
- [Sports scores bot](https://botable.io/telegram-bots/sports-scores-bot): A Telegram sports bot follows the teams you choose, posts goals and results as they happen, and lists upcoming fixtures. Describe your teams and how noisy you want it, and Botable builds the polling and the alerts.
- [Flashcard bot](https://botable.io/telegram-bots/flashcard-bot): A Telegram flashcard bot sends you cards to review at the moment you are about to forget them. You rate how well you knew each one and the schedule adapts. Describe your decks and Botable builds the review engine.
- [Job board bot](https://botable.io/telegram-bots/job-board-bot): A Telegram job board bot collects roles through a guided submission flow, posts approved ones to a channel, and alerts job seekers whenever a new listing matches the skills and seniority they saved. Describe your fields and your moderation rule, and Botable builds the flow and the matcher.
- [Form bot](https://botable.io/telegram-bots/form-bot): A Telegram form bot asks form questions one at a time in a chat, validating each answer as it arrives and saving progress. Describe your fields and validation rules and Botable builds the flow and the export.
- [Delivery tracking bot](https://botable.io/telegram-bots/delivery-tracking-bot): A Telegram delivery tracking bot watches a parcel and messages the customer when its status actually changes, rather than every time it checks. Describe your carriers and which events are worth a notification, and Botable builds the polling schedule, the status normalising and the alerts.
- [Event bot](https://botable.io/telegram-bots/event-bot): A Telegram event bot announces an event, collects RSVPs against a real capacity, runs a waitlist that promotes automatically when someone cancels, and reminds everyone before it starts. Describe your capacity, your reminder schedule and whether you need check-in, and Botable builds it.

## How-to guides, how Telegram bots work

- [Create a Telegram bot](https://botable.io/guides/how-to-create-a-telegram-bot): Creating a Telegram bot takes two things: registering it with @BotFather to get a token, and running code that uses that token to answer messages. BotFather takes about thirty seconds. The second part is what people mean when they say building a bot is hard.
- [Bot tokens](https://botable.io/guides/telegram-bot-token): A Telegram bot token is the single credential that controls a bot. You get it from @BotFather with /newbot or /token, it looks like 123456789:AAH…, and anyone who has it can act as your bot completely. Treat it like a password.
- [BotFather commands](https://botable.io/guides/botfather-commands): @BotFather is Telegram's official bot for creating and configuring bots. It handles registration, tokens, profile details, the command menu, privacy mode, group permissions, inline mode and deletion. It does not host or run your bot's logic.
- [Add a bot to a group](https://botable.io/guides/add-bot-to-group): Open the group, go to members, add the bot by its @username, and it joins like any member. Anything beyond reading commands, deleting messages, restricting members, pinning, needs it promoted to admin with those specific permissions.
- [Group privacy mode](https://botable.io/guides/group-privacy-mode): Privacy mode is on by default and limits what a bot receives in groups to commands, replies to its own messages, mentions of itself, and service messages. Turn it off with /setprivacy in BotFather, then remove and re-add the bot.
- [Bot not responding](https://botable.io/guides/bot-not-responding): A silent Telegram bot almost always has one of six causes: the process is not running, a webhook conflict, privacy mode in a group, a missing admin permission, a crashed handler, or rate limiting. Check them in that order, it is roughly the order of probability.
- [Webhooks vs polling](https://botable.io/guides/webhook-vs-polling): A Telegram bot receives updates one of two ways: long polling, where it repeatedly asks Telegram for new messages, or a webhook, where Telegram posts them to your HTTPS URL. You can use one or the other, never both, setting a webhook disables polling.
- [Command menus](https://botable.io/guides/bot-commands-menu): The command menu is the list that appears when someone taps the menu button next to the message box. Set it with /setcommands in @BotFather or the setMyCommands API method. It is the cheapest discoverability improvement a bot can get.
- [Buttons and keyboards](https://botable.io/guides/inline-keyboard-vs-reply-keyboard): Inline keyboards attach buttons to a specific message and send a silent callback when tapped. Reply keyboards replace the user's typing keyboard and send the button's label as a normal message. Inline is right for almost everything.
- [Photos and files](https://botable.io/guides/send-photos-and-files): A bot can send a file three ways: uploading bytes, giving Telegram a public URL to fetch, or reusing a file_id from a file Telegram already has. The third is instant and free, and is what you should use for anything sent repeatedly.
- [Storing data](https://botable.io/guides/store-data-in-a-telegram-bot): Telegram stores nothing on your behalf, each update arrives with no memory of the last. Anything a bot needs to remember has to go in your own database, keyed by chat id and user id. In-memory variables are lost on every restart.
- [Telegram Stars payments](https://botable.io/guides/telegram-stars-payments): Telegram Stars is Telegram's in-app currency for digital goods. A bot sends an invoice, the user confirms inside the chat, and the bot receives a payment event. No external checkout, no card form, no merchant account.
- [Telegram Mini Apps](https://botable.io/guides/telegram-mini-apps): A Telegram Mini App is a web page that opens inside Telegram, launched from a bot. It suits interfaces a chat cannot express well, catalogues, calendars, dashboards, and is unnecessary for anything a few buttons already handle.
- [Bot admin rights](https://botable.io/guides/make-bot-group-admin): Promote a bot through group info, Administrators, Add Admin, then enable individual permissions. Grant only what its features require, Telegram rejects unpermitted actions silently, which is why a bot that does nothing usually has a permissions problem.
- [Posting to channels](https://botable.io/guides/telegram-channel-bot): A bot posts to a channel by being an admin of it with the post-messages right. Add it as an administrator, get the channel id, and send to that id. Channels are broadcast-only, so a bot cannot have a conversation there.
- [Finding chat and user IDs](https://botable.io/guides/get-telegram-chat-id): Every Telegram chat has a numeric ID: positive for private chats, negative for groups, and negative starting -100 for supergroups and channels. The simplest way to get one is a bot command that reports the ID of the chat it was sent in.
- [Rate limits](https://botable.io/guides/telegram-bot-rate-limits): Telegram enforces soft limits on how fast a bot can send: roughly one message per second to a single chat, a higher ceiling overall, and a lower one for bulk sends to a group. Exceeding them gets you throttled with a retry delay, not banned.
- [Broadcasting](https://botable.io/guides/broadcast-to-bot-users): Broadcasting means sending to every stored user id, paced under Telegram's rate limits, with progress saved so a crash resumes rather than restarts. Blocked users return an error you should use to prune your list.
- [Scheduled messages](https://botable.io/guides/schedule-messages): Telegram does not schedule messages for bots, your bot does. Store the message with a send time, run a scheduled check, and send when it is due. The two hard parts are timezones and what to do about missed sends after downtime.
- [Calling external APIs](https://botable.io/guides/connect-bot-to-api): A bot calls an external API from the server side, with the key held in an environment variable, results cached so repeated requests do not hit the provider, and a clear message to the user when the provider is unavailable.
- [Multi-language bots](https://botable.io/guides/multi-language-bot): Telegram sends the user's app language with each update, which is a good default but a poor assumption. Store an explicit preference, keep every user-facing string in one place per language, and let users switch.
- [Deep links](https://botable.io/guides/telegram-deep-links): A Telegram deep link is your bot's URL with a start parameter: t.me/yourbot?start=CODE. The code arrives with the user's first message, which lets you attribute where they came from without cookies or a landing page.
- [Bot analytics](https://botable.io/guides/telegram-bot-analytics): Telegram gives bots no analytics, so you record your own. Four numbers cover most of it: how many people start, how many reach the first useful outcome, how many return after a week, and where conversations stop.
- [Bot security](https://botable.io/guides/telegram-bot-security): Most Telegram bot incidents come from five places: a leaked token, admin commands that anyone can run because nothing checks who sent them, an unverified webhook endpoint accepting forged updates, unvalidated input reaching a database query, and storing far more personal data than the bot needs.
- [What bots cost](https://botable.io/guides/telegram-bot-cost): Telegram charges nothing to create or run a bot, and nothing per message. The real costs are hosting, any paid data APIs, and time. A simple bot can run for nothing; the expensive part is almost always building and maintaining it.

## Video guides, Botable on screen

Screen recordings of the product, all on https://botable.io/guides/watch. Every
one has its full transcript in the page HTML, so the spoken content is readable
without playing anything.

- [Create your first bot](https://botable.io/guides/watch#01-create-your-first-bot): The whole path from an empty description box to a bot people can message. What Telegram issues, what Botable writes and hosts, and where the two meet.
- [Create a bot without BotFather](https://botable.io/guides/watch#02-create-without-botfather): The second route to a token: Telegram creates the bot and hands the token straight to Botable, so you never run /newbot or copy a secret by hand.
- [What a bot token actually is](https://botable.io/guides/watch#03-bot-tokens-explained): A token is not a setting on the bot, it is the bot, and whatever holds the string can act as it. Why Botable checks it on entry, and what to do the day it ends up somewhere public.
- [How to ask the builder for a change](https://botable.io/guides/watch#04-talking-to-the-builder): The builder is an agent with file tools working inside your bot's own directory, on code that is already running. How to phrase a request so it lands the first time.
- [See the plan before it builds](https://botable.io/guides/watch#05-plan-mode): Plan mode has the agent read the bot and describe what it intends to do without writing anything. When that is worth the extra step, and how to approve or redirect the plan.
- [Ask your data in plain language](https://botable.io/guides/watch#06-ask-your-data): A mode in the same chat you build in: ask a question about your bot's own data and the answer comes back drawn as a chart or table, with no metric picker to learn first.
- [The Manage dashboard, row by row](https://botable.io/guides/watch#07-the-manage-dashboard): A tour of the screen a project opens on, the rail of eight rows, what each pane beside it holds, and why five of the rows behave differently from the other three.
- [Read your bot's analytics](https://botable.io/guides/watch#08-read-your-analytics): Every update your bot receives is written down as it arrives, before your bot's code sees it. What each card counts, and which question each one actually answers.
- [Know your audience](https://botable.io/guides/watch#09-know-your-audience): The Audience pane names the people behind the numbers: everyone who has ever messaged the bot, what they touched, and when they were last seen.
- [Export your users](https://botable.io/guides/watch#10-export-your-users): Taking your audience out of Botable as a CSV or a spreadsheet. What each column holds, and how to keep the file useful without keeping it forever.
- [Send your first broadcast](https://botable.io/guides/watch#11-your-first-broadcast): Writing a message to everyone who has used your bot: composing it, sending a test to yourself first, and reading the delivery result once it goes out.
- [Segment and schedule broadcasts](https://botable.io/guides/watch#12-segment-and-schedule-broadcasts): Narrowing a broadcast to part of your audience, watching the recipient count update as you change the selection, and setting it to send at a chosen time.
- [Charge with Telegram Stars](https://botable.io/guides/watch#13-charge-with-telegram-stars): Setting up paid plans priced in Telegram Stars: what each plan includes, what the customer sees inside the chat, and where the payments and customers appear afterwards.
- [Browse your bot's database](https://botable.io/guides/watch#14-browse-your-bots-database): Every bot gets its own SQLite file. How to open the tables it created, read the rows, and confirm that what you think is being saved is actually being saved.
- [The flow view](https://botable.io/guides/watch#15-the-flow-view): The flow view reads your bot's handler files and draws them as a graph, commands, buttons and the paths between them, so the shape of the bot is visible without reading code.
- [Version history and rollback](https://botable.io/guides/watch#16-version-history): Every agent run leaves a version behind. How to read the history, tell the versions apart, and put an earlier one back when a change turns out wrong.
- [Logs, errors and auto-fix](https://botable.io/guides/watch#17-logs-errors-and-autofix): Where a running bot's output and crashes surface, how to read the traceback that comes with one, and the auto-fix path that hands the error back to the agent.
- [Your bot's Telegram settings](https://botable.io/guides/watch#18-telegram-settings): The Telegram-side profile: display name, description, avatar and the command menu. What a stranger sees before pressing Start, and how each one gets set.
- [Build a Mini App](https://botable.io/guides/watch#19-build-a-mini-app): Asking the builder for a Mini App, previewing it in the phone frame inside Botable, and watching the events it fires while you click through it.
- [Secrets and external APIs](https://botable.io/guides/watch#20-secrets-and-external-apis): Giving your bot an API key without pasting it into the code: the agent asks for the value, it is stored as an environment variable, and the bot calls the outside service with it.
- [Why your bot ignores group messages](https://botable.io/guides/watch#21-why-your-bot-ignores-groups): Privacy mode is on by default, so a bot in a group sees commands and almost nothing else. The two ways to change that, and why an existing group has to re-add the bot before either takes effect.
- [Add your bot to a group](https://botable.io/guides/watch#22-add-your-bot-to-a-group): Adding the bot is the easy half. The half that decides whether it works is what it is allowed to see once it is in there.
- [The BotFather commands worth knowing](https://botable.io/guides/watch#23-botfather-commands-worth-knowing): The handful of BotFather commands you will actually reach for, and which of them Botable already does for you so you never type them.
- [Webhooks or long polling](https://botable.io/guides/watch#24-webhooks-or-polling): What the two delivery models cost you in latency and hosting, the one case where polling is genuinely easier, and why anything hosted ends up on webhooks.
- [Give your bot a command menu](https://botable.io/guides/watch#25-give-your-bot-a-command-menu): The menu button beside the message box is how people discover what a bot can do. A command nobody can find may as well not exist.
- [Which keyboard your bot should use](https://botable.io/guides/watch#26-which-keyboard-to-use): Inline keyboards attach to a message and edit in place; reply keyboards replace the user's keyboard and stay. Picking the wrong one is the most common design mistake in bots.
- [How a bot sends photos and files](https://botable.io/guides/watch#27-sending-photos-and-files): By URL, by upload, or by file_id, and why file_id is the one that matters once the same file goes out more than once.
- [Which admin rights your bot needs](https://botable.io/guides/watch#28-bot-admin-rights): Admin quietly turns privacy mode off, which is often the real reason people grant it. Which individual rights each job needs, and why you should stop there.
- [Post to a channel from your bot](https://botable.io/guides/watch#29-post-to-a-channel): Posting to a channel is the same send call with a different chat id. Getting the bot admitted as an admin with post rights is the part that takes a minute.
- [Find a chat ID or a user ID](https://botable.io/guides/watch#30-find-a-chat-or-user-id): Usernames change and IDs do not, which is why everything durable keys on the ID. What the negative numbers mean, and where Botable already shows you them.
- [Stay inside Telegram's rate limits](https://botable.io/guides/watch#31-stay-inside-telegram-rate-limits): The published ceilings are soft and Telegram may change them. What a 429 actually asks you to do, and what paces your sends for you.
- [Send it later, or every morning](https://botable.io/guides/watch#32-schedule-messages): Telegram has no scheduler for bots, so something on your side has to hold the clock. The no-code route through a scheduled broadcast, and the in-bot route through cron.
- [Make your bot speak more than one language](https://botable.io/guides/watch#33-make-your-bot-multilingual): Telegram hands you the user's language on every message, so you rarely have to ask. Keeping strings in one place is what makes the second language cheap.
- [Track which link sent you each user](https://botable.io/guides/watch#34-deep-links-that-track-growth): A start payload turns every post, ad and partner into a measurable source, so you stop guessing which one is carrying the growth.
- [The security mistakes that cause incidents](https://botable.io/guides/watch#35-bot-security-basics): The token is the bot. Callback data is user input. Those two sentences cover most of what goes wrong.
- [What a bot actually costs](https://botable.io/guides/watch#36-what-a-bot-actually-costs): Telegram charges nothing. The bill, when there is one, comes from keeping a process alive around the clock and from whatever APIs the bot calls.
- [Build a support bot that opens tickets](https://botable.io/guides/watch#37-build-a-support-bot): The prompt that produces a working ticket flow, what the branching looks like afterwards, and where the tickets are stored.
- [An FAQ bot that shows what people ask](https://botable.io/guides/watch#38-build-an-faq-bot): Five answers behind five buttons, and then the useful part: a ranking of which ones people actually press, so the FAQ improves from evidence.
- [Collect emails with a waitlist bot](https://botable.io/guides/watch#39-build-a-waitlist-bot): Capture a contact, store it, export it. Including the part about these being real people who can withdraw consent.
- [Build an order bot for your shop](https://botable.io/guides/watch#40-build-an-order-bot): A menu, a cart and a confirmation, and why a cart belongs on inline buttons that edit in place rather than a stack of new messages.
- [A booking bot that cannot double-book](https://botable.io/guides/watch#41-build-a-booking-bot): Showing slots is easy. Not selling the same slot twice is the whole problem, and it is solved in the database rather than in the message.
- [Build a daily digest bot](https://botable.io/guides/watch#42-build-a-daily-digest-bot): A scheduled push that people keep. The cron side, the pacing side, and the honest warning about what an unasked-for daily message does to your mute rate.
- [Build a quiz bot with a leaderboard](https://botable.io/guides/watch#43-build-a-quiz-bot): Questions, scoring and a leaderboard, the first thing you build that has to remember something between messages.
- [Answer from a live API or a sheet](https://botable.io/guides/watch#44-connect-a-live-data-source): Asking for the integration in plain language, the inline form the builder shows when it needs a key, and why the answer should be cached.
- [Gate a paid community with Stars](https://botable.io/guides/watch#45-gate-a-paid-community): Setting a plan, what the customer sees inside the chat, and checking entitlement before you serve anything.
- [Getting your first hundred users](https://botable.io/guides/watch#46-your-first-hundred-users): The share link, the QR, and tagged deep links so you learn which channel worked. Plus the reason a bot posted without a reason to press start converts badly.
- [A broadcast people do not mute](https://botable.io/guides/watch#47-a-broadcast-people-dont-mute): Segmenting instead of blasting, one clear reason to open, and testing on yourself first. Then reading delivered against failed.
- [What your retention numbers mean](https://botable.io/guides/watch#48-read-retention-honestly): What day one, seven and thirty actually count, why a window reads zero until the bot is old enough, and what a strong day one with a weak day seven is telling you.
- [What to charge for your bot](https://botable.io/guides/watch#49-what-to-charge): Stars are bought inside Telegram, so the friction is low and the unit is unfamiliar. Pricing against the job rather than the feature list.
- [Your bot stopped answering](https://botable.io/guides/watch#50-five-minute-triage): The checks in the order that finds it fastest: asleep, token, logs, and whether the error you are looking at is even current.

## Comparisons

We compare on architecture, not price, and deliberately publish no competitor
pricing: a stale number is a false claim about someone else's business. Every
comparison also states where the other tool is the better choice.

- [Botable vs ManyBot](https://botable.io/compare/botable-vs-manybot): ManyBot assembles a bot from fixed commands, autoposts and broadcasts, configured inside Telegram. Botable writes an actual program from your description. The dividing line is whether your bot needs to remember things, calculate, or call an API, ManyBot's model does not extend there.
- [Botable vs Chatfuel](https://botable.io/compare/botable-vs-chatfuel): Chatfuel is a multi-channel visual flow builder, you draw conversations as connected blocks and deploy them across messaging platforms. Botable generates a real Telegram program. The choice is mostly breadth against depth: several channels shallowly, or one channel without a ceiling.
- [Botable vs SendPulse](https://botable.io/compare/botable-vs-sendpulse): SendPulse is a marketing platform, email, SMS, push, with a visual chatbot builder as one component. Botable does one thing: it writes Telegram bots. If chat is one channel in a wider marketing stack, the suite wins on consolidation.
- [Botable vs Botpress](https://botable.io/compare/botable-vs-botpress): Botpress is a conversational-AI platform with a visual studio, code extensibility and many channels, powerful and aimed at people comfortable building. Botable turns a plain-language description into a running Telegram bot. The split is who is doing the building.
- [Botable vs coding it yourself](https://botable.io/compare/botable-vs-coding-it-yourself): Writing it yourself gives complete control and no vendor. It also gives you the hosting, the deploys, the dependency updates and the 3am restarts. Botable generates the same kind of program and keeps it running. The trade is control against maintenance.
- [Botable vs Zapier & Make](https://botable.io/compare/botable-vs-zapier-and-make): Zapier and Make connect apps: when something happens in one service, do something in another, including sending a Telegram message. That is automation, not a bot. If your requirement is genuinely "notify me when X", they are the better tool.
- [ManyBot alternatives](https://botable.io/compare/manybot-alternatives): People look for a ManyBot alternative for one of two reasons: they have outgrown fixed commands, or they want something more actively maintained. The right replacement depends entirely on which, the options differ completely.
- [Chatfuel alternatives](https://botable.io/compare/chatfuel-alternatives): The right Chatfuel alternative depends on whether you still need several channels. If you do, another multi-channel flow builder is the like-for-like move. If Telegram is where your audience actually is, a Telegram-first tool goes deeper.
- [Telegram bot builders compared](https://botable.io/compare/telegram-bot-builder-comparison): There are five ways to build a Telegram bot: menu builders, multi-channel flow builders, marketing suites, AI builders that generate code, and writing it yourself. They differ less in features than in where each one stops.
- [Drag-and-drop vs AI builders](https://botable.io/compare/drag-and-drop-vs-ai-bot-builders): A drag-and-drop builder configures a shared engine, your bot is a set of settings it interprets. An AI builder writes a program. The first is bounded by the blocks on offer; the second by what the Telegram API allows.

## Key facts

- One credit builds a bot; one credit makes a change to it.
- New accounts get 5 free credits. No credit card required.
- Plans (monthly, cancel anytime):
  - Free: $0, 5 credits on signup
  - Pro: $20/month, 100 credits per month
  - Business: $49/month, 100 credits per month
- Unused credits roll over and do not expire while the account is open.
- Hosting is never billed separately, bots run 24/7 at no extra cost on every plan.
- Bots are built on grammY (Node.js) and served over webhooks.
- Every bot gets its own isolated SQLite database, named database.db.
- Users supply a Telegram bot token from @BotFather; it is stored server-side and never shown in the UI.
- Built-in: Telegram Stars payments and subscriptions, broadcasts, live deployment logs,
  a chat preview, natural-language analytics over the bot's own data, and Telegram Mini Apps.
- No external server, container registry, or hosting account is needed.

## Contact

- Support email: support@botable.io
- Support chat: https://t.me/botablesupport
- Community (English): https://t.me/BotableEnglish
- Community (Russian): https://t.me/BotableRussian

## Notes for fetchers

- Canonical origin: https://botable.io
- Sitemap: https://botable.io/sitemap.xml
- Everything above is rendered server-side and readable without JavaScript.
- Paths under /projects, /admin and /billing are the signed-in application and are not indexable.