Illustrative previewA per-tenant Business Central / Dynamics 365 extension that bridges Telegram,
Viber, Slack, Discord, and Teams into one unified inbox — send and receive messages from CRM records, auto-create contacts and deals from chats, and sync full chat history to the record timeline. Built, installed, and supported by
ECOSIRE on your tenant.
What is Telegram & Multi-Messenger Hub for Dynamics 365?
A per-tenant Business Central / Dynamics 365 extension that bridges Telegram, Viber, Slack, Discord, and Teams into one unified inbox — send and receive messages from CRM records, auto-create contacts and deals from chats, and sync full chat history to the record timeline. Built, installed, and supported by ECOSIRE on your tenant. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
About this Product
Bring the messengers your market actually uses inside Dynamics 365
In many regions, deals close on Telegram and Viber, not email. Yet Dynamics 365 Business Central and Dataverse have no native connector for them — conversations live on personal phones, never touch the CRM timeline, and contacts are recreated by hand. The Telegram & Multi-Messenger Hub closes that gap with a custom AL extension that wires Telegram, Viber, Slack, Discord, and Teams directly into your D365 environment.
This is not an instant AppSource download. ECOSIRE builds the extension to fit your tenant, deploys it as a per-tenant extension (or a Dataverse/Power Platform solution for D365 CE), and supports it afterward. We map your channels, permission sets, and record flows to your real sales process before go-live.
What it does
A unified inbox page in Business Central aggregates threads across all five platforms. Agents reply from the message itself or from a Contact / Customer / Opportunity card — outbound messages route through the right gateway (Telegram Bot API, Viber, Slack, Discord webhooks, and the Bot Framework Direct Line custom-channel bridge for Teams). Inbound messages are matched to existing records by phone or handle, and unmatched chats can auto-create a contact and a deal in one click.
Every message is written to the record timeline / interaction log via AL table extensions and event subscribers, so history survives staff turnover and is queryable through the BC REST/OData API. A Job Queue entry handles polling, retries, and delivery-receipt reconciliation. Access is governed by a dedicated permission set, and all credentials are stored in isolated storage — never in code.
Built honestly, installed on your tenant, and maintained under a support agreement.
What you get
- A per-tenant Business Central extension (.app) — or a Dataverse/Power Platform managed solution for D365 CE — built in AL and deployed to your environment
- Channel onboarding: Telegram bot, Viber, Slack, Discord, and Teams Direct Line endpoints configured and connected to your tenant
- Custom permission set, isolated-storage credential setup, and Job Queue configuration applied to your environment
- Source code handover (AL project) and a signed deployment package, version-controlled in your or our repository
- Admin and end-user documentation plus a live walkthrough session for your team
- Sandbox validation pass followed by supervised production go-live
- Post-launch support and update agreement (bug fixes, BC version-compatibility maintenance, channel API changes)
Who this is for
Regional Sales Manager
Runs a team that closes deals over Telegram and Viber but reports in Dynamics 365. Needs every conversation logged to the opportunity timeline so pipeline and forecasts reflect what really happened, not just emails.
Customer Support Lead
Handles inbound queries across Slack, Discord, and Teams. Wants one inbox inside Business Central where agents reply in context, with full history attached to the customer record and governed by permission sets.
D365 / IT Administrator
Owns the Business Central tenant and is wary of unmanaged middleware. Wants a clean per-tenant extension with isolated-storage secrets, a defined permission set, Job Queue scheduling, and Application Insights telemetry — installed and supported, not bolted on.
How Telegram & Multi-Messenger Hub for Dynamics 365 Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Dynamics 365 Business Central Native |
|---|---|---|---|---|
| Unified inbox for Telegram, Viber, Slack, Discord & Teams inside D365 | Included | Partial support | Partial support | Not included |
| Auto-create contacts and deals from inbound chats | Included | Partial support | Partial support | Not included |
| Chat history synced to record timeline / interaction log | Included | Partial support | Partial support | Not included |
| Teams interop via Bot Framework Direct Line bridge | Included | Partial support | Not included | Partial support |
| Installed as governed per-tenant extension with dedicated permission set | Included | Partial support | Included | Included |
| Built to your channels, routing rules & sales process | Included | Included | Not included | Not included |
| Ongoing support, BC version & channel-API maintenance | Included | Not included | Partial support | Included |
| Secrets in isolated storage with signed webhook verification | Included | Partial support | Partial support | Included |
Frequently Asked Questions about Telegram & Multi-Messenger Hub
Is this a download from Microsoft AppSource?
No. This is a build-to-order extension. ECOSIRE develops it in AL to match your tenant's channels and sales process, deploys it as a per-tenant extension (or a Dataverse/Power Platform solution for D365 CE), and validates it in a sandbox before go-live. There is no instant marketplace install.
How long does delivery take?
Typical lead time is one working week from kickoff, depending on how many of the five channels you need live at launch and whether you require Dataverse packaging. We confirm a fixed timeline after a short scoping call that covers your channels, permission model, and record-matching rules.
What ongoing support and updates are included?
The build includes a post-launch support and update agreement covering bug fixes, compatibility maintenance across Business Central monthly/major releases, and adaptation to changes in the Telegram, Viber, Slack, Discord, or Teams APIs. Support tiers and response times are agreed before go-live; we hold the source so we can patch quickly.
Which messengers and CRM records are supported?
Telegram, Viber, Slack, Discord, and Microsoft Teams (via the Bot Framework Direct Line bridge). Out of the box, messaging is wired to Contact, Customer, and Opportunity records, with the timeline / interaction log capturing history. Additional record types can be added during scoping.
Where are credentials and chat data stored, and is it secure?
Bot tokens and webhook secrets are kept in Business Central isolated storage — never in source code. All access is gated by a dedicated permission set, inbound webhooks use signed-payload verification, and conversation data stays inside your tenant, queryable through the BC REST/OData API. Errors and telemetry flow to Application Insights for visibility.
Related Modules
Tap Payments Connector (GCC)
A build-to-order Business Central extension that adds Tap-hosted pay links to your sales invoices, supports KNET, mada and card schemes across the GCC, and auto-reconciles captured payments back to the originating customer ledger entries. Built, installed per-tenant and supported by ECOSIRE.
Tap Payments Gateway for Business Central
A build-to-order AL extension that wires Business Central to Tap Payments for GCC card, Mada, KNET, Benefit and Apple Pay acceptance, pay-by-link, tokenized card-on-file, in-BC refunds, and automated payout and fee reconciliation against your AR.
Telr Payment Gateway for Business Central
A build-to-order AL extension that connects Microsoft Dynamics 365 Business Central to the Telr gateway for UAE/KSA card, Mada and local-wallet acceptance, hosted pay-links, tokenized recurring billing, 3DS2/SCA and automatic payment reconciliation. Built, installed per-tenant and supported by ECOSIRE.
Thailand e-Tax Invoice & Receipt
An ECOSIRE-built AL extension that turns posted Business Central sales invoices, credit memos, and receipts into digitally signed Thai e-Tax Invoice & Receipt documents, delivers them to the buyer and your accredited channel, and keeps a compliant archive. Built to order for your Business Central version and your Thai tax setup.
Telegram & Multi-Messenger Hub
A per-tenant Business Central / Dynamics 365 extension that bridges Telegram, Viber, Slack, Discord, and Teams into one unified inbox — send and receive messages from CRM records, auto-create contacts and deals from chats, and sync full chat history to the record timeline. Built, installed, and supported by ECOSIRE on your tenant.
- Unified multi-channel inbox page surfacing Telegram, Viber, Slack, Discord, and Teams threads inside Business Central
- Send and receive messages directly from Contact, Customer, and Opportunity cards via AL page extensions
- Inbound message-to-record matching by phone number or platform handle, with one-click auto-create of contacts and deals from unmatched chats
- Full chat history synced to the record timeline / interaction log through table extensions and event subscribers