WhatsApp and SMS channels in Customer Service

For growing slices of the customer base, WhatsApp and SMS aren't secondary channels — they're the primary ones. Many customers prefer messaging over calls or emails, and customer service organisations that don't meet them on these channels lose the relationship. Dynamics 365 Customer Service supports both natively as part of the omnichannel stack.

WhatsApp Business. Microsoft offers WhatsApp Business integration through:

• WhatsApp Cloud API (Microsoft's direct integration, recommended for new tenants).
• WhatsApp via Infobip, Twilio, or other BSPs (Business Solution Providers) — partner connectors.

Provisioning WhatsApp.

1. Acquire a WhatsApp Business phone number (separate from any personal WhatsApp number) through Meta Business Manager.
2. Verify the business through Meta's verification process (required for WhatsApp Business API access).
3. Configure the WhatsApp number in Dynamics 365's omnichannel admin.
4. Define operating hours, routing rules, agent capacity for the channel.
5. Set up message templates — Meta requires pre-approved templates for outbound messages (proactive outreach to customers).

WhatsApp message templates. WhatsApp Business has strict rules about who initiates contact. Customers can message the business freely; the business can only respond within a 24-hour window after the customer's last message. Outside that window, the business can only send pre-approved message templates (greeting, appointment reminder, order update, etc.). Templates go through Meta approval and can take days. Plan for this.

SMS. SMS is more straightforward — most countries have local SMS regulations, but the operational mechanics are similar:

• SMS provider — Azure Communication Services, Twilio, Infobip, or country-specific carriers.
• Sender number — short code (high-volume marketing) or long code (transactional, conversational).
• Two-way capable number — required if customers can reply.

The agent experience. Once configured, WhatsApp and SMS conversations route through Unified Routing like other channels. The agent sees them in their Customer Service workspace alongside chats, voice calls, and emails, with the same productivity pane, conversation history, and Copilot assistance. Conversation summarisation, suggested replies, and knowledge articles work the same way.

Identity binding. Inbound WhatsApp / SMS messages identify the customer by phone number. The platform matches the phone number to a Dataverse contact; unmatched numbers prompt the agent to create or link the contact. Persistent conversation history binds future messages from the same number to the same contact automatically.

Rich media. WhatsApp supports images, videos, audio messages, documents, locations, and structured cards. SMS supports text only (and MMS where carriers allow). Build conversation patterns around what each channel can carry.

Compliance.

• Customer opt-in — both WhatsApp Business and most SMS regulations (GDPR, TCPA in the US, equivalent rules elsewhere) require explicit customer consent before outbound messaging. Capture and audit consent.
• Opt-out — every outbound message includes an opt-out instruction; the platform must honour opt-out immediately.
• Record retention — messages are stored as Dataverse records; retention policy applies per regulatory requirements.

Common pitfalls.

• WhatsApp template approval lag — partner templates often need editing before Meta approval. Plan launch with buffer.
• Conflating personal numbers — agents using personal WhatsApp for business breaks audit, doesn't route, doesn't track. Always use the official business channel.
• SMS cost surprise — high-volume SMS bills can be substantial. Monitor consumption.

Operational reality. WhatsApp and SMS adoption improves customer satisfaction measurably in many demographics — but requires the same discipline as any service channel. Train agents, monitor response time, capture consent, comply with regulations.