Most writing communities end up testing three or four bots before settling on one. If Make is on your shortlist, this breakdown will save you that trial and error. Here is what it does, what it lacks, and how it stacks up against BotWave.
Make is a no-code automation platform where you piece together Telegram actions manually and pay per operation. It is a no-code automation tool. For some use cases that is fine. For running a live writing community where members want to participate, share, and stay engaged, it falls short in ways that cost you time and members.
These are the specific limitations that writing communities run into with Make:
A writing community does not need five stacked bots. BotWave handles moderation, engagement, AI, games, and growth in one place, which is where Make leaves gaps.
Here is what a writing community actually does with BotWave on a normal day:
| Capability | BotWave | Make |
|---|---|---|
| Monthly cost | Free forever | Paid tiers required |
| Per message fees | $0 | Yes |
| 24h reply window | No limit | Restricted |
| Commands | 200+ | Limited |
| Group size | 200,000 | Capped lower |
| Inline games | Yes | No |
| AI assistant | Built in | Limited |
| Crypto tracking | Yes | No |
| Media downloads | 8 platforms | No |
| Trust scores | Yes | No |
| Karma and levels | Yes | No |
| Mini app dashboard | Yes | No |
Most competitors in the no-code automation space price per message, per seat, or per campaign. BotWave does not. Here is what that means for a writing community.
| Usage | BotWave | Make |
|---|---|---|
| 1,000 msgs/day | $0 | $5 to $80/day |
| 10,000 msgs/day | $0 | $50 to $800/day |
| Hosting | $0 | Self host or paid |
| Command | What it does |
|---|---|
/welcome | Greet new members with sharing rules |
/poll | Vote on feedback |
/notes | Share draft notes |
/ai | Help with writing prompts |
If you are already running Make and want to move to BotWave, the migration is straightforward. Here is the step-by-step for a writing community.
Take a typical writing group: 2,000 members, a few hundred messages a day, and a volunteer admin team. Here is what happened after they switched.
Before the switch, the group was running {comp} for its one feature and two or three other bots for the rest. Admins spent more time managing bots than managing the community. Spam slipped through, engagement was flat, and new members left within a week.
After adding BotWave, the admins turned on welcome, captcha, karma, and polls in the setup wizard. Within three days, spam dropped to near zero because captcha blocked bot accounts at the door. Karma gave regular contributors a visible reputation, and the leaderboard created a light competitive loop that pulled lurkers into the conversation.
The AI assistant handled questions that admins used to answer manually. Reminders pinged the group before events, and the notes module replaced a cluttered pinned-messages chain. The group went from five bots to one, admin workload dropped, and daily active members climbed.
The admin team now spends zero time on bot maintenance and all of their time on the community itself. That is the difference between a tool that does one thing and a platform that runs the whole group.
Here is the honest summary of why writing communities switch from Make to BotWave.
Keep Make if its specific feature is all you need. Switch to BotWave if you want your writing group to have moderation, games, AI, and growth in one free bot.
Yes. /ai generates prompts and /notes pins draft notes.
Yes. /poll lets the group vote on feedback for drafts.
Yes, completely free with no per-message fees and no member limits.
Add BotWave now and put your writing group on autopilot. No per-message fees, no 24-hour window, no limits.
Add BotWave in 30 seconds. No registration, no payment, no setup.
Add BotWave to Telegram