Dispatcher Assistant
Product Overview
Digital Worker Name: Dispatcher Assistant 1.O
Release Version: Q1 2026
Release Date: 1 May 2026
What's New
This release introduces the Dispatcher Assistant Digital Worker, a new autonomous worker designed to manage appointment disruptions and priority changes end‑to‑end with minimal dispatcher intervention.
It helps service teams respond faster to changing conditions by interpreting customer and system signals, identifying the best next actions, and driving resolution workflows across automated and human-assisted scenarios.
Human intervention is brought in only when policy, confidence thresholds, or operational constraints require it, ensuring the process remains controlled, traceable, and operationally efficient.
What’s new at a glance:
Customer Exception Parsing & Intent Detection interprets incoming customer and system-generated signals to identify appointment issues and required actions.
Slot Discovery & Optimization uses Planning & Scheduling Optimization (PSO) logic to identify suitable appointment alternatives while ensuring resource/skill availability and SLA adherence.
Appointment Renegotiation & Customer Communication supports multi-iteration customer negotiation through automated email communication.
Appointment Priority Change Management enables individual or bulk reprioritization of appointments in response to regional events such as weather disruptions or area-wide outages.
Dispatcher Support provides controlled human-in-the-loop escalation for approvals, overrides, and exception handling.
Built for bulk disruption scenarios with end-to-end auditability and traceable decision logs.
Changes in Product Offering
Release Scope & Constraints
This section outlines the supported operational scenarios, known limitations, and processing considerations for the Dispatcher Assistant Digital Worker in this release.
Supported Scenarios
The digital worker supports automated and human‑assisted handling of appointment disruptions with the following characteristics:
Known Limitations & Edge Cases
The following scenarios are either not supported or may require additional handling in this release:
Voice‑based customer negotiation
Advanced PSO simulations
Omni‑channel orchestration beyond email (for example, SMS or portal-native conversations)
Bulk exceptions may experience variable processing times in high‑volume situations.
Prerequisites
This section outlines the customer‑side prerequisites that must already be in place to successfully set up and use the Dispatcher Assistant Digital Worker.
These prerequisites are in addition to any configuration performed within IFS Loops.
Supported Versions
IFS Cloud Compatibility:
Version
Feature
26R1
25R2
25R1
24R2
24R1
Customer Exception Parsing & Intent Detection
Slot Discovery & Optimization
Appointment Renegotiation & Customer Communication
Appointment Priority Change Management
x
x
x
Dispatcher Support
Technical Prerequisites
To enable automated appointment disruption handling and human‑in‑the‑loop workflows, customers must have the following technical setup in place:
Email connector configured for outbound/inbound customer communication
Collaboration channel (e.g., Microsoft Teams) set up for HITL exception handling and dispatcher communication.
Appropriate IFS Cloud components and APIs assigned to the service user permission sets for that digital worker identity, including:
IFS Cloud Components & Permission Sets:
Component
API Name
SVCSCH
SvcschScheduleExceptionHandling
SVCSCH
SvcschAppointmentBookingHandling
REQMGT
RequestTaskHandling
SVCSCH
AppointmentService
IFS Cloud Basic Data Prerequisites
The following IFS Cloud master and transactional data must already be configured and maintained by the customer to support automated processing:
Service user configured with required company, site, and service organization access
Service resources and crews
Skills and competency definitions
Service‑level agreements (SLAs) and priority rules
Scheduling calendars, availability, and operational constraints
This data is required to enable effective slot discovery, PSO‑based optimization, and accurate exception resolution.
Last updated
Was this helpful?