Kenner vs the AI built into your FSM: Agentforce for Field Service and Dynamics 365 Copilot

Side by side

Salesforce and Microsoft details and list prices are from their own product, pricing and documentation pages, last checked 10 November 2026.

What Agentforce for Field Service does well

Salesforce’s pricing page describes it as assistive AI for dispatchers and mobile workers. For the technician it lists a Pre-Work Brief, On-site Knowledge Search, Multimodal Troubleshooting and a Post-Work Summary. For the office it lists schedule summaries, help resolving schedule gaps, an asset health score and capacity planning.

Salesforce has also thought about the drive to site. In its deep dive it describes technicians playing back the pre-work brief on their phone through a Siri shortcut, so they hear it without taking their eyes off the road.

If Salesforce is your system of record for work orders, assets and knowledge, the strength is obvious: one vendor, one data model and one set of permissions.

What Copilot in Dynamics 365 Field Service does well

Microsoft’s documentation lists what Copilot does today: work order summaries on demand, with status, priority, related activities and recommended next actions; work order updates from natural language, typed or spoken, in the mobile app, currently in preview; and questions in natural language about the data in the system. On its product page Microsoft adds that Copilot can search lengthy product manuals for answers.

For the office there is inspection template creation from PDFs or images, and an agent feed for supervising agent-generated tasks. And the price is hard to argue with: Microsoft’s pricing page lists Copilot assistance as included in the Field Service licence.

Where Kenner is different

It works across systems, not inside one

The AI in an FSM answers from that FSM. In commercial HVAC and refrigeration, half the story is often somewhere else. Kenner reads store and rack controllers (Danfoss Alsense, Copeland Site Supervisor, Emerson E2/E3, CAREL boss), manuals and old reports in SharePoint or Confluence, and parts and stock in the ERP. It links them to the unit in a knowledge graph, next to the work orders from your FSM. See knowledge graph vs RAG for field service.

It meets technicians where they already are

Technicians save Kenner as a contact and use WhatsApp, iMessage, Microsoft Teams, RCS or a normal phone call. Nobody has to open the FSM’s app to ask a question or file a report.

It is built for HVAC and refrigeration

After a leak repair or a top-up, Kenner asks for what refrigerant records need under rules such as EPA 608 and F-gas, writes it to the unit’s record in your FSM and books the follow-up leak check.

It writes back to your FSM

Kenner does not become another system of record. With Salesforce Field Service, the record goes to the work order and the asset. With Dynamics 365 Field Service, it is written back to the work order and the asset as well.

Who should pick which

Use the built-in AI if your technicians already work in the Salesforce or Dynamics 365 mobile app all day, the knowledge they need is maintained in that platform, and you want scheduling and dispatch help as much as help on the job.

Add Kenner if the answer to a fault usually depends on data outside the FSM, your technicians prefer to text or call, or you want reports and refrigerant records written from a voice note and saved to the work order.

The same reasoning applies to other platforms. If you run ServiceTitan, read Kenner vs ServiceTitan Atlas. For an independent enterprise platform, read Kenner vs Aquant.

Common questions