Send order, invoice, payment, and delivery notifications from Business Central via the WhatsApp Business API and multi-gateway SMS — a per-tenant AL extension built, installed, and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
示意预览Send order, invoice, payment, and delivery notifications from Business Central via the WhatsApp Business API and
multi-gateway SMS — a per-tenant AL extension built, installed, and supported by ECOSIRE.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Dynamics 365 Business Central 上构建、配置并安装。
约 2–4 周内上线,并提供上线后的支持期。
WhatsApp & SMS Notifications for Business Central is a build-to-order AL extension that turns Business Central document events into outbound WhatsApp and SMS messages — no manual emailing, no copy-pasting order numbers into a phone.
This is not an instant AppSource download. ECOSIRE designs, builds, installs, and supports the extension on your Business Central environment (SaaS online or on-prem) as a per-tenant extension, configured to your gateways, templates, and document flows.
Under the hood, the extension uses event subscribers on standard codeunits (e.g. posting routines for sales orders, posted sales invoices, payment registration, and warehouse shipments) so notifications fire automatically the moment a document is released, posted, or shipped. Outbound calls are made through the WhatsApp Business Cloud API and your chosen SMS gateway over HttpClient, queued and retried via the BC Job Queue so a transient gateway outage never blocks posting.
We add table and page extensions for per-customer opt-in, phone/WhatsApp number validation, and a notification log; permission sets so only authorized roles can edit templates or resend; and event-triggered, parameterized message templates that merge BC field data (customer name, document no., amount, due date, tracking link).
Optional capabilities include delivery-status webhooks (sent/delivered/read writeback), inbound reply capture routed to a BC queue, and Dataverse / Power Platform surfacing for Power Automate flows. Everything is documented, version-controlled, and handed over with a runbook. You own the tenant; we own getting it working and keeping it working.
Wants customers notified automatically the instant an order is confirmed, invoiced, or shipped — without staff manually emailing or calling — to cut WISMO inquiries and speed up confirmations.
Needs invoice and payment-receipt notifications and due-date reminders pushed over WhatsApp/SMS to improve collection speed and give customers a clear, auditable payment trail.
Cares that it ships as a clean per-tenant extension with proper permission sets, Isolated Storage for credentials, Job Queue retries, and a log — not brittle customizations that break on the next BC update.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Dynamics 365 Business Central 原生 |
|---|---|---|---|---|
| Sends WhatsApp + SMS on order/invoice/payment/delivery events out of the box | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Built, installed, and supported on your tenant by the vendor | 包含 | 不包括在内 | 不包括在内 | 不包括在内 |
| Tailored to your exact document events, templates, and gateways | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Delivery-status tracking and inbound reply capture into BC | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Job Queue retry so gateway outages never block posting | 包含 | 部分支持 | 部分支持 | 不包括在内 |
| Source code and .app handed over to you | 包含 | 包含 | 不包括在内 | 不包括在内 |
| Fixed one-time price with no per-seat license | 包含 | 不包括在内 | 不包括在内 | 包含 |
| Maintained against monthly BC release cycles | 包含 | 部分支持 | 包含 | 包含 |
Typical lead time is 2 to 4 weeks from a confirmed scope, depending on how many events and gateways you need and whether WhatsApp Business templates require Meta approval (that approval is on Meta's side and can add a few days). We start with a short scoping call to map your document events and channels, build the AL extension, validate against a sandbox/test tenant, then install on production and walk your team through configuration. You get a date estimate in writing before we begin.
Every build includes a post-launch support window for bug fixes and minor adjustments. Because this is a per-tenant extension we maintain, we test it against Business Central's monthly and major release cycles and can update it when Microsoft changes underlying objects or events. Beyond the included window, we offer ongoing support and enhancement retainers. You receive the source code and the .app artifact either way, so you are never locked out of your own extension.
No. This is a build-to-order, per-tenant extension. ECOSIRE builds it to your specific events, templates, and gateways, then installs it on your Business Central environment (online or on-prem) and supports it. There is no public AppSource download — that is deliberate, because notification logic, opt-in rules, and gateway choices differ per business.
WhatsApp is handled through the official WhatsApp Business Cloud API (Meta), which requires a WhatsApp Business account and pre-approved message templates for proactive notifications. SMS is built against a gateway abstraction so we can wire in providers like Twilio or Vonage, or a regional gateway you already use, and configure fallback rules. We confirm exact providers during scoping and store credentials in Isolated Storage.
No. Notifications are dispatched asynchronously through the Business Central Job Queue with retry and backoff, so the outbound call never sits inside the posting transaction. If WhatsApp or your SMS gateway is temporarily unavailable, the document still posts and the message is retried; failures are recorded in the notification log with the error so an admin can resend.
Send order, invoice, payment, and delivery notifications from Business Central via the WhatsApp Business API and multi-gateway SMS — a per-tenant AL extension built, installed, and supported by ECOSIRE.