If you are running an advertisement on a Telegram bot, the main question is not “how to beautifully design buttons”, but where are the applications located and who works with them?. The most common pain that people come to us with: the bot collects contacts, but the manager manually copies them from the correspondence into the table, some of the leads are lost, and no one knows where the client came from. Bunch telegram bot → lead collection → google tables (and in parallel CRM) closes this once and for all: the application gets into the table within seconds after the person clicks “Submit”, without manual transfer and without losses.
globall.dev is a Telegram bot studio. Over the past 3+ years, we have launched 17+ bots in production, and collecting leads with uploading to spreadsheets and CRM is one of the most popular scenarios. Below we will look at how it works technically, what to choose - a table, CRM or both, how much it costs and how long it takes to launch. With a specific example from a real project.
Why collect leads through a Telegram bot?
A landing page with a form and a Telegram bot solve the same problem—capturing a contact—but behave differently. The bot lives where the client is already located, does not require filling out fields on the mobile keyboard one at a time, is able to push through dialogue and immediately provides a two-way communication channel. For traffic from Telegram channels, Reels, Stories and QR codes, this is often more converting than the usual form.
But the bot itself is only an “input”. The value comes when the lead automatically ends up where it is processed: in Google Sheets for quick glances and uploads and/or in the CRM for the sales funnel. It is this “pipe” from the first message to the row in the table that we are designing.
How a link works: from a message to a row in a table
The scheme that we assemble in each such project consists of four links:
- Capture. A person opens a bot (often via a deep-link with a source tag), the bot guides him through a short questionnaire: name, phone number/contact, whatever is needed. You can use inline buttons so you don’t have to type by hand.
- Validation. The bot checks your phone, email, and required fields. A crooked contact will not be included in the table as garbage - the client is politely asked to repeat it.
- Saving. The application is immediately written to the bot’s own database (this is “insurance”), and from there to Google Sheets and/or CRM.
- Notice. The manager receives a lead card in the work chat with the “Get Hired” / “Called” buttons, and the client receives confirmation that the application has been accepted.
Technically, uploading to Google Sheets is done through a Google service account and the Sheets API: the bot is authorized using the key, finds the desired sheet and adds a line. No copy-pasting - the data is structured into columns from the moment it appears.
Why is the retry queue important?
An amateur bot writes directly into the table: if Google is unavailable at that moment or the API limit is exceeded, the application is simply lost, and no one will know about it. In a production bot, there is a queue between the bot and the external service: the lead is already recorded in the bot’s database, and the entry in Sheets and CRM comes with retries. If it didn’t register the first time, it will be added automatically, and you will receive an alert about the failure. This error handling for the Telegram API and external services, monitoring and backups are included in every bot by default, and not for an additional fee.
Google Sheets or CRM - what to choose
A common question on the brief is: “Do we need a table or just a CRM?” The answer depends on how the sales department is structured. Short comparison:
| Criterion | Google Sheets | CRM (CRM / CRM) |
|---|---|---|
| When it's enough | 1–2 people, simple registration of applications, quick uploads and summaries are needed | There is a sales department, stages of the transaction, tasks and control of managers |
| Start | In hours - minimal setup | You need a CRM account and funnel setup |
| Funnel and stages | By hand (statuses in the column) | Out of the box - the lead gets to the right stage on its own |
| Source analytics | UTM/tags column + pivot table | Source fields + CRM reports |
| Cost of ownership | Free | CRM subscription |
In practice, the best option for a growing business is both at the same time: the bot writes a lead both in Google Sheet (a live log of requests that can be conveniently opened from your phone and uploaded to an accountant) and in CRM at the desired stage of the funnel. Duplication is configured so that one lead is not lost in any of the channels. You can start with a table and add CRM later - the architecture allows this without rewriting the bot.
Real example: leads from Telegram directly to CRM
A good example of an "adult" version of this problem is case with integration of Telegram bot and CRM. The original problem was classic: leads from Telegram were lost between chat and CRM, the source of the application was unknown — the manager did not understand which advertisement the person came from, and some of the contacts ended up in correspondence.
What we did: each lead now gets to the desired stage of the CRM funnel with a UTM source and two-way chat - manual transfer zero. The manager responds to the client directly from CRM, and the same message is sent to Telegram; the source (where the lead came from) is entered automatically via deep-link. This is the same “pipe” capture → validation → saving → notification, only the final point is CRM instead of a table (and often both together). If you already have CRM or CRM, we will connect the bot with them; if there is no CRM, start with Google Sheets and add CRM when you grow up.
What goes into the table: list of fields
To ensure that the table immediately becomes a working tool and not a dump, we lay out the structure of the columns in the brief. Basic set for a lead bot:
- Date and time applications (according to your time zone);
- Name and contact (phone/@username/e-mail) - validated;
- Substance of the request — what the client needs (from a questionnaire or free text);
- Source — label from deep-link (advertising campaign, post, QR code);
- Telegram ID — so that you can write to the client again;
- Status — column for the manager (“new”, “call”, “closed”);
- Link to dialogue or application ID in the bot database.
Checklist: what a bot should be like to collect leads
If you order such a bot (from us or somewhere else), check what is included in it:
- ✅ Validation of contacts - no garbage gets into the table;
- ✅ Source tags via deep-link - you can see where the lead came from;
- ✅ Recording in Google Sheets and/or CRM via a queue with retrays;
- ✅ Duplicating a lead in the bot database as insurance against losses;
- ✅ Instant notification to the manager with action buttons;
- ✅ Protection against spam and flood (rate-limit, anti-bot);
- ✅ Monitoring and alerts in case of failures, database backups;
- ✅ You have the source code - the bot can be developed without being tied to a contractor.
How much does it cost and terms
The estimate is fixed in the contract before the start, payment is staged, we show a demo every 2-3 days. Tariff guidelines for the task of collecting leads:
| Tariff | What's included | Price | Deadline |
|---|---|---|---|
| Starter | Bot questionnaire, validation, recording leads in Google Sheets, notification in chat | Quote on request | 5–7 days |
| Business | + integration with CRM, source tags, branched funnel, lead cards with buttons | Quote on request | 10–14 days |
| Turnkey | + multiple sources, complex logic, admin, analytics, load | Quote on request | 3–5 weeks |
| Mini App/Product | Full-fledged Telegram application with forms, personal account and integrations | Quote on request | 3–5 weeks |
For most tasks, “collect requests from advertising into a table and notify the manager” is enough Starting tariff. As soon as the sales department gets involved and you need a funnel, we move on to Business with CRM. Full price list and cost calculator are on the services page.
Common mistakes that burn your budget
In order for the bot to actually generate leads, and not just “be”, avoid three pitfalls: a long questionnaire (each extra field reduces the conversion - ask the minimum, get the rest in the dialogue); direct entry without a queue (applications are lost due to API failures); lack of source tags (without them, you don’t know which advertising is paying off, and you’re wasting your budget blindly). All this is decided at the design stage - that’s why we always start with a short brief, and not straight away with the code.
FAQ
How much does a Telegram bot cost for collecting leads and uploading them to Google Sheets?
A simple bot questionnaire with recording applications in Google Sheets - “Start” tariff Quote on request, period 5–7 days. If you need integration with CRM, an extensive funnel and notifications to managers, this is “Business” Quote on request, period 10–14 days. Complex scenarios with Mini App and several sources - “Turnkey” Quote on request.
Is it possible to connect both Google Sheets and CRM at the same time?
Yes. The bot can simultaneously write a lead in Google Sheets as a live log of requests and send it to CRM (CRM, CRM) to the desired stage of the funnel. The table is convenient for quick viewing and uploading; CRM is convenient for the work of the sales department. Duplication is configured so that one lead is not lost in any of the channels.
What happens if Google Sheets is temporarily unavailable?
The lead is first recorded in the bot’s own database, and the entry in Google Sheets and CRM goes through a queue with repeated attempts. If the external service is unavailable, the request is not lost: it will be added automatically when the connection is restored, and you will receive a notification about the failure.
Where does the source of the application come from in the table?
The bot catches deep-link at startup (for example t.me/yourbot?start=instagram_may) and writes the source label next to the lead. So in the table and in the CRM you can see which advertisement, post or QR code the client came from, and you can calculate the cost of a lead by channel.
How long does it take to launch such a bot?
A bot questionnaire with uploading to Google Sheets is launched in 5–7 days. Version with CRM, notifications and source analytics - in 10–14 days. We show a demo every 2-3 days, the estimate is fixed in the contract before the start.