SoftTech AI Registry
UiPath · UiPath Agents

LLM-Inferred Escalation Recipient Selection

An agent escalation can use the LLM inferred assignment criterion. The developer provides instructions describing who should receive an escalation; at runtime the agent determines recipient(s) based on case context, after which the inferred assignee(s) are validated against the organisation's directory. If no valid recipient can be determined, the Action is created unassigned.

Recorded characteristics

Function
Smallest controlled object: one escalation → one inferred human recipient or recipient set. Not workforce management, staffing optimisation, organisational resource allocation, workforce planning or human decision-making. Authority chain: runtime case/agent context → LLM/agent inference → inferred human recipient(s) → directory validation → Action Center assignment → selected recipient receives the assigned Action. UiPath states escalations are powered by Action apps in Action Center and provide human-in-the-loop events during agent execution, and documents the Assignment criterion "LLM inferred: Lets the agent determine the recipient(s) at runtime." and "Use this option when the right recipient depends on the context of each case." Model-owned decision: contextual derivation of the human recipient(s). Execution system owns: validation and the resulting Action Center assignment. Selected human owns: any subsequent judgment, approval, rejection or business decision; that later authority is not transferred to the model. Analytical classification: Category 2 — model-derived consequential recipient choice + automatic assignment without evidenced per-assignment human confirmation. Consequence: "As soon as an Action is assigned to a user, it moves from the Unassigned tab to the Pending tab of the assigned user." Failure behaviour (only behaviour recorded): if no valid recipient can be determined, the Action is created unassigned ("rather than sent to the wrong person").
Data access
Runtime case/agent context of the escalation, interpreted against developer-written instructions describing who should receive the escalation; inferred assignee(s) are validated against the organisation's directory. The candidate recipient universe exposed to inference is not publicly established.
Actions
Can take actions
External actions
No
Human confirmation
Not required
Permission basis
Not established
Administrative control
Constraint boundary: developer routing instructions (the prompt describing who should receive the escalation) constrain the inference; directory validation occurs after recipient inference and is treated as a constraint/validation layer, not an independently established recipient-selection mechanism; exact validation mechanics are not publicly established. The model is not recorded as having unrestricted choice across the organisation. Action Center uses folder-based access controls; Actions are created within the relevant folder context and access depends on folder membership, roles and permissions. Assigning an Action to another user requires the applicable Action Assignment permission, and reassignment is also permission controlled. Deterministic alternatives are documented separately (User/fixed recipient, Workload, All users in group, Round Robin, directly supplied email/group routing, input binding); for guaranteed routing UiPath directs developers to fixed recipient or input binding. Human confirmation not_required applies ONLY to approval of each individual model-derived recipient before assignment; humans still configure the escalation, choose LLM inferred, provide routing instructions, configure the surrounding agent and subsequently resolve the escalation. The overall system is not described as human-free. Outside action no (controlled classification for this record only): the assignment is executed through Action Center as part of UiPath's documented agent-escalation mechanism; crossing from UiPath Agents into Action Center does not by itself constitute action outside the immediate service boundary. Permission basis not_established: Action Center/Orchestrator access controls exist, but the exact runtime principal exercising the inferred assignment has not been established. Default state not_established: developer configuration of LLM-inferred assignment does not establish a default state. Reversibility: Pending Actions can subsequently be administratively reassigned. Reassignment is a later assignment operation and does not mean the original model-derived assignment never occurred. UiPath describes reassignment as unassigning the Action from the previous user and assigning it to the newly selected user. Completed-escalation reversibility is not publicly established. Auditability: Action Center provides operational Action audit trails through Orchestrator (audit logs centralised in the corresponding Orchestrator tenant, filterable to the Actions component). Model-specific recipient-decision explainability is not publicly established; no claim is made that audit logs expose model reasoning, candidate recipients, raw model output, inference prompt, directory-validation result or model version.
Default state
Not established
Availability
UiPath Agents — Automation Cloud: "New assignment criteria options are now available for agent escalations" (release notes, 24 July 2026), listing Workload, All users in group, Round Robin and LLM inferred; no Preview/Beta qualification identified for this functionality in the controlled evidence. Automation Cloud Dedicated / Test Cloud Dedicated: the same assignment options were added on 21 August 2026 (supporting deployment evidence only). Production parity across every UiPath deployment model and region is not established.
Licensing
Not publicly established.
External model or provider
Not publicly established (exact LLM/model used for recipient inference unknown).
Limitations and uncertainty
Monitoring deliberately deferred: no monitor created for this record; robots.txt, terms and automated retrieval were not tested. Category 2 recorded in narrative only. EXCLUSIONS: recipient's subsequent judgment; recipient's approval or rejection; underlying business decision; subsequent workflow outcome; workforce optimisation; staffing optimisation; workforce planning; generic task creation; fixed-recipient assignment; round-robin assignment; workload-based assignment; all-users-in-group assignment; directly supplied email/group routing; generic Action Center assignment; Maestro routing; MCP execution; sub-agent delegation; downstream agent actions; model-owned organisational staffing decisions; unrestricted employee selection. NOT PUBLICLY ESTABLISHED: (1) exact LLM/model used for recipient inference; (2) exact internal model output representation; (3) whether identity, email, username or another identifier is emitted; (4) candidate recipient universe exposed to inference; (5) whether candidates are ranked; (6) ranking/scoring mechanism; (7) exact runtime inference prompt assembled by UiPath; (8) exact directory-validation algorithm; (9) whether validation performs only verification or additional identity resolution; (10) multiple-match/tie behaviour; (11) partial failure with several inferred recipients; (12) fallback for directory outage; (13) unavailable/deactivated recipient behaviour; (14) exact runtime permission principal used to create/assign the Action; (15) whether the agent has an independently represented identity for this operation; (16) exact maximum inferred recipient count; (17) bulk-escalation behaviour; (18) whether per-assignment model reasoning is exposed to customers; (19) whether directory-validation results are logged; (20) exact model/version recorded for a historical assignment; (21) model versioning behaviour; (22) retraining/learning behaviour relevant to recipient selection; (23) online adaptation; (24) production parity across all UiPath deployment models/regions; (25) completed-escalation reversibility. Unknown means unknown.

Evidence