Field Service and Customer Service integration

A customer calls about a broken HVAC. The contact centre agent opens a case. Investigation reveals an on-site technician is needed. A work order is created from the case; technician is dispatched. After service, work order closes; case closes; customer is satisfied. This Customer Service ↔ Field Service integration is one of the most common Dynamics 365 patterns, and one of the most operationally important.

The shared foundation.

• Both run on Dataverse.
• Customer / account / contact records shared.
• Common knowledge base.
• Unified user model.
• Same Power Platform extensibility.

The integration isn't a separate product; it's a built-in unification within the Dynamics 365 family.

Case-to-work-order flow.

1. Customer Service case captures the customer's report.
2. Agent diagnoses; determines field service needed.
3. Creates work order from case (action button).
4. Work order pre-populated with case data: customer, asset, description.
5. Case status updates to "In Field Service".
6. Field Service workflow takes over.

The reverse: work-order-to-case. Sometimes a field technician discovers an issue requiring office-side handling:

• Service uncovered something else.
• Customer dispute over scope.
• Billing question.

Technician notes; case created back to Customer Service for handling.

Linked records.

• Case ↔ Work Order is a link, not a merge.
• Each retains its own lifecycle.
• Status of one informs but doesn't dictate the other.

For reporting and analytics, linkage enables end-to-end view (call to resolution).

Agent handoff.

• Customer Service agent → Field Service dispatcher → Technician.
• Each handoff is a transition in record ownership.
• Notes carry forward; full context preserved.

Notifications at each handoff keep the customer informed.

Customer 360 view. From either app, the same customer is visible:

• Open cases.
• Open work orders.
• Recent service history.
• Asset list.
• Service contracts.
• Communication history.

This is the unified view — agents in either domain see what's happening across both.

Case types that route to Field Service.

• Equipment failure — technician dispatch.
• Installation request — new equipment setup.
• Inspection — routine site visit.
• Repair after warranty — paid service call.

Configuration determines which case types trigger field service workflow.

Workflow automation.

• Auto-create work order — when case categorised as "field service required".
• Auto-route — to appropriate technician queue.
• Status sync — work order status updates case.
• Closure cascade — closing work order closes related case.

Power Automate flows orchestrate; standard templates exist.

SLA management across both.

• Case has SLA — time to resolution.
• Work order has SLA — time to dispatch, time to complete.
• Both must be tracked.
• One overall SLA from customer's perspective (case raised to resolution).

Complex but essential for service operations with commitments.

Knowledge base usage in both.

• Customer Service agent searches KB to potentially resolve without dispatch.
• Field Service technician searches KB at the customer site for procedure.
• Same KB serves both.

KM (Knowledge Management) discipline benefits both surfaces.

Service contracts and billable services.

• Customer's contract determines coverage.
• Work order references contract.
• Billable items charged; covered items not.
• Customer Service agent knows contract status.

Unified across the products.

Returns and Reverse Logistics. For physical goods:

• Customer returns defective product (Customer Service handled).
• Field Service may collect or arrange courier.
• Linkages tracked.

Reporting across both.

• First call resolution rate — case resolved without dispatch.
• Dispatch rate — % cases escalating to work order.
• End-to-end resolution time — case open to resolved.
• Customer satisfaction — survey post-resolution.

These integrated metrics drive service operations decisions.

Common pitfalls.

• No standard escalation criteria. Each agent decides; inconsistent.
• Case stays open through work order. Or closes prematurely; reporting wrong.
• Customer messaged twice. Once from each side; communication fragmented.
• Knowledge silos. Service teams maintain separate KB; redundancy.
• Different SLAs not aligned. Customer sees one experience but internal SLAs treated separately.

Best practices.

• Defined escalation criteria — when does case become work order?
• Single customer-facing communication per resolution flow.
• Unified KB — one source.
• Cross-trained agents — understand both sides.
• Joint dashboards — leadership sees both.

Omnichannel integration. Voice / chat / email all converge:

• Customer chats; agent escalates to work order.
• Customer calls; agent dispatches.
• Customer emails; case → work order.

All in unified workspace.

Operational rhythm.

• Real-time — case / work order updates.
• Daily — queue review.
• Weekly — case-to-work-order conversion analysis.
• Monthly — leadership review of integrated metrics.

Strategic positioning. Customer Service + Field Service integration is the modern service operating model. The technical integration is built-in; the operational design (process flows, role responsibilities, KPIs) must be intentional. The competitive advantage isn't from having both products but from the seamless customer experience their integration enables. Invest in process design as much as technical configuration; the customer never sees the distinction between the two apps — they should never need to.