From suggestions to actions

On 21 October, Microsoft introduced ten autonomous agents for Dynamics 365. Sales Qualification Agent was designed to research and prioritise leads, while Customer Intent and Customer Knowledge Management Agent would build a knowledge base for service. Case Management Agent focused on case flow, and Scheduling Operations Agent would help dispatchers handle changes in field service.

The common change was a move from drafting text to taking actions within a process. Data access and status changes therefore mattered more. A summary could be checked before use; an agent that created, prioritised or moved work affected customers and employees directly. Each action needed a defined mandate, a log and a point for escalation.

The announcement combined previews with planned capabilities. Organisations therefore had to inspect availability for each agent rather than treat the catalogue as production-ready. A decision paper needed to record the environment, region, licence and date of the test. That allowed a pilot result to be distinguished from capabilities that had only been demonstrated or had not reached the tenant.

Marketing and service gained a connected view

The October Customer Insights – Journeys update previewed inflow and exit analytics at each journey step, heat maps for email links and multiple starting segments in one journey. The announced six-month limit also took effect: older message links stopped producing tracking results, while SMS and unsubscribe links more than six months old stopped working.

This changed how a connected customer journey could be measured. Marketing could see where participants left, sales could receive qualified signals, and service could get better context. Field scheduling belonged in the same information chain when a case required a visit. The statuses still needed shared meanings across systems; otherwise, agents merely automated existing breaks.

Heat maps and step data could also change the discussion about campaigns. A high click count said little if the recipient later dropped out or had to contact service. By linking journey insight with lead, case and work-order status, teams could examine which communication led to the intended next action and which messages created new friction.

Maturity had to be assessed task by task

Forrester published a state-of-the-market report on 3 October that described wide variation in maturity and time to benefit across agent use cases. It provided a useful counterweight to the vendor’s broad launch. The existence of a technical preview did not show that the data, process or organisation was ready for independent actions.

A suitable pilot target was therefore narrower than a “better customer journey”. A team could select one lead type, one case category or one field scheduling area, then measure correct routing, waiting time, manual corrections and escalations. If the agent did not improve at least one measure without weakening another, October’s capabilities gave little reason to expand the scope.

Sources

Microsoft Dynamics 365 Blog: Transform work with autonomous agents across business processes, 21 October 2024.

Microsoft Dynamics 365 Blog: 2024 release wave 2 launches with Copilot capabilities, 29 October 2024.

Microsoft Learn: Customer Insights – Journeys: October 2024 update, October 2024.

Forrester: The State Of AI Agents, 2024, 3 October 2024.

Gartner: Harness Customer Success Trends and GenAI to Drive Revenue Growth, 21 October 2024.

For discussion

Which customer process has a clear start, a measurable outcome and a safe point for human review?