A seller connects Telegram in 1CS to send order and shipping updates, picks a brand-new customer’s order, and the push message never lands — no error the customer notices, just silence. Telegram’s own rule is the cause: a bot cannot send the first message in a chat. The customer has to message the bot, or tap Start, before it can ever reach them. For an order placed on a marketplace or over the phone, that moment may never happen on its own.
Why the first message never arrives
Telegram’s developer documentation is direct about this: “Users will see a Start button the first time they open a chat with your bot” (Telegram Bot Features) — which only happens once a user opens the chat themselves, by searching the bot’s username or following a link to it. Try to message someone who never did that and the send simply fails, because by Telegram’s own design a bot is never the side that starts the conversation. A customer who blocked the bot after talking to it before fails the same way from the outside — but only the never-started case is fixable by inviting the customer to message first.
This is also a different failure from Telegram’s group Privacy Mode, which hides ordinary group chat from a bot that’s already a group member. That problem is about a bot that’s present but deaf; this one is about a bot that’s never been introduced at all — the fix is getting the customer to open the chat once, not a BotFather setting.
The rate limit that catches you next
Once a customer has started the chat, sending still has to respect Telegram’s own throttles. Its FAQ page states them plainly: “In a single chat, avoid sending more than one message per second,” bots in a group “are not be able to send more than 20 messages per minute,” and for bulk notifications “the API will not allow bulk notifications to more than ~30 users per second” unless the bot has paid broadcasts enabled (Telegram Bot FAQ). For a list larger than that, Telegram’s own advice is to spread the send “over longer intervals (e.g. 8-12 hours)” rather than firing it all at once — a recommended pacing, not a guarantee against every 429 error, so treat it as a starting point and watch for throttling on your first large send.
Set up in 1CS
Two things need to be true before a Telegram order update can land: the inbox has to be live, and the system has to catch the moment a customer becomes reachable. First, open AI > AI Agent (AI เจ้าหน้าที่), go to the Overview (ภาพรวม) tab, and confirm the Telegram inbox is switched on under Active channels (ช่องทางที่ใช้งาน). Second, go to AI > Automation (เงื่อนไขอัตโนมัติ) and add a rule from the ready-made Welcome message (ข้อความต้อนรับ) template, which fires on the conversation created (การสนทนาที่ถูกสร้าง) event — the instant a customer’s first message makes the chat exist. Edit the template text to confirm the order and tell the customer their Telegram is now connected for shipping updates; that single exchange is also what proves the chat is now reachable for that customer. The full click-by-click steps are in Thai: สร้างกฎอัตโนมัติ (Automation rule) แรก. 1CS’s channel setup for Telegram alongside LINE, Facebook, Instagram, WhatsApp, email, SMS and live chat sits inside Omnichannel inbox.
A line to add before the order ships
Put this where a customer already sees it — an order confirmation page, a LINE or Facebook reply, or a packing note — so they open the Telegram chat before you need to send anything through it:
📦 Want shipping updates on Telegram? Message [bot username] on Telegram and send any message (even just “hi”) — that’s all it takes. We can’t send the first message, so this step is on you, just once.
Sellers juggling the same shipping-update problem on other channels have the same root cause in reverse on WhatsApp, where a messaging limit grows with real sending instead of blocking the first message outright — worth comparing before picking which channel carries your order updates by default.
