STRAX Reach · Messaging apps
Telegram bot conversations in Reach
Clients start a chat with your company bot on Telegram and every message reaches the same console and history as your other channels.
- Bot messages and documents
- Webhook or polling
- t.me deep links
Two ways to listen, one history
Reach can receive Telegram messages through a signed webhook or by polling Telegram on a schedule. Polling needs no inbound exposure at all, which suits installs that sit behind a firewall; the webhook answers faster once you have a public address.
Outbound text and PDF documents go through the Bot API. A deep link with a start code lets a client connect the chat to their account in one tap, after which Reach treats them as a linked client.
Telegram users often never share a phone number, so the start code does the matching. Your portal issues a short code, the client opens the deep link, and from then on every message from that Telegram id belongs to their record until you revoke it.
Where it helps
Account alerts
Push low-balance and large-transaction alerts to clients who prefer Telegram, with replies landing in their conversation.
Monthly statements
Linked clients ask the bot for last month's statement and receive the PDF your reporting produces.
Support queue
Questions the bot cannot answer go to an agent in the Reach console, who replies without leaving it.
Login confirmations
Ask a client to confirm a new sign-in from the bot, so a surprise login is reported in the same place as the alert.
What you need
-
A Telegram bot
Created with BotFather, which gives you the bot token and username.
-
The bot token
Stored in the STRAX credential vault and used only by the Reach workflows.
-
A polling schedule or a public address
Either enable the polling job, or give the webhook a public HTTPS address and a secret.
-
Reach Core
The client records and console this channel files into.
Good to know
Telegram allows either a webhook or polling for a bot, never both at once. Pick one lane per bot; switching means removing the webhook before polling starts.
Questions
Which lane should we choose?
Start with polling if the install has no public address. Move to the webhook when you want replies to land within a second or two.
Can the bot send documents?
Yes, linked clients can receive PDFs such as statements, generated by your STRAX reports.
Does it work in group chats?
Reach answers private chats with the bot. Group conversations are ignored so client data never lands in a shared room.
What happens if someone forwards the start link?
Each code works once and expires within a day, and a linked chat can be blocked from the Reach console if a client reports misuse.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Telegram to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 2 |
| Global variable | 1 |
| Scheduled job | 1 |
| Workflow | 5 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Telegram channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - Telegram"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
Telegram is a trademark of its owner, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.


