# Fundamentals

## Overview

The Dispatcher Assistant is an AI-powered Digital Worker designed to keep field service operations stable when conditions aren't. It monitors live schedules and execution signals continuously, identifies exceptions and SLA risks early, while corrective options still exist, and generates ranked reallocation options with clear reasoning behind each one. Low-risk actions can proceed automatically. Higher-impact decisions are escalated to dispatchers with everything needed to confirm quickly. Customer communication is handled throughout, keeping all parties informed without adding to the dispatcher's workload.

By converting reactive, manual exception handling into a structured, proactive process, the Dispatcher Assistant gives dispatch teams time back for the complex trade-offs, difficult customer conversations, and judgment calls that genuinely require human experience.

## Key Benefits

**Early exception detection:** SLA risks and schedule disruptions are identified as they develop, not after a breach has already occurred, giving dispatchers time to act while options are still available.

**Ranked reallocation options:** When an exception is detected, the system evaluates engineer availability, skill match, travel feasibility, and downstream impacts, then surfaces ranked options with the reasoning behind each one, so dispatchers make informed decisions rather than quick guesses.

**Automated customer communication:** Customers are notified automatically when schedules change, appointments are renegotiated via email or SMS, and confirmations are handled end to end, without dispatcher involvement for routine cases.

**Consistent exception decisions:** All disruptions follow the same structured, explainable flow aligned with PSO logic, eliminating the variability that comes from relying on individual dispatcher experience across regions and teams.

**Scalable disruption management:** The same approach handles both individual exceptions and large-scale regional events such as weather or outages, without requiring additional dispatcher headcount.

**Full traceability:** Every exception, recommendation, and schedule change is tracked and auditable end to end.

## The challenge it solves

Dispatch teams operate in a constant state of disruption. Delays, cancellations, overruns, and last-minute customer changes force dispatchers into reactive firefighting. SLA risks are often identified too late, schedules are manually reshuffled mid-day, and communication across customers, engineers, and systems becomes fragmented. At scale, regional events amplify the problem, creating operational bottlenecks and inconsistent outcomes.

In practice, dispatchers are spending 40 to 60% of their time on exception management: manually reassigning jobs, calling or emailing customers to reschedule, spending 10 to 20 minutes per disrupted job on coordination, managing bulk disruption events without a structured process, and relying heavily on individual experience to make reallocation decisions. Schedule changes and customer communication are handled separately, creating gaps and inconsistency.

## Before and After

### Before

Before the Dispatcher Assistant, handling a schedule exception requires manual effort at every stage:

{% stepper %}
{% step %}
Monitor engineer delays, overruns, and incoming exceptions
{% endstep %}

{% step %}
Review job details, SLA commitments, and the current schedule
{% endstep %}

{% step %}
Assess impact across downstream appointments
{% endstep %}

{% step %}
Identify conflicts and prioritization issues
{% endstep %}

{% step %}
Manually explore reallocation or rescheduling options
{% endstep %}

{% step %}
Contact customers to renegotiate appointments
{% endstep %}

{% step %}
Update the schedule and systems with agreed changes
{% endstep %}
{% endstepper %}

This process is slow, inconsistent across teams, and limited in its ability to account for downstream impacts before changes are made.

### After

With the Dispatcher Assistant, the same process runs in five automated steps:<br>

{% stepper %}
{% step %}
Detect exceptions in real time, monitors delays, overruns, and regional events automatically
{% endstep %}

{% step %}
Evaluate impact on schedule and SLA, identifies affected appointments using PSO and business rules
{% endstep %}

{% step %}
Generate optimized resolution options, proposes engineer swaps, resequencing, or alternative slots
{% endstep %}

{% step %}
Orchestrate customer negotiation, engages customers via email or SMS, presents options, manages responses
{% endstep %}

{% step %}
Execute and update systems, confirms the new appointment, updates IFS Cloud, logs the outcome and audit trail
{% endstep %}
{% endstepper %}

## How It Works

The Dispatcher Assistant continuously monitors live schedules and execution signals in PSO, interpreting customer and system-driven exceptions and assessing their impact on time-to-breach, SLA exposure, and engineer capacity.

**When an exception is detected:** the system evaluates the situation using real-time availability, engineer capability and location, SLA and priority constraints, travel optimization, and customer history, accounting for downstream impacts before any recommendation is made.

**Best-fit appointment options are generated:** ranked by SLA exposure, travel efficiency, and priority. For routine, low-risk exceptions the system can proceed automatically. For higher-impact or lower-confidence decisions, the exception is escalated to the dispatcher with ranked options and clear reasoning, everything needed to confirm quickly without additional investigation.

**Customer communication is managed throughout:** proposing new appointment windows, handling back-and-forth responses, refining slots based on customer feedback, and confirming the agreed appointment across all stakeholders.

**All decisions are revalidated and logged before commit:** maintaining full oversight and auditability.

## What Triggers the Dispatcher Assistant

The Dispatcher Assistant responds to a wide range of operational exceptions that break or threaten the live schedule:

**Engineer availability shifts:** engineer calls in sick, is stuck in traffic, experiences a vehicle breakdown, exceeds driving hours, or has a certification lapse.

**Job duration drift:** a job overruns its expected duration due to asset complexity, unexpected parts requirements, or safety escalations.

**SLA and priority changes:** a customer escalates, a VIP account is prioritized, an asset criticality is reclassified, or a regulatory deadline approaches.

**Parts and material disruptions:** a required part is unavailable at van stock, a transfer is delayed, or an incorrect part was dispatched.

**Customer behavioral changes:** a customer cancels last minute, restricts site access, or requests a different appointment window.

**Environmental and external event:** severe weather, flooding, transport strikes, or regional power outages requiring bulk rescheduling.

**System and data anomalies:** duplicate work orders, missing SLA data, or scheduling rule misconfigurations.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kb.theloops.io/digitalworkers/ifs-loops-digital-workers/digital-worker-guides/dispatcher-assistant/core-concepts/fundamentals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.