How to build a lightweight CRM bot on Telegram
By the Botable team
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.
What is a crm bot?
A Telegram CRM bot is not a replacement for a sales platform; it is a replacement for the notes nobody writes. Real CRMs fail small teams for a friction reason — logging a call means leaving the conversation, opening a tool and filling a form, so it happens on Friday from memory or not at all. A bot that accepts "note acme: wants pricing by Friday" in the chat you are already in gets used. The data model is three tables: contacts, interactions appended against a contact, and follow-ups with a due date. The follow-up is the part that produces value, because the entire discipline a CRM is meant to enforce is remembering to come back. Pipeline stages are worth adding only if they change what you do; three stages people actually update beat eight that decay into fiction within a month.
What commands does it have?
| Command | What it does |
|---|---|
/add <name> | Creates a contact |
/note <name> <text> | Logs an interaction against them |
/next <name> <when> | Sets a follow-up reminder |
/who <name> | Their full history in one message |
/pipeline | Contacts grouped by stage |
What do you need before you start?
- A Telegram bot token from @BotFather
- Your pipeline stages — three or four, named for decisions not feelings
- Whether it is personal or shared with a team
How do you build it?
Why does logging have to be one line?
Because anything longer does not happen. The measure of a CRM is not what it can store but what actually gets stored, and every field you require is another reason to do it later. Ask for a single free-text line that attaches to a contact by name.
What makes follow-ups work?
A due date on a row and a scheduled message when it arrives — pushed to you, not waiting in a list you have to check. A follow-up you must remember to look for is not a follow-up.
How many pipeline stages should there be?
Three or four, each naming a decision: contacted, qualified, proposal, closed. Eight-stage pipelines are updated for a fortnight and then stop reflecting reality, at which point the pipeline view is actively misleading.
Can a whole team share it?
Yes — run it in a group, store contacts against the chat rather than a person, and attribute each note to whoever wrote it. Say this up front, because a personal CRM and a shared one differ in the data model, not just permissions.
A prompt you can use as-is
Paste this into Botable and adjust the details. It is specific on purpose — a vague description produces a vague bot.
Build a lightweight CRM bot. /add <name> creates a contact with optional company and handle. /note <name> <text> appends a dated interaction. /next <name> <when> sets a follow-up and messages me when it is due, understanding "friday" and "in 2 weeks". /who <name> returns the contact with their full interaction history. Stages are contacted, qualified, proposal and closed; /stage <name> <stage> moves them and /pipeline groups contacts by stage with counts. Attribute every note to the Telegram user who wrote it. /due lists everything I owe a follow-up on today.
Who is this bot for?
- Solo founders and consultants whose deals live in chat
- Small sales teams who abandoned a real CRM for being too heavy
- Anyone who keeps client context in their head and loses it
What goes wrong with this kind of bot?
- Required fields are the reason logging stops; keep it to one line
- Follow-ups that sit in a list instead of arriving as a message do not get actioned
- More than four stages and the pipeline becomes fiction within a month
Questions about crm bots
Can it sync with a real CRM?
It can push to one via an API if you name the endpoint and the field mapping. A common setup is the bot as the fast capture layer and the platform as the system of record, which removes the friction without abandoning the tooling.
Can it capture leads automatically?
Yes — combine it with a lead qualification flow so an inbound conversation creates the contact and its first note without anyone typing them.