> For the complete documentation index, see [llms.txt](https://kb.theloops.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.theloops.io/releasenotes/release-notes/digital-workers-release-notes/job-intake-manager.md).

# Job Intake Manager

{% updates format="full" %}
{% update date="2026-09-15" %}

## Product Overview

* **Digital Worker Name:** Job Intake Manager 1.0 
* **Release Version:** Q3 2026 
* **Release Date:** Sep 15th, 2026 

### **What's New**

This release introduces the Job Intake Manager Digital Worker, a new autonomous worker that converts incoming job emails into service requests in IFS Cloud. 

It extracts the job details, validates the customer, location, and equipment, resolves the appropriate service, and creates the request with relevant references, service notes, and attachments. 

**What’s new at a glance:** 

* **Automated Job Intake** extracts and processes service job information from incoming emails. 
* **Duplicate Request Detection** checks the customer's job reference before creating a new request. 
* **Customer & Asset Resolution** validates customer, location, address, and equipment information against IFS Cloud. 
* **Service & Organization Resolution** identifies the appropriate service and service organization for the requested work. 
* **Multi-Service Request Creation** creates a main request and adds additional scopes for distinct service needs. 
* **Job Information & Attachment Handling** carries relevant contact details, priorities, SLA commitments, service notes, and source attachments into the request. 
* **Exception Handling** reports unresolved or ambiguous information for human attention before unsafe request creation. 

### Changes in Product Offering

<details>

<summary><strong>New or Enhanced Functionality</strong></summary>

This release introduces the Job Intake Manager Digital Worker as a new capability in the IFS Loops ecosystem, automating the conversion of incoming job emails into validated service requests in IFS Cloud.

</details>

<details>

<summary><strong>Deprecated Functions</strong></summary>

Not applicable.

</details>

<details>

<summary><strong>Removed Functions</strong></summary>

Not applicable.

</details>

### Release Scope & Constraints&#x20;

This section outlines the supported job intake and service request creation scenarios for the Job Intake Manager Digital Worker.

**Supported Job Intake Management Scope**

The digital worker supports automated job intake with the following characteristics:

<details>

<summary><strong>Claim Intake &#x26; Processing Scope:</strong></summary>

* Processing of incoming job emails and relevant attachments
* Duplicate checking using the customer's job identifier
* Extraction of customer, location, equipment, contact, and service information and validation against IFS Cloud
* Resolution of equipment information where available

</details>

<details>

<summary><strong>Service Request Creation Scope:</strong></summary>

* Resolution of the appropriate service and service organization
* Creation of the main service request with the customer's job reference
* Addition of separate scopes for distinct service needs
* Inclusion of relevant priority, contact, SLA, and service-note information

</details>

<details>

<summary><strong>Document &#x26; Exception Scope:</strong></summary>

* Upload and association of the source attachments with the created request
* Reporting of unresolved or ambiguous information with available candidate matches
* Clear reporting of successful, failed, or partially completed processing

</details>

**Known Limitations & Edge Cases**

The following processing constraints and guardrails apply to this release: &#x20;

* A duplicate request identified using the customer's job reference is not created again.&#x20;
* Customer, location, address, service, and organization information must be resolved before request creation.&#x20;
* Unresolved or ambiguous required information prevents the affected request from being created.&#x20;
* Equipment information is optional unless specifically required for the request; unmatched equipment is reported as a warning where processing can continue.&#x20;
* Distinct service needs are added as separate scopes, while unrelated locations are handled as separate requests.&#x20;
* Attachments are uploaded only after a request has been successfully created.&#x20;
* If a later processing step fails, the Digital Worker reports what was completed and what still requires attention.&#x20;

In addition, Human-in-the-Loop (HITL) channels are used to communicate processing outcomes and exceptions. Where applicable, users are provided with a link to the relevant service request in IFS Cloud for further review or action.

### Prerequisites&#x20;

This section outlines the customer-side prerequisites required to set up and use the Job Intake Manager Digital Worker.&#x20;

These prerequisites are in addition to any configuration performed within IFS Loops.&#x20;

#### Supported Versions&#x20;

**IFS Cloud Compatibility:** &#x20;

<table data-header-hidden><thead><tr><th></th><th></th><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td rowspan="2"><strong>Feature</strong> </td><td colspan="6"><strong>Version</strong> </td></tr><tr><td>26R2 </td><td>26R1 </td><td>25R2 </td><td>25R1 </td><td>24R2 </td><td>24R1 </td></tr><tr><td>Automated Job Intake </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Duplicate Request Detection </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Customer &#x26; Asset Resolution </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Service &#x26; Organization Resolution </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Multi-Service Request Creation </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Job Information &#x26; Attachment Handling </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr><tr><td>Exception Handling </td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td><td><ul><li> </li></ul></td></tr></tbody></table>

&#x20;

**Technical Prerequisites**&#x20;

To enable automated Job Intake Management workflows, customers must have the following technical setup in place:&#x20;

* IFS Cloud integration configured for customer, service request, service, and document processing.&#x20;
* Email integration configured for incoming job email and attachment intake.&#x20;
* Appropriate IFS Cloud components and APIs assigned to the service user permission sets for the Digital Worker identity, including:&#x20;

**IFS Cloud Components & Permission Sets:** &#x20;

| **Component** | **API Name**                             |
| ------------- | ---------------------------------------- |
| ENTERP        | CustomerHandling.svc                     |
| REQMGT        | RequestHandling.svc                      |
| REQMGT        | RequestServices.svc                      |
| DOCMAN        | DocReferenceObjectAttachmentHandling.svc |
| ENTERP        | GetPartyTypeWidgetInfo.svc               |
| REQMGT        | ServiceNotesAssistantHandling.svc        |
| SRVBAS        | ServiceOrganizationHandling.svc          |
| SERCAT        | SrvOrgDlvryUnitRuleHandling.svc          |

&#x20;

**IFS Cloud Basic Data Prerequisites**&#x20;

The following IFS Cloud master and transactional data must already be configured and maintained by the customer to support automated processing:&#x20;

The following basic data must be configured in IFS Cloud:&#x20;

* Customer & Location Data including customer records with applicable locations and addresses.&#x20;
* Equipment Data including relevant equipment and model information where required for job processing.&#x20;
* Services & Organizations including configured services and service organizations available for request creation.&#x20;
* Service Request Configuration including applicable priorities, contacts, SLA settings, and other required request information.&#x20;
  {% endupdate %}
  {% endupdates %}