Small and medium business | Business Central, N...

Best way to integrate SMS notifications in Dynamics workflows?

(3) Share

Report

Posted on by AB-30040537-0

Hi everyone,

I’m working on a requirement where we need to send real-time notifications from Dynamics (for example: order updates, approval alerts, or customer confirmations). While email is already in place, we’re exploring SMS as a faster and more reliable channel for critical updates.

I wanted to understand from the community:

What’s the best way to trigger SMS from Dynamics (Power Automate, plugins, or external APIs)?

How do you handle delivery tracking and retries?

Any recommended approach for scaling this in high-volume scenarios?

I came across some SMS platform solutions like https://almuqeet.net/products/sms-platform and was wondering if integrating something like this via API is the right approach, or if there are better native options within Dynamics.

Would love to hear your experiences or best practices.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Kamal Khakhkhar 3,428 on at

Like (2)

Report
Copy link

Link copied!

Hii There,
as per your requirement you can go through microsoft Document . as per below or use AppSource Extension if you want or create for That

https://learn.microsoft.com/en-us/dynamics365/sales/manage-text-message-communications

if you found answer , Mark This verified.
Thank You.
Kamal Khakhkhar

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 17,681 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,
The best approach depends on volume: for low/medium volume, use Power Automate triggered from Dataverse/Dynamics records and call an SMS provider connector/API; for high-volume or critical notifications, avoid putting all logic in Power Automate delays/retries and use a more scalable pattern: Dataverse event → lightweight flow/plugin/webhook → Azure Service Bus → Azure Function → SMS provider such as Azure Communication Services, Twilio, Infobip, etc. For tracking, store each SMS as a custom “Notification Log” record with status, provider message ID, retry count, error message, and timestamp; then update it from the provider callback/webhook where supported. Integrating an external platform like the one you shared can be fine if it has solid REST APIs, delivery receipts/callbacks, throttling, and retry support, but I’d first compare it with native-supported providers in Dynamics/ACS, especially if you need compliance, scaling, and supportability.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No

Join the conversation

Community site session details

Best way to integrate SMS notifications in Dynamics workflows?

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Best way to integrate SMS notifications in Dynamics workflows?

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates