SMS for Dynamics 365 CRM (Twilio/Multi-Gateway)

Características clave

Chat-style SMS FactBox and page extensions on Customer, Contact, Sales Order, and Service records so threads live where the data lives

Two-way messaging: outbound sends plus inbound replies and delivery receipts captured via a Business Central API page (OData/REST webhook endpoint)

Event-triggered automated texts using AL event subscribers and business events (order confirmation, shipment, appointment reminder, payment due, service update)

Bulk and segmented SMS campaigns driven by the BC job queue with throttling, retry-on-transient-error, and per-recipient delivery logging

Multi-gateway abstraction layer: switch between Twilio, Vonage, or MessageBird via configuration, no code rewrite

Multi-language message templates with placeholder merge fields resolved from BC record data

Emoji and MMS/media support where the selected gateway permits

Per-message and per-campaign delivery status tracking (queued, sent, delivered, failed) with audit log

Dedicated permission sets for agents, marketers, and admins so SMS access follows BC role-based security

Configurable opt-out/STOP keyword handling and consent flags on Contact records for compliance

Gateway credentials stored using Business Central isolated storage / secrets, never hard-coded

Optional Dataverse / Power Platform integration so the SMS log surfaces in model-driven apps and Power Automate flows

Hecho a medida, listo para ti

Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.

Haces el pedido

Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.

Creamos e instalamos

ECOSIRE la crea, la configura y la instala en tu Dynamics 365 Business Central.

En marcha + soporte

Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.

Sobre este producto

SMS for Dynamics 365 CRM brings native two-way text messaging into your Business Central environment without bolting on a disconnected third-party portal. ECOSIRE designs, builds, and installs this as a per-tenant AL extension directly on your BC tenant (cloud SaaS or on-prem), so your conversations live next to the Customer, Contact, Sales Order, and Service records they belong to.

The extension adds a chat-style SMS FactBox and page extensions to the records you already work in. Messages are sent and received through the gateway you choose — Twilio, Vonage, or MessageBird — via their REST APIs, with delivery-status webhooks handled by a Business Central API page (a published OData/REST endpoint) so inbound replies and delivery receipts flow back into BC automatically. Event subscribers (OnAfterInsertEvent, document-release publishers, and custom business events) fire automated texts on triggers you define: order confirmations, shipment notifications, appointment reminders, payment-due nudges, and service ticket updates.

Bulk and segmented campaigns run through the job queue, so large sends are throttled, retried on transient gateway errors, and logged per recipient. Multi-language templates, emoji, and MMS/media are supported where the gateway allows.

This is honest build-to-order software: it is not an instant AppSource download. After purchase, ECOSIRE scopes your gateway and trigger requirements, develops the extension, installs it on your tenant, configures permission sets, and hands over a tested, documented solution. We then support and update it as Business Central releases roll out. Optional Dataverse / Power Platform integration lets the same SMS log surface in model-driven apps and Power Automate flows. You own the result; we keep it running.

lo que obtienes

A per-tenant Business Central AL extension (.app) built to your scoped requirements and installed on your cloud or on-prem environment

Table and page extensions adding the SMS thread, message log, and template/configuration pages

A published BC API page (OData/REST endpoint) wired to your gateway's inbound and delivery-status webhooks

Configured permission sets for agent, marketer, and administrator roles

Job queue entries configured for bulk-campaign processing and retry handling

Source AL code plus deployment package, and configuration documentation and a short admin/user guide

¿Para quién es esto?

Service & support teams

Agents resolving cases who need to text customers appointment reminders, status updates, and quick confirmations directly from the Service or case record without leaving Business Central.

Sales reps and account managers

Sellers who want a chat-style thread on the Contact and Sales Order so SMS follow-ups, quote nudges, and delivery alerts are logged against the deal automatically.

Marketing teams

Marketers running segmented bulk SMS campaigns to BC contact lists with templated, multi-language messages, consent handling, and per-recipient delivery reporting.

Cómo se compara SMS for Dynamics 365 CRM (Twilio/Multi-Gateway)

Criterio	ECOSIRE	Construcción personalizada	Competidor
Two-way SMS embedded on BC records (Customer, Contact, Sales Order)	Incluido	Apoyo parcial	Apoyo parcial
Event-triggered automated texts via AL event subscribers	Incluido	Incluido	Apoyo parcial
Bulk/segmented campaigns processed through the BC job queue	Incluido	Apoyo parcial	Apoyo parcial
Multi-gateway support (Twilio, Vonage, MessageBird) by configuration	Incluido	Apoyo parcial	No incluido
Built, installed as a per-tenant extension, and supported for you	Incluido	No incluido	No incluido
Tailored to your exact triggers, templates, and consent rules	Incluido	Incluido	No incluido
Optional Dataverse / Power Platform integration	Incluido	Apoyo parcial	Apoyo parcial
Retested against each Business Central major release	Incluido	No incluido	Apoyo parcial

Preguntas frecuentes sobre SMS for Dynamics 365 CRM (Twilio/Multi-Gateway)

Is this an instant download from Microsoft AppSource?

No. This is build-to-order software. After purchase ECOSIRE scopes your gateway and trigger requirements, develops the AL extension, and installs it on your Business Central tenant as a per-tenant extension. There is no instant AppSource download — you receive a tested, configured solution installed on your own environment.

How long does delivery take?

Typical lead time is about 2 to 4 weeks from the scoping call, depending on how many automated triggers, templates, and gateways you need and whether Dataverse/Power Platform integration is included. We confirm a firm timeline in writing after the initial scoping call and keep you updated through build and install.

How does ongoing support and updates work?

ECOSIRE supports the extension after handover, including fixes and configuration help. Because Microsoft ships Business Central updates regularly, we retest and adjust the extension against new major releases so it keeps working. Support and update terms are agreed during scoping; the build price covers initial delivery, and ongoing maintenance is offered as a separate arrangement.

Which SMS gateway do I need, and do I pay for messages separately?

You choose Twilio, Vonage, or MessageBird. You hold your own gateway account and pay that provider directly for message traffic and phone numbers. The extension connects to your account via its REST API using credentials stored securely in Business Central isolated storage.

Can the SMS data also appear in Dataverse or Power Platform?

Yes, optionally. We can surface the SMS log in model-driven apps and expose it to Power Automate flows through the Dataverse / Power Platform integration, so texting events can drive wider automation. This is scoped as an add-on to the core BC extension.