The messaging channel became part of the contact centre

On 3 September, Microsoft opened a public preview of a first-party WhatsApp channel in Dynamics 365 Contact Center. Organisations could connect a WhatsApp number, route conversations through queues and let representatives respond in the same workspace as other digital channels. Conversation context and customer information could follow the enquiry, reducing the need to copy details between separate tools.

For marketing and service, this was more than another inbox. A message could begin with a campaign, become a support case and later require a visit. The channel setup therefore had to respect what the customer had consented to receive, when automation handed the dialogue to a person, and how the history was linked to the right contact.

The September Customer Insights – Journeys update announced that, from 10 October, links in messages older than six months would stop producing tracking results, while SMS and unsubscribe links would expire after six months. Link lifetime, measurement and customer expectations therefore became concrete parts of channel design.

Technicians received a clearer mobile workspace

On 16 September, the new Dynamics 365 Field Service Mobile user experience became generally available. It included a new agenda, improved navigation and support for Copilot summaries. The aim was to make work orders, customer information and the next activity easier to reach while working at a customer site.

In a customer story published on 28 August, G&J Pepsi described how it used Field Service, Customer Service and Sales together across a large customer operation. Its results cannot simply be transferred to another organisation, but the story illustrated a useful design principle: a field solution creates value when scheduling, parts, customer information and commercial agreements work together.

The mobile experience also needed testing with the people who performed the work. Taps, searches for information and later re-entry were useful observations. If a technician still had to call the office for customer or parts information, the information flow was incomplete even after the app upgrade.

One customer journey needed shared definitions

September’s changes made it possible to connect digital conversations and physical follow-up more closely. The practical task was to define the handover. Which information should create a case? When should a case become a work order? Which status should the customer see, and who owned the follow-up if a visit uncovered a new sales or service need?

A useful pilot could follow one specific enquiry type from WhatsApp to a completed work order. The team could measure waiting time, manual handovers, missing information and reopened cases. Channel, CRM data and mobile workflow could then be improved together, without assuming that introducing a new channel would by itself fix the customer journey.

The pilot also needed to establish what should be shared and what remained channel-specific. Contact details, consent and case history could be common, while response times, message templates and escalation rules could vary. This boundary could give the customer a connected experience without forcing two different working situations into exactly the same process.

Gartner published research on 6 September recommending that bot design prioritise customer needs and remove barriers to expressing them. The same criterion applied to a WhatsApp pilot: measure whether customers reached the right help sooner, rather than only counting messages handled automatically.

Sources

Microsoft Dynamics 365 Blog: Try the first-party WhatsApp channel in Dynamics 365 Contact Center, 3 September 2024.

Microsoft Dynamics 365 Blog: General availability of the new UX in Field Service Mobile, 16 September 2024.

Microsoft Dynamics 365 Blog: G&J Pepsi profit rises with Microsoft Dynamics 365, 28 August 2024.

Microsoft Learn: Customer Insights – Journeys: September 2024 updates, September 2024.

Gartner: Improve Engagement With Chatbots and Voice Bots by Prioritizing Customer Needs, 6 September 2024.

For discussion

Where does customer history currently break between a campaign, the contact centre and a field visit, and which specific break should be addressed first?