There are two models for Telegram subscription bots. In the first, you use a shared platform bot - your subscribers message something like @ChannelManagerBot, which could be serving a hundred other channels. In the second, you have your own bot with your own username: @EliteTipsBot, @ForexSignalsVIP, whatever fits.
The difference seems superficial until you think about it from the subscriber's side.
The subscriber experience
When someone subscribes to your channel and interacts with a bot called @SubsManagerBot or @SubscriptionHandlerPro, they know they are being processed by a third party. It is not a disaster. But it is a signal that you did not build something specifically for them.
A bot under your own name says something different. It says your channel is a proper operation, not just someone's side hustle using someone else's tool. That is a small thing, but small things matter in a trust-dependent business like paid tipping.
Portability
There is also a practical argument. A bot you own is one you can take with you. Your subscriber list, your bot token, your configuration - all under your control. If you ever want to move infrastructure, you can. With a shared bot model, you are somewhat more locked in.
The "but nobody notices" counter-argument
Some operators say their subscribers do not notice or care. That is probably true for a meaningful percentage of people. But "nobody notices the difference" is rarely the right standard to aim for. You notice the difference.
Setup
Creating your own Telegram bot via BotFather takes about three minutes. It is genuinely not technical - you message a Telegram account, follow a handful of prompts, and receive an API token. That is all that is needed. From there, Subs Manager connects to it, and everything else runs automatically.
The naming decision is the hardest part. Apparently people deliberate over bot names for longer than they deliberate over pricing.