Have you noticed that when you create bots, you get tasks that repeat from project to project? Creating a list of tasks will speed up your work and increase your professionalism in the eyes of the customer. Let's collect our own database of such solutions.
Automate team creation
Create templates directly in the bot
Why customize chains of messages over and over again, if you can duplicate them We start a separate bot, in which we create what we repeat from bot to bot and later start building from duplication. What exactly can be duplicated, we will understand further.
Collect information about what is happening in the bot
Connect Google table
A table is essentially a database that extends the capabilities of the bot builder. With its help, you can analyze who hangs up at what stage, what is the yield in the bot, as well as set up interaction with subscribers.
We recommend you to read the video instructions: Integration with Google Table and How to output information from Google Table.
Later we will release a separate post on how to work with a connected table using formulas.
Get all important notifications on time
Connect a Telegram group
With it it is much more convenient to keep track of all the latest information and quickly respond to the most different events, for example:
A new subscriber appeared. You can immediately see a notification about it designed in your style.
It is necessary to understand the source from which the person came. At the same time, all information can be duplicated in tables.
A user responded to a questionnaire. We will promptly receive detailed information about the user.
It is necessary to confirm the application. You can also customize from the group.
Form daily and weekly reports with all the necessary data. It is also convenient to collect them in the group.
A subscriber's paid access to the product has expired. You will learn about it and can contact for casdev.
Reanimate interest in the bot and customize touches
Remind about browsing through scripts
In each bot, it is advisable to set up a series of taps so that those who are distracted from watching can get a reminder and get back to watching.
We create a script that restarts each time a key command is invoked. In this scenario, the reminder intervals are multiples, e.g. reminder on day 1, 3, 7,15, 30.
The point is not to overfeed with touches. In this case, there is a high probability that the subscriber will simply block the bot.
Eliminate failures
Increase Google Tables limits
If the customer's bot is planned to have a high load in the moment, it makes sense to connect several tables, read more: How to increase the limits of Google tables.
Improve communication in the bot
Customize the ability to ask a question to the author
Anyone, even the most savvy person, can get stuck at some point in a bot. Give him the opportunity to ask a question:
Through dialogs.
Through the button with the transition to a personal account.
Through a form to submit a request.
Create a controllability effect for the bot author
Set up a personal account
This is not an obvious solution and is more about the wow effect for the customer. We create a hidden button, accessible only to the owner of a separate category, for example admins. Add yourself and those who need access to the hidden information to that category.
Application options:
Post links to important sources. Tables, groups and so on, so that the customer is not lost in the abundance of information.
To formalize the issuance of access to paid products manually. For example, the bot owner wants to gift access or give it in exchange for a casdev. Or the customer just transferred money to the card and you need to perform the action manually.
Customize the transition between different types of access. For example, the bot for those who have paid for access and those who have not paid can look different. Most often, the customer cannot simply switch between modes - this task can be solved through the personal cabinet.
View data from Google tables directly in the bot, uploading them to the Google slider.
Collect data for further development of the bot
Keep your own list of metrics
Most often at the bot building stage, customers do not think at all about how we will measure the bot's efficiency. And even if you are building a purely technical solution, without funnels and product approach, you can still collect data.
For example:
Number of subscribers and unsubscribes per day.
Total number of subscribers.
How many times total people filled out a survey or clicked on a command in a day.
How many people subscribed to the feature.
How many received it by subscription today.
For example, 3% of subscribers miss even the first button in the bot. 82% reach the end of the chain and so on. All this data can be collected using variables. And upload them to a table for clarity.
This is not the whole list of solutions. Write which one you'd like us to break down in more detail, and we'll continue in the next publications.






