The assistant follows the role across tools

At Ignite on 15 November, Microsoft presented Copilot for Sales and Copilot for Service. The sales assistant was intended to connect CRM data with Outlook and Teams, while the service assistant would use contact-centre knowledge sources in the working interface. Copilot for Service was scheduled for public preview in December and general availability in the first quarter of 2024. It was therefore a product direction and timeline, not a function everyone could use in November.

For sales and service leaders, such a connection changes where work happens. An employee can read a summary or prepare follow-up without first opening CRM. The system displaying information does not automatically become its source of truth. Customer status, consent, agreements, and case history still need to be owned and updated in agreed systems. Otherwise, the assistant can present a tidy summary of outdated information.

In October, Gartner advised sales leaders to assess generative AI through sales outcomes and concrete tasks. The analyst identified meeting preparation, account summaries, and next activities among the use cases. This suggests a practical pilot: measure preparation time, the proportion of summaries requiring correction, and whether the seller records the result back in CRM. A forecast from a vendor or analyst should not be recorded as the organisation’s own benefit.

Field service received a mixed availability plan

Microsoft’s field service update separated several delivery dates. A redesigned web work-order surface was generally available. The Outlook add-in and scheduling support in Teams were scheduled for general availability in December, while Copilot in the Field Service mobile app was planned for public preview. A technician would be able to receive a summary and update completed work in natural language.

This can reduce handovers between inbox, dispatcher, and field, but the automation affects operational data. Before rollout, the organisation must decide who confirms timing, parts, skills, and customer address. Mobile updates must work under limited connectivity and handle conflicts if the same order changes in several places. Relevant measures include schedule changes, incomplete orders, synchronisation errors, and first-time resolution, rather than only the number of Copilot calls.

Marketing and sales share more customer signals

For Customer Insights, Microsoft scheduled a December preview that would create customer-profile summaries for sellers using demographic, transactional, and behavioural data. An Optimizely integration was intended to make segments and journeys available for personalised campaigns. Both were future previews at the intended publication date.

When a marketing segment is used in sales or an external channel, its definition and consent basis need to travel with it. Marketing should own purpose, channel, and brand requirements; sales should own qualification and follow-up. Automated summaries can support the handover, but the teams need a shared explanation of signals and a mechanism for correcting errors in the underlying customer data.

On 8 November, Forrester argued that marketing leaders should plan for a new division of work between people and machines, anchored in customer experience rather than individual features. This supports task-by-task adoption: retain human accountability for audience, message, and exceptions, then assess which parts AI can prepare.

Collaboration requires visible accountability

Role-based assistants promise less switching between apps, but they also cross organisational boundaries. A customer case can be read in Outlook, discussed in Teams, and updated in CRM. Management should map which actions the assistant only suggests, which it can perform, and where human approval is required. A shared exception register across marketing, sales, service, and field makes it possible to improve sources and process without hiding errors behind a smooth interface.

A simple responsibility matrix can name the data owner, process owner, and approver for each scenario. It should also state who corrects an error and how employees are informed when a source or automated action is temporarily withdrawn.

Sources

Microsoft Dynamics 365, 15 November 2023

Microsoft Dynamics 365 Field Service, 15 November 2023

Gartner, 24 October 2023

Forrester, 8 November 2023

Join the discussion

Where in your sales process do you spend the most time on manual follow-up? Share your experience.