WhatsApp Business for Dynamics 365 CRM

This is a build-to-order extension, not an instant AppSource download. After a short scoping call to confirm your gateway (Meta Cloud API or Twilio), record types, templates, and triggers, typical delivery is around 2 to 4 weeks depending on the number of automations and integrations. We build the AL extension, install it as a per-tenant extension on your own Dynamics 365 / Business Central environment, configure your credentials and templates, and run a knowledge-transfer session before handover.

You'll need a WhatsApp Business account with an approved phone number through either the Meta Cloud API (WhatsApp Business Platform) or a Twilio WhatsApp sender, plus administrator access to the target Dynamics 365 / Business Central environment so we can deploy the per-tenant extension and configure the inbound webhook. We'll guide you through provisioning if any of these aren't set up yet. WhatsApp message templates must be submitted to and approved by Meta — we help you draft and structure them.

Yes. Every build includes a warranty period covering defects in the delivered extension at no extra charge. Beyond that, ECOSIRE offers ongoing support and maintenance — adapting to Business Central platform updates, gateway API changes, new templates, or additional triggers — under a support agreement scoped to your needs. Because you own the extension on your tenant, you're never locked out; we simply remain available to maintain and extend it.

Yes. Beyond the manual chat panel, we wire AL event subscribers and an optional job queue so messages fire on triggers you define — a new case, a stage change, an appointment reminder, an order confirmation. If you use the Power Platform, we can also dispatch messages from Power Automate flows on Dataverse events, so automation lives wherever your team already builds it.

Yes. API credentials, phone-number IDs, and webhook verification tokens are held in isolated, secured setup tables — never hard-coded. Access is governed by dedicated permission sets so you control who can read conversations, send messages, and manage templates or credentials. The inbound webhook validates the gateway's verification token, and all messages are logged per user for auditability. The extension follows Business Central per-tenant extension and AppSource technical conventions even though it's installed directly rather than via the marketplace.