Article content
In briefShow moreShow lessCustomer Service made three Copilot functions generally available in October.
- Customer Service made three Copilot functions generally available in October.
- Customer insight was intended to feed sales summaries and editable customer journeys, but parts of the wave remained in the future.
- Field Service put more of the work order in the mobile interface, including work with limited connectivity.
- Automation requires control of knowledge sources, customer data, and customer-facing text.
Service functions reached general availability
Microsoft made three Copilot functions generally available in Dynamics 365 Customer Service in October: questions against the organisation’s knowledge sources, email response drafts, and usage analytics. Case and conversation summaries had become available the previous month. Agents could see the sources behind an answer and rate it as helpful or unhelpful. Managers could monitor measures including usage, conversation duration, and the share of cases resolved with Copilot.
This moves some automation from a separate experiment into the normal service interface. The result still depends on the knowledge base and division of responsibility. A response draft can save time when an agent checks facts and tone. If outdated product information or the wrong case context reaches a customer directly, the same speed becomes a risk. Service teams therefore need an owner for source material, a feedback routine, and quality measures alongside time measures.
Customer insight was intended to carry into sales and marketing
In its release wave 2 presentation, Microsoft showed Customer Insights data feeding lead summaries in Dynamics 365 Sales. Visit and activity signals could appear alongside status and recent activity. For marketing, the company described customer journeys created in natural language, with suggestions for segments, triggers, timing, and branches. The generated journey could be edited, while style tools could take colours and typography from a web address.
The release wave ran from October 2023 through March 2024. Microsoft said many capabilities were available, while the remainder would enter preview or become generally available before April. A feature list is therefore insufficient as an adoption plan. Sales and marketing leaders need to check status, geography, and licensing for each scenario before basing training or performance expectations on it.
The connection between marketing and sales also makes data definitions a shared responsibility. A signal of interest is not the same as a qualified opportunity. The organisation must agree which activities affect priority, how long they remain relevant, and when a seller can override a recommendation. Facts, brand, and consent in customer-facing content still require approval before delivery, even if a first draft arrives faster.
Field work gained a more complete mobile surface
A separate Field Service update described the mobile app for Windows, Android, and iOS. Technicians could open work orders from Teams, view and update customer and asset information, conduct inspections, complete forms, and collect a signature. Microsoft highlighted work under limited connectivity. This was a product and partner presentation, not an independent measurement of impact.
For field service, management responsibility sits in the handover between contact centre, dispatcher, and technician. A digital checklist reduces paperwork only when the assignment contains the correct parts, skill requirements, and asset data. Measures should include complete work orders, first-time resolution, later data entry, and synchronisation errors. AI and automation can suggest and summarise, while responsibility for safe execution and customer approval must remain clearly human.
Controls must follow the customer journey
Forrester wrote in October that many executives overestimated how well their organisation understood generative AI. That matters when the same customer data feeds campaigns, sales priorities, service, and field assignments. Each step needs a defined data basis, an accountable role, and a method for detecting errors. Only then can an organisation compare whether automation produces faster and better customer work without treating a vendor’s planned capabilities as its own results.
A monthly cross-functional review can track exceptions and decide which automated steps should continue, change, or stop.
Sources
Microsoft Dynamics 365, 23 October 2023
Microsoft Dynamics 365, 24 October 2023
Microsoft Business Applications, 25 October 2023
Microsoft Dynamics 365, 26 October 2023
Forrester, 3 October 2023
Join the discussion
What have you learned from trying new marketing tools? Share what worked and what you needed to change.









