什么是 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 $249.00 USD; request a quote for a scoped proposal.
产品详细信息以英文显示。翻译即将推出。
示意预览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
Bot Framework Direct Line custom-channel bridge for Microsoft Teams interoperability
Telegram Bot API, Viber, Slack, and Discord webhook integration with signed-payload verification
Job Queue entry for background polling, outbound retries, and delivery-receipt reconciliation
Dedicated permission set and isolated-storage credential vault — no secrets in source
Conversation data exposed through the Business Central REST/OData v4 API for reporting and Power BI
Optional Dataverse / Power Platform solution packaging for Dynamics 365 Customer Engagement tenants
Per-channel routing rules mapping incoming threads to the correct team, queue, or salesperson
Attachment and media handling (images, documents, voice notes) linked to the originating record
Configurable canned-reply and message-template support stored as BC setup records
Telemetry and error logging surfaced to Application Insights for support visibility
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
- 3
上线 + 支持
约 2–4 周内上线，并提供上线后的支持期。
关于此产品
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.
你得到什么
- 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)
这是给谁的
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.
Telegram & Multi-Messenger Hub for Dynamics 365 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| 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 | 包含 | 部分支持 | 部分支持 | 包含 |
关于Telegram & Multi-Messenger Hub for Dynamics 365的常见问题
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 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.
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.
相关模块
申请报价
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.
- 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