SMS & Notifications for Business Central

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.

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.

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.

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.

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.

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.