Dynamics 365 Field Service and route-aware slot booking

What Dynamics 365 Field Service documents about customer booking

Dynamics 365 Field Service supports customer self-service through the Customer Service Hub portal and Power Pages. Customers request service against customer assets, see asset status and agreement status, view incident types, and pick from offered time slots. The portal is branded, hosted and integrated with the Dynamics 365 data model. The slots it offers come from the bookable resource capacity model against territory.

What neither the Customer Service Hub nor the Schedule Board positions as a lead capability is route-aware availability as a slot source: a calculation that asks, given the current optimized plan, which of the technically-available slots would the optimizer accept without breaking other commitments. Capacity availability and route-aware availability are different sets. The first answers “is there a resource free?” The second answers “can this slot be honored without dropping another one?”

Where capacity-aware slot booking reaches its boundary

The shape of operation where the difference starts to matter:

• Time-window-dense work. Many customers want narrow arrival windows. Capacity-aware booking can offer a 13:00-15:00 slot that nominally fits an engineer’s day; route-aware booking asks whether actually putting a work order in that window protects the other 11 commitments around it.
• SLA-locked stops. Agreement-driven preventive maintenance, customer asset visits and recurring programs with SLA windows: capacity-aware slots can chip away at those windows by accident. Route-aware slots protect them by design.
• High reschedule rate. Operations where customers reschedule often: capacity-aware portals create a steady stream of slots that look fine when picked but break the day when reconciled.
• Multi-characteristic mix. Where the right resource for a work order depends on characteristics: capacity-aware booking can offer a slot to a resource who can’t actually do the work. Route-aware booking matches characteristics to slot before offering it.

The cost of unrouteable bookings shows up as missed windows, coordinator escalations, and the slow drift of customer trust.

At a glance: a 50-engineer commercial service operation

A commercial service organization running calibration and break-fix service across a regional book. Fifty engineers in the field, dispatched out of two service centers. Roughly 70% of work comes in through the Dynamics 365 customer self-service portal: customers pick a slot against their agreement, the booking lands on the day’s Schedule Board, Resource Scheduling Optimization slots it into an engineer’s day within its configured scope. Field Service Mobile handles execution; Dynamics 365 tracks the customer asset, the agreement and the inventory.

The cost of capacity-only slots shows up downstream. A 13:00–15:00 slot offered to a customer at 09:00 looks fine in the portal but breaks the day when reconciled against the engineer’s actual position at 12:45 (still on a calibration from this morning, four jobs away from the customer). Failed-visit rate runs 8–10%. Coordinators absorb the reconciliation by phone. Customer trust drops on missed windows. Putting route-aware slot availability behind the same booking surface changes what comes back: only slots that the optimizer would accept against the current plan, given the customer’s location, the asset and the agreement SLA. Failed-visit rate typically drops to 3–5%. Around 70% of customer-driven reschedules go through without coordinator involvement. The portal continues to live in Dynamics 365.

How eLogii’s slot booking co-pilot works

eLogii’s slot booking endpoint takes a query (customer location, work type, required characteristic, SLA window) and returns only slots that fit the current optimized plan. The customer never sees eLogii. The booking surface keeps using the Dynamics 365 portal, Power Pages, SMS link, or whichever channel is in use. What changes is the source of the slot list.

• Route-aware availability. Slots returned are slots the optimizer would accept, not slots that nominally fit a capacity bucket.
• Characteristic-matched. Only resources who can do the work appear in the slot list. Characteristic mismatch never propagates to the customer.
• SLA-protected. Slots that would compromise existing SLA-locked commitments (agreement anniversaries, contract windows) are filtered out.
• Customer-driven reschedule. Reschedule slots come from the same endpoint. The customer picks a slot that already fits; the route re-optimizes around the new commitment.
• Live driver GPS context. Real-time progress feeds the slot calculation, so late-day slots reflect what’s actually happening on the road, not what was planned at 08:00.

How the integration sits with Dynamics 365 Field Service

The Dynamics 365 customer self-service portal (or Power Pages) stays in place. The slot list it shows is sourced from eLogii’s slot booking endpoint over REST. the connector is custom-built.

1. Customer initiates booking. Customer hits the Dynamics 365 self-service portal as normal. The branded surface, the asset view, the agreement check and the confirmation flow continue to live in Dynamics 365.
2. Slot availability query. The portal queries eLogii’s slot booking endpoint with the booking context (location, asset, required characteristic, SLA window).
3. Route-aware slot list returned. eLogii returns only slots that fit the current optimized plan. The portal renders them to the customer.
4. Booking confirmed. Customer picks a slot. The booking writes back to Dynamics 365 in the normal way. eLogii re-optimizes to absorb the new commitment. Field Service Mobile picks up the assignment.

Most teams complete the connector build in 3 to 5 weeks. The same endpoint covers customer-driven reschedule from any surface Dynamics 365 uses.

Frequently asked questions

What is the difference between the Dynamics 365 Field Service self-service portal and a route-aware slot booking layer?

Dynamics 365 Field Service provides customer self-service through the Customer Service Hub portal and Power Pages: customers request service against assets, see asset and agreement status, and pick from offered time slots based on bookable resource capacity. The booking surface (the journey, the brand wrapping, the asset view, the confirmation flow) sits in Dynamics 365. eLogii’s slot booking co-pilot is the route-aware availability calculation that powers the slot list: given the current optimized plan, which slots can actually be offered to a customer without breaking optimized routes. The customer never sees eLogii; the booking surface keeps using Dynamics 365. What changes is which slots come back.

Why does route-aware availability matter?

Three reasons. First, slots offered to customers should be honorable: a slot that breaks the optimized plan ends in a missed window or a panic reassignment. Second, route-aware slot booking cuts failed visits materially: eLogii customers report around 35% reductions in failed visits where this is implemented. Third, around 70% of customer-driven reschedules can be handled without coordinator involvement when the customer can only pick slots that already fit the plan.

Does this replace the Dynamics 365 customer self-service portal?

No. The portal stays in Dynamics 365. The customer journey, the asset view, the agreement and entitlement checks, the confirmation, the Dynamics 365 data model continue to live there. What changes is the slot availability source. The Dynamics 365 portal queries eLogii’s slot availability over REST, gets back only route-aware slots, presents them to the customer. The customer experience is unchanged in shape; the slots are different.

How does the integration sit?

Custom integration against the Dataverse Web API (OData v4) and eLogii’s REST API. The self-service portal in Dynamics 365 (or Power Pages) queries eLogii’s slot booking endpoint for available slots; eLogii returns only slots that fit the current optimized plan, given the customer’s location, the asset, the required characteristic and the SLA window. When the customer picks a slot, the booking is written back to Dynamics 365 in the normal way and eLogii re-optimizes to absorb the new commitment.

What about customer-driven rescheduling?

Same pattern. The customer initiates a reschedule through whichever surface Dynamics 365 is using (portal, Power Pages, SMS link, email confirmation). The available reschedule slots are sourced from eLogii’s route-aware availability. The customer picks a slot that already fits the optimized plan; the reschedule is written back to Dynamics 365 and the route re-optimizes around the new commitment. ~70% of reschedule requests handled without coordinator involvement in operations that implement this.