How to connect Telegram to X10CRM: bot, Business and company account
Choose a connection, add your channel, set team access and test the first conversation.
Use this guide to connect Telegram and check that your reps can receive messages and reply from the CRM. Still choosing a connection? Read the comparison of bots, Business and company accounts.
#Before you start
- You need access to integration settings and a list of teammates who should use the channel.
- For a bot: a BotFather token and a CRM address available over HTTPS.
- For Business: a connected bot with Business Mode enabled and access to the Telegram account settings.
- For a direct account: the phone with Telegram and its two-step verification password, if enabled. The implementation team must configure the server module first.
- For E-chat, follow the separate E-chat setup guide.
Open the Telegram settings under Integrations → Social channels → Telegram. The page in your CRM is /settings/social/telegram/. If you cannot access it, ask your administrator to check permissions and your CRM version.
#Option 1. Connect a Telegram bot
- Open the official BotFather, send
/newbot, create your bot and copy its token. - Choose the option to add a bot in the CRM Telegram settings. Enter a name and token, then save.
- Connect the bot. X10CRM registers the address that receives incoming messages.
- From a test account, open the bot, select Start or send
/start, then send a normal message. - Find the conversation in the social inbox and reply. Check that the reply reaches the test account.
#Option 2. Connect Telegram Business
- Connect a bot to X10CRM using the steps above.
- In BotFather, select the bot and enable Bot Settings → Business Mode.
- In the Telegram account settings, find the business chatbot connection, enter the bot’s @username and grant access to the chats it should handle. Menu names can vary between app versions.
- Check that a Business channel appears in X10CRM. Its initial access is inherited from the bot, so review the permitted teammates.
- Send a new message from a test account to an allowed chat, then test a reply from X10CRM.
Old Business conversations are not imported. New messages arrive after connection; reply permissions and Telegram’s rules still apply. Telegram’s documentation states that connected bots are also available without Premium. Check other business features separately.
#Option 3. Sign in to a company account with a QR code
The implementation team first configures Telegram on the CRM server. You then sign in as you would on another device. Use a company account you will retain access to.
- Add your company phone number in the CRM Telegram settings and save the channel.
- Choose QR-code sign-in. On your phone, open Telegram → Settings → Devices, choose to link a device and scan the code shown in X10CRM.
- If two-step verification is enabled, enter the password in the field that appears in the CRM.
- If the QR code expires, request a new one. You can also switch to verification-code sign-in: the CRM shows where Telegram sent the code. It is not necessarily an SMS.
- Check that the channel is connected, then test a message from another account and a reply from the CRM.
#Set team access and conversation ownership
- Review who can access the channel. Test with a rep’s account, not just an administrator account.
- Configure an owner or automatic assignment for new conversations.
- If needed, enable an automatic reply or AI assistant. Test the content and handover to a person.
- Verify that the test conversation is linked to the correct lead record.
#Groups, reactions and deleted messages
Group chats are disabled by default for bots and direct accounts. Enable them in the channel settings if needed. Each group appears as a separate conversation. A bot needs suitable Group Privacy settings in BotFather or group administrator rights to see all messages.
- AI and automatic replies do not answer in groups.
- Reaction support depends on the connection mode; Business reactions are not supported in the current implementation.
- Where deletion events are available, X10CRM keeps the message marked as deleted in Telegram. Regular bots do not receive these events.
- Full recovery of missed history is not guaranteed. In particular, direct-account supergroups are not backfilled after a gateway restart.
#Check before your team starts using the channel
- An incoming test message appears in the correct CRM channel.
- The rep’s reply arrives from the intended bot or account.
- A test file can be received and opened.
- A permitted rep can access the channel; an unpermitted teammate cannot.
- The conversation is linked to the correct lead and assignment works as intended.
- AI or automatic replies, if enabled, have been tested separately in a private chat.
#Troubleshooting
| Problem | What to check |
|---|---|
| No messages from the bot | Has the customer started it? Is the bot connected and the CRM available over HTTPS? Ask the administrator to check the webhook. |
| Telegram service is not running | Ask the implementation team to check telegram_gateway. Entering the code again will not fix the server module. |
| A password is requested after QR sign-in | Enter the account’s two-step verification password, not a one-time login code. |
| No verification code | Read the delivery hint in X10CRM and check the Telegram app. Use another method if the interface offers one. |
| Business cannot reply | Check bot permissions, allowed chats and a recent customer message. An old chat does not necessarily allow a reply now. |
| A rep cannot see the channel | Check channel access and CRM account permissions. |
| Telegram rejects an outgoing message | Read the error under the message. Repeated sending does not remove account or recipient restrictions. |
If you need support, share the channel name, test time and error text. Do not include tokens, passwords or login codes in ordinary messages or screenshots.
