Microsoft Dynamics 365 Customer Experience Analyst : Configure text messages

Configuring text messages in Dynamics 365 Sales enables sales teams to communicate with customers via SMS directly from the system, creating a seamless multichannel engagement experience. This setup involves integrating a supported SMS provider, such as Twilio or Azure Communication Services, and configuring the necessary connection settings within Dynamics 365. Once configured, users can send and receive text messages linked to leads, contacts, or opportunities, ensuring that all interactions are tracked within the customer record. Automated workflows or Power Automate flows can also be used to trigger text messages for reminders, follow-ups, or promotional updates. By enabling text messaging, organizations can enhance customer engagement, improve responsiveness, and maintain a complete record of all communications for better sales tracking and relationship management.

1. Understanding SMS Capabilities in Dynamics 365 Sales

Dynamics 365 Sales, by itself, does not send SMS messages natively out of the box. However, there are three main ways to enable text messaging:

• Using Microsoft’s Digital Messaging / Omnichannel capabilities (part of Customer Service or Customer Insights – Journeys).
• Using Power Automate with an external SMS provider (e.g., Twilio, Azure Communication Services, ClickSend, MessageBird).
•  Using ISV solutions (third-party add-ons) from AppSource or custom plugin integration.

The most suitable option depends on your organization’s licensing, scalability needs, and infrastructure.

2. Option 1 — Using Microsoft Digital Messaging (Native Option)

If your environment has Customer Service Enterprise or Customer Insights – Journeys (formerly Marketing), you can configure SMS as a communication channel.

Prerequisites

 Dynamics 365 Customer Service Enterprise or Customer Insights – Journeys license.

• Access to Omnichannel for Customer Service (for conversational SMS) or Journeys (for outbound SMS).
• A verified SMS provider account (e.g., Azure Communication Services or Twilio).
• Administrative permissions in Power Platform Admin Center.

Steps

 Step 1: Enable Digital Messaging Channel

1. Go to Customer Service Admin Center → Channels → SMS.

2. Select Add SMS channel.

3. Choose your provider (e.g., Twilio, Azure Communication Services).

4. Enter:

•  Account SID / API Key
•  Authentication Token
•  Phone number (Sender ID)

 Step 2: Configure Workstream

• Create a workstream to manage SMS interactions.
• Define routing rules, auto-assignment, or queues for incoming messages.
• Associate with a Sales Team Queue for tracking customer responses.

 Step 3: Test and Validate

• Send a test message to a contact.
• Check that replies appear as a conversation in the Timeline or Conversation pane.
• Ensure messages are stored under Activities → SMS Message.

 Step 4: Use in Customer Journeys (for Marketing/Sales)

Use Customer Insights – Journeys to send bulk or triggered SMS messages (e.g., appointment reminders, order updates, sales follow-ups).

 3. Option 2 — Power Automate with SMS Connector (Flexible Option)

For organizations using Dynamics 365 Sales standalone, Power Automate provides the most flexible way to send SMS.

Prerequisites

• Dynamics 365 Sales (Dataverse access).
• Power Automate Premium or included flow license.
• SMS provider account (e.g., Twilio, ClickSend, or Azure Communication Services).

Steps

 Step 1: Create a Power Automate Flow

1. Go to make.powerautomate.com → Create → Automated cloud flow.

2. Trigger: When a record is created or updated (in Dataverse)

   e.g., Trigger when a Follow-up Reminder or Appointment Confirmation is created.

Step 2: Add “HTTP” or “Twilio” Connector

 If Twilio:

• Choose Twilio – Send Text Message (SMS).
• Provide Account SID, Auth Token, and From/To Numbers.
•  If using Azure Communication Services:
• Use the HTTP action.
• Call the ACS REST API endpoint to send messages.

Step 3: Map Fields

• Map recipient phone number from the Contact/Lead entity.
• Compose your message text dynamically:

Hi @{triggerOutputs()?['body/firstname']}, your sales appointment is scheduled on @{triggerOutputs()?['body/scheduleddate']}.

 Step 4: Test and Log Message Activity

•  Add a Create a new record (Activity → SMS Message) step in Dataverse to log the message.
•  Validate message delivery in the contact timeline.

Example Use Cases

 Send a text reminder when an Opportunity reaches the “Proposal Sent” stage.

 Notify a Sales Rep via SMS when a high-value lead is assigned.

 Automate “Thank you for your purchase” messages post-conversion.

4. Option 3 — Using Third-Party ISV Solutions

If you prefer plug-and-play functionality without custom flows, use ISV solutions available in AppSource, such as:

•  Twilio SMS Integration for Dynamics 365
•  ClickDimensions SMS
•  TeleMessage
•  SMSLink for Dynamics 365

Advantages

• Prebuilt dashboards for sent/received messages.
• Two-way conversation tracking inside Dynamics timeline.
• Templates, bulk sending, and consent management.

Installation Overview

1. Go to [AppSource](https://appsource.microsoft.com).

2. Search for the preferred SMS solution.

3. Install the managed solution into your Dynamics environment.

4. Configure your provider credentials in Settings → SMS Configuration.

5. Test sending from the Contact or Lead record ribbon.

5. Data Model — How SMS Messages Are Stored

When SMS is configured (via Omnichannel or ISV):

 A new activity type SMS Message is created in Dataverse.

 It includes fields like:

• To / From Number
• Message Text
• Direction (Incoming/Outgoing)
• Status Reason (Sent, Failed, Delivered)
• Regarding (Contact, Lead, Opportunity, Case)

This allows messages to appear on the Timeline, enabling full customer interaction visibility.

6. Compliance, Security, and Consent

When implementing SMS messaging in Dynamics:

• Always obtain explicit consent from customers before sending promotional texts (GDPR, CAN-SPAM, etc.).
• Store opt-in status in Contact preferences.
• Configure Data Loss Prevention (DLP) policies in Power Platform.
•  Use field-level security to protect phone numbers and message history.
•  Enable auditing on the SMS Message entity for compliance tracking.

7. Monitoring and Analytics

•  Use Power BI to visualize SMS metrics (sent, delivered, failed, replied).
•  Use Customer Insights to segment customers based on response patterns.
•  Set up Power Automate alerts for delivery failures.
•  Track conversation sentiment with Azure Cognitive Services if applicable.

Example: Twilio SMS Integration via Power Automate

Flow Summary:

 Trigger: “When Opportunity Stage = Proposal Sent”

 Actions:

  1. Retrieve Contact details (name, phone).

  2. Send message via Twilio connector.

  3. Log message as an Activity in Dynamics.

  4. Update “Last SMS Sent” date on the contact.

Sample message:

Hi John, thank you for your interest in our product. Our team will reach out shortly to discuss your proposal. – Contoso Sales Team

Summary:

By integrating SMS messaging into Dynamics 365 Sales, organizations can:

•  Engage customers instantly.
•  Enhance follow-up efficiency.
•  Enable real-time notifications for sales teams.
•  Improve customer satisfaction through personalized outreach.

Whether you choose Microsoft’s native Omnichannel, Power Automate, or third-party connectors, ensure the configuration follows security, consent, and ALM best practices for reliable communication.