Telegram is one of the main customer channels in Ukraine. The adapter turns incoming bot messages into CRM leads, so requests don't get lost in chats.
Through a bot, not your personal account
The integration works with a Telegram bot — you create one and hand customers its link. Messages sent to your personal account (@username) do not reach the CRM: the Telegram Bot API has no access to a person's private chats, which is a platform limitation rather than a CRM one. Practical consequence: make the bot the main contact button on your site and in your profile, and every enquiry becomes a lead immediately. If someone does write to the personal account, that lead has to be created by hand.
What becomes a lead
Text message
The Telegram profile name plus the message text in the lead's notes.
Shared contact
The highest-quality signal: name and phone straight into the card.
Automatic reply to the customer
After the lead is created the bot sends a confirmation itself: "Thank you, your request has been received." The customer sees a response, the manager sees a new card.
What lands in the CRM
- Lead name (from the contact or profile)
- Phone — if the customer shared a contact
- The message text in notes
- Source: telegram
- Duplicate protection via the message external ID
Connect in 3 steps
- 1
Create a bot
In @BotFather run /newbot and copy the token.
- 2
Add the adapter and test
Paste the token; the test calls getMe and shows the bot's @username.
- 3
Set the webhook
Call setWebhook with the URL and secret token — a test message already creates a lead.
Frequently asked questions
Is this two-way messaging?
Yes — reply to the customer straight from the unified CRM Inbox or the lead page; the full conversation history is kept in the thread.
Is the webhook secured?
Yes — a secret token is verified in the X-Telegram-Bot-Api-Secret-Token header.
Stop losing Telegram requests
Connect a bot and every message becomes a lead.
Start for free