Your platform has two Telegram features with similar names, and they serve completely different people. Get them straight once and a whole category of confusion goes away.<\/p>\n\n\n\n
This is the customer facing product. Their business messages its own audience on Telegram.<\/p>\n\n\n\n
What it covers:<\/p>\n\n\n\n
Setup is unusual in a good way: the business creates its own bot through Telegram’s BotFather and pastes the token in. The platform registers and maintains the inbound webhook from there. No carrier, no sender ID, no template approval queue.<\/p>\n\n\n\n
This is the operations plugin. It sends platform alerts to admins over Telegram: low balance warnings, application monitoring, new sender name requests, SMPP session alerts, support ticket notifications and similar.<\/p>\n\n\n\n
Nobody’s customers are involved. This is your own team’s pager.<\/p>\n\n\n\n
A Telegram bot cannot message a person or chat that has never messaged it first. There is no API call that starts a conversation with a stranger. The user has to send \/start or tap through a link before the bot can reach them.<\/p>\n\n\n\n
This catches out every customer who imports a contact list and expects it to work like SMS. Tell them during the sales conversation, not after they have bought it.<\/p>\n\n\n\n
The usual way to build the audience is deep links of the form Telegram publishes its limits, and they are not generous for bulk:<\/p>\n\n\n\n Set expectations with volume customers accordingly. Telegram is excellent for engaged, opted in audiences, and poor as an SMS replacement for cold lists.<\/p>\n\n\n\nhttps:\/\/t.me\/botname?start=payload<\/code>, which open a chat with the bot and pass a parameter to its start handler. Customers put those behind QR codes, ads, emails, SMS and WhatsApp messages, so each new subscriber arrives already identified.<\/p>\n\n\n\nTelegram’s own rate limits<\/h3>\n\n\n\n
\n
Which one your customer means<\/h3>\n\n\n\n