A Telegram button solves only the first part of website communication: it gives the visitor somewhere to click. If it opens a manager’s personal profile, customer messages still depend on one person. The complete support route is different:
Website → business Telegram bot → GramDesk → private team topic
Customer ← business Telegram bot ← GramDesk ← teammate's reply
The Telegram button generator creates the entry point. The website support use case explains who this model fits. This guide covers the actual setup and verification.
What you need
Prepare a Telegram account that will own the business bot, access to edit the website, a private group for the people who answer customers and about 15–20 minutes for setup and testing. Do not make an employee’s personal username the main destination when several people may need to answer.
Step 1
Visitor clicks the website support button
Step 2
Customer writes to the business bot
Step 3
GramDesk creates a private customer topic
Step 4
The team replies and the customer receives it
Step 1: Create the customer-facing bot
Open @BotFather in Telegram, send /newbot and choose a recognizable display name and a username ending in bot, for example ExampleStoreSupportBot. BotFather returns an authentication token. Store it securely: anyone with the token can control the bot.
Do not publish the token in website code, public chats or screenshots. If it is exposed, open @BotFather, use /token or the bot-management interface to generate a replacement, then update the GramDesk connection. Telegram’s official bot guide documents bot creation and token replacement.
Step 2: Create a private team group
Create a new private Telegram group and add only the people who need customer context. Give it a clear internal name such as Example Store — Customer Support. Customers will not join this group or see its members.
Use a dedicated support group instead of the company’s general chat. Otherwise customer conversations, operational messages and informal discussion will compete for attention.
Step 3: Enable Topics and the required permission
Open Group Settings → Topics and enable Topics. Add the bot as an administrator with permission to manage Topics. Telegram documents the current settings path in its Topics update, while the forum API documentation confirms that topic management requires the appropriate administrator right.
If the option is missing, update Telegram and confirm that you are the group owner. Telegram’s underlying forum mode uses a supergroup; an older basic group may need to be upgraded first. Only an administrator with owner rights can switch forum mode on or off. Current Telegram clients normally handle the conversion through the interface.
Topics matter because every customer needs a separate conversation. Without them, the private group becomes another long mixed chat.
Step 4: Connect the bot and group to GramDesk
Open @GramDeskBot, start the connection flow and provide the bot token when requested. Link the private support group and complete the permission checks. The exact interface is covered in the Telegram support bot setup guide.
After connection, a private message to the business bot should create or reopen that customer’s topic, and a reply from the topic should return to the customer’s bot chat.

Step 5: Add the website button
The destination uses the public bot username:
https://t.me/YourBotUsername
Create ready-to-paste code with the free Telegram button generator, or follow the focused HTML installation guide. Put the button where questions arise: product and service pages, pricing, delivery, returns, booking, contacts and the footer.
Use a label that explains the action: Ask a question in Telegram, Contact support or Check an order. A label that only says Telegram does not tell the visitor whether it opens a channel, profile or support bot.
Step 6: Test the complete route
Test as a real customer, not only as the bot owner:
- Open the published website on another account or device.
- Click the button and start the bot.
- Send a customer question.
- Confirm that a new topic appears in the private group.
- Reply inside that topic.
- Confirm that the reply reaches the customer’s bot chat.
- Send a second message and verify that it returns to the same topic.
- Repeat the button test on mobile.
The setup is complete only when both directions work.
Common setup problems
I cannot find the Topics option
Use the latest Telegram app and verify that you are the group owner. An older basic group may require conversion to a supergroup before forum Topics can be enabled.
The bot cannot create customer topics
Adding the bot to the group is not enough. Make it an administrator and grant the permission to manage Topics.
The customer message arrives, but no reply returns
Reply inside the customer’s topic and verify that the bot-to-group connection is active. Then repeat the full test from an external account.
The button appears on only one page
Place the generated script in the site’s global footer or site-wide custom-code area rather than a single page block.
Know the boundary of this setup
This workflow fits a small team that needs shared visibility without another dashboard. A full helpdesk is a better choice when you need staffed 24/7 chat, strict SLA routing, extensive analytics, complex automation or enterprise ticket management. The goal here is not to imitate every helpdesk feature; it is to give website visitors one clear contact and the team one organized Telegram workspace.