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. One-time license from $249.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

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.
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
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
Bot Framework Direct Line custom-channel bridge for Microsoft Teams interoperability
Telegram Bot API, Viber, Slack, and Discord webhook integration with signed-payload verification
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.
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.
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.
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.
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.
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Telegram & Multi-Messenger Hub for Dynamics 365 modülünün ZIP dosyasını indirin.
ZIP'i sunucudaki Odoo özel eklentiler klasörünüze çıkarın (veya Uygulamalar > Odoo.sh / runbot'taki dosyadan yükle yoluyla yükleyin).
Geliştirici Modunu etkinleştirin, Uygulamalar'ı açın, Uygulama Listesini Güncelle'ye tıklayın, Telegram & Multi-Messenger Hub for Dynamics 365'i arayın ve Yükle'ye basın.
Yeni menüyü açın, ECOSIRE lisans anahtarınızı yapıştırın, tüm harici kimlik bilgilerini (Shopify, Amazon, Stripe vb.) bağlayın ve kaydedin.
Yerleşik bağlantı testini çalıştırın, ilk 10 kaydınızı senkronize edin ve yinelenen cronu planlayın. Herhangi bir sorun olursa desteğe başvurun.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Unified inbox for Telegram, Viber, Slack, Discord & Teams inside D365 | ||||
| Auto-create contacts and deals from inbound chats | ||||
| Chat history synced to record timeline / interaction log | ||||
| Teams interop via Bot Framework Direct Line bridge | ||||
| Installed as governed per-tenant extension with dedicated permission set | ||||
| Built to your channels, routing rules & sales process | ||||
| Ongoing support, BC version & channel-API maintenance | ||||
| Secrets in isolated storage with signed webhook verification |
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.
Typical lead time is 3 to 5 weeks 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.
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.
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.
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.
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.