# Real-world scenarios ## Overview This article walks through one of the most common field service disruptions, a technician needing to leave early, and shows how the Dispatcher Assistant handles it end to end. The scenario is shown twice: once through the Microsoft Teams interface, and once through the Dispatch interface. Both result in the same outcome, illustrating that the Dispatcher Assistant operates consistently across whichever interface the dispatcher is working in. ### Scenario: Technician Leaves Early, Reassignment via Microsoft Teams A technician has to go home early, leaving a job unassigned for the remainder of the day. Without the Dispatcher Assistant, this would require the dispatcher to identify the affected job, check who has capacity, evaluate their suitability, make the reassignment, notify the new technician, and contact the customer, multiple steps across multiple systems, typically taking 10 to 20 minutes per disrupted job. #### Step 1: Exception Detected The Dispatcher Assistant detects that the technician needs to leave early and proactively surfaces the issue in Microsoft Teams before the dispatcher has spotted it manually. It immediately pulls the relevant job details, what was scheduled, the timing, and the expected duration, so the dispatcher has full context from the first message. #### Step 2: Available Resources Identified The system analyzes engineer availability and evaluates who has the capacity, skills, and travel feasibility to take the job. Two available technicians are surfaced as options. Alongside each option, the Dispatcher Assistant includes additional context, previous experience with similar jobs, current availability, location, and any other relevant factors, giving the dispatcher everything needed to make the right call quickly. #### Step 3: Dispatcher Makes the Selection The dispatcher reviews the options in Teams and selects the technician they want to assign. The decision takes seconds rather than the time it would have taken to manually investigate each option. #### Step 4: Reassignment Executed The Dispatcher Assistant populates the reassignment details and pulls any relevant resources for the job, documentation, job context, or other materials, sending them directly to the newly assigned technician. The schedule is updated automatically. #### Step 5: Feedback Captured The dispatcher gives a thumbs up or thumbs down on the recommendation. This simple feedback loop helps the Dispatcher Assistant track and improve its performance over time, both in how it ranks options and how it presents context for decision-making. #### Step 6: Customer Notified Automatically The Dispatcher Assistant emails the customer to let them know their schedule has changed. No manual email drafting, no risk of the notification being missed or delayed. The customer is informed promptly with a clear, professional message. **Result:** A process that would normally span multiple steps, multiple people, and significant back-and-forth is resolved end to end with a few keystrokes. The job is reassigned, the new technician is briefed, and the customer is notified, all handled through a single Teams interaction. ### Same Scenario: Reassignment via the Dispatch Interface The same exception, a technician leaving early, can also be handled directly through the Dispatch interface rather than Teams. The process and outcome are identical; the interface is different. The Dispatcher Assistant surfaces the notification in the Dispatch interface, providing the same level of detail: which job is affected, the original schedule, and how long it was set to last. Two available resources are presented with additional context to support the decision. The dispatcher selects the preferred technician, the job is reassigned, relevant resources are shared with the new technician, and the customer is automatically notified. The feedback mechanism works the same way, the dispatcher gives a thumbs up or down, and the full decision is logged with an audit trail. ## What This Scenario Illustrates **Exceptions are caught proactively, not reactively.** The Dispatcher Assistant surfaces the issue before the dispatcher has had to spot it themselves, early enough that a clean reassignment is straightforward rather than a last-minute scramble. **Options come with reasoning, not just names.** The system doesn't just show who is available, it provides the context behind each option, so the dispatcher's decision is informed rather than instinctive. Experience, availability, and location are all surfaced alongside the recommendation. **The dispatcher makes the decision; the system does the rest.** Once the dispatcher selects a technician, everything else, the reassignment, the technician briefing, the customer notification, happens automatically. The dispatcher's role is the judgment call, not the coordination work surrounding it. **Customer communication is never a separate step.** Notifying the customer is part of the same automated process, not an afterthought. The customer receives a timely, professional update without the dispatcher having to draft or send anything manually. **The interface is flexible; the process is consistent.** Whether the dispatcher is working in Teams or in the Dispatch interface, the same structured process applies, the same context, the same ranked options, the same automated execution after confirmation. This consistency reduces reliance on individual dispatcher experience and ensures exceptions are handled the same way across teams and regions. **Feedback improves future recommendations.** The thumbs up/down mechanism is not just a nicety, it creates a structured signal that helps the Dispatcher Assistant refine how it ranks and presents options over time. --- # 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/real-world-scenarios.md?ask= ``` 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.