The podcast episode

Trond Jarnes, Business System Director at Jets Group, described AI-assisted order processing in Dynamics 365 Sales. Developed with ProsessPilotene, the solution targeted parts of the order process that could fit the sales team’s existing workspace.

What this means for the organisation

The customer example shows the value of a clear process boundary and control of exceptions. Manufacturers considering a similar approach should map order variation, incoming data quality and which decisions still require an employee.

Trond Jarnes described the solution from the perspective of Jets Group’s sales work and production-related order process. The case shows that automation must fit the existing workspace and handle variation in incoming orders. Document quality and exceptions determine how much can be processed automatically before an employee takes over.

Microsoft’s Sales plan records product capabilities and planned availability in the relevant release period. It helps date the vendor offering but does not show that a particular organisation achieved an outcome. The ProsessPilotene source shows the demonstration or case; the release plan supplies product context and bounds the timeline.

For sales work, testing should attach to a concrete stage such as qualification, quoting or ordering. Data coverage, rejected suggestions and review time should be recorded alongside outcomes. This distinguishes support in the real workflow from a feature that appears convincing in a bounded demonstration.

Sources

Primary source: ProsessPilotene, “Smartere og enklere ordrebehandling i produksjonsbedrifter,” 27 January 2026 (Norwegian).

Microsoft, Dynamics 365 Sales 2024 release wave 1 plan, 25 January 2024.

Join the discussion

Which experience from your own organisation is most relevant to this story? Share what you learned.