SMS & Notifications for Business Central

主な機能

Event-driven SMS via AL event subscribers bound to standard BC publishers (OnAfterPostSalesDoc, OnAfterPostPurchaseDoc, shipment registration, workflow approval events)

Notification Template table with Business Central field-merge tokens (e.g. %CustomerName%, %DocumentNo%, %DueDate%, %AmountDue%) resolved at send time

Multi-gateway provider configuration table — route through Twilio, Vonage, MessageBird or a regional aggregator over their REST API via HttpClient

Bulk reminder runs for overdue invoices executed as a scheduled Job Queue Entry over filtered ledger entries

Delivery receipts (gateway status callbacks) logged to a per-message SMS ledger and reconciled per recipient

Table and page extensions exposing SMS settings and message history on Customer, Sales, Service and Posted Document pages

Dedicated permission sets separating SMS configuration, send-now, and read-only log access

Per-tenant signed extension install via Extension Management — no source published to public AppSource

Opt-out / consent flag on the Customer record so suppressed numbers are skipped at send time

Retry and error handling for transient gateway failures, with failed sends visible in the message ledger

Telemetry written to the BC partner telemetry / Application Insights stream for send-rate and failure monitoring

Manual 'Send SMS' action on document and customer pages for ad-hoc one-off messages using the same templates

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Dynamics 365 Business Central 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

SMS & Notifications for Business Central turns key ERP events into instant customer text messages — without exporting data to a separate marketing tool. When a sales order is posted, an invoice falls overdue, or a warehouse shipment is registered, the extension's COD event subscribers fire and send a templated SMS through your chosen gateway.

This is a build-to-order extension, not an instant AppSource download. ECOSIRE builds it in AL against your Business Central version (Online SaaS or on-premises), packages it as a signed per-tenant extension, installs it through the Extension Management page (or your AppSource private-app flow), and supports it on your environment. No data leaves your tenant except the message payload sent to the SMS gateway you configure.

Technically, the app ships table and page extensions to surface SMS settings and a message log on Customer, Sales/Service, and Posted Document pages; event subscribers bound to standard publishers (OnAfterPostSalesDoc, workflow events, job queue triggers); a Notification Template table with Business Central field-merge tokens resolved at send time; and a provider configuration table so you can route through Twilio, Vonage, MessageBird, or a regional aggregator via their REST API using HttpClient. Bulk reminder runs (e.g. all overdue invoices) execute as a Job Queue Entry on a schedule you set. Delivery receipts returned by the gateway are written back and reconciled to a per-message ledger for full auditability.

Dedicated permission sets keep configuration and send rights separate from operational users. Because every customer's posting routines, document flows, and approval workflows differ, ECOSIRE scopes the exact triggers, templates, and gateway with you before development — so what you receive matches your processes, not a generic template.

得られるもの

Signed per-tenant AL extension (.app) built against your Business Central version and installed on your environment by ECOSIRE

Configured SMS gateway connection (Twilio / Vonage / MessageBird or your chosen regional aggregator) with credentials held in your tenant

Set of notification templates wired to your specific posting and workflow triggers, agreed during scoping

Permission sets and Job Queue Entry configured for bulk reminder runs on your schedule

Source code handover (AL project) plus a short admin runbook covering template edits, gateway keys and the message ledger

Post-deployment support window with bug fixes and assistance configuring additional triggers or templates

これは誰のためのものですか

Finance / AR Manager

Wants automated payment reminders that fire from overdue customer ledger entries via a scheduled Job Queue run, cutting manual chasing and improving days-sales-outstanding without a separate dunning tool.

Operations / Fulfilment Lead

Needs order-confirmation and delivery-alert texts triggered the moment a sales document is posted or a shipment is registered, reducing 'where is my order' calls to the support desk.

Business Central Administrator

Responsible for the tenant and wants a clean per-tenant extension with proper permission sets, telemetry and an auditable message ledger — not ad-hoc scripts or data exported to an unmanaged third-party app.

SMS & Notifications for Business Central の比較方法

基準	エコシエール	カスタムビルド	競合他社
Triggers SMS directly from BC posting & workflow events (no export)	付属	付属	部分的なサポート
Installed as a managed per-tenant extension with permission sets	付属	部分的なサポート	付属
Templates with native BC field-merge tokens	付属	付属	部分的なサポート
Multi-gateway provider choice (Twilio / Vonage / regional aggregator)	付属	部分的なサポート	部分的なサポート
Delivery receipts reconciled to an auditable message ledger	付属	部分的なサポート	部分的なサポート
Scoped to your exact processes (not a generic template)	付属	付属	含まれていない
Built, installed and supported for you (no in-house AL skills needed)	付属	含まれていない	部分的なサポート
AL source code handed over for future maintenance	付属	付属	含まれていない
Available instantly with one-click install	含まれていない	含まれていない	付属

SMS & Notifications for Business Central に関するよくある質問

How long does delivery take, since this isn't an instant AppSource download?

This is a build-to-order extension, so there's a short lead time rather than a one-click install. After a scoping call to confirm your triggers, templates and gateway, a typical build, install and test cycle runs about 2–4 weeks depending on how many event triggers and document flows are involved. ECOSIRE develops in AL against your exact Business Central version, packages a signed per-tenant extension, and installs it on your environment — we share the timeline in writing before work begins.

What happens with ongoing support and updates after install?

Every build includes a post-deployment support window covering bug fixes and help configuring additional triggers or templates. Because the extension is per-tenant AL, when Microsoft ships a new Business Central major version we can recompile and re-test it against the new runtime as part of an ongoing support arrangement. You also receive the AL source and an admin runbook, so your own BC partner can maintain it if you prefer.

Which SMS gateways can it use?

The provider configuration table is built to call a gateway's REST API over HttpClient, so common choices are Twilio, Vonage (Nexmo) or MessageBird, plus regional aggregators where you need local sender IDs or better rates. We confirm your preferred gateway during scoping and configure the credentials inside your tenant — the keys never leave your environment except in the message payload sent to that provider.

Does customer data leave my Business Central tenant?

No customer data is exported to any ECOSIRE system. The extension runs entirely inside your tenant; the only data that leaves is the individual SMS payload (recipient number and message body) sent to the gateway you configure at send time, exactly as required to deliver the text. Delivery receipts come back into the BC message ledger.

Can it send bulk reminders, or only one message per event?

Both. Event-driven sends fire one message per posting or workflow event. For bulk dunning, the extension includes a Job Queue Entry that runs on your schedule, filters overdue customer ledger entries, and sends a templated reminder to each — with every send and its delivery status recorded in the message ledger so you have a full audit trail.

Does this work on Business Central Online (SaaS) and on-premises?

Yes. The extension is written in AL and can target Business Central Online (SaaS) as a per-tenant extension or an on-premises deployment. Gateway calls use HttpClient, which is supported in both; we confirm your deployment type during scoping so the build and install path match your environment.