Introducing Remote Desktop

With Remote Desktop support, Pallet Agents can now execute workflows inside applications delivered through Citrix, Microsoft Remote Desktop, VMware Horizon, and other virtual desktop environments, without requiring APIs or custom integrations.

Your AI is only as useful as the systems it can reach

Every supply chain depends on a mix of WMSs, TMSs, ERPs, and homegrown applications that have evolved alongside the business.

Pallet already connects to modern enterprise systems through APIs, EDIs, and other integrations, as well as legacy infrastructure through our native AS/400 support. But another major category of enterprise software has historically remained difficult for AI to reach: desktop applications accessible only through remote environments such as Citrix, Microsoft Remote Desktop (RDP), or VMware Horizon.

The challenge is not simply that these systems are old. Many do not expose reliable API endpoints for the information that needs to be read or updated. And unlike browser-based applications that software can access through a URL, these applications run inside a remote desktop session.

Imagine if Gmail could only be opened through a desktop application on a remote computer rather than through a browser. Software could not simply navigate to a URL or call an API. It would first need to enter the remote environment, open the application, and operate the interface the same way a person would.

Because of these limitations, IT teams have often assumed that workflows inside remote desktop applications would always require manual work.

That assumption is no longer true.

Pallet Agents can now work inside Remote Desktop applications

Pallet Agents can now securely enter Citrix, Microsoft RDP, VMware Horizon, and other virtual desktop environments and operate the applications inside them just as an operator would.

Agents can log in, open applications, navigate interfaces, read information, update records, submit transactions, and verify that each action was completed successfully before continuing the workflow.

Rather than requiring customers to rebuild their systems, expose new APIs, or develop custom integrations, Pallet Agents can work through the existing application interface.

This follows a principle that has guided how we build Pallet: businesses should not have to change the systems they rely on before they can deploy AI. Agents should be able to work across the infrastructure that already runs the business, whether that means connecting through an API, accessing AS/400, or operating an application through Remote Desktop.

Workflows that were previously inaccessible because they lived inside Citrix or another virtual desktop environment can now be completed without replacing the underlying software.

From email to on-prem systems of record, without human handoffs

Many enterprise workflows begin in one system and end in another.

A request may arrive through email, require information from a PDF, and ultimately need to be entered into a WMS that is accessible only through a remote desktop session. Historically, a person had to bridge those systems manually.

Pallet Agents can now execute the full workflow from beginning to end. Whether the work happens through an API, EDI connection, browser, AS/400 terminal, Citrix session, or Windows desktop application, the agent can move between environments and complete the necessary actions.

Many supply chain teams rely on applications such as Blue Yonder, Infor WMS, Manhattan SCALE, Synapse, and other enterprise systems that are often accessed through virtual desktop environments. With Remote Desktop support, Pallet Agents can securely work inside these applications through the same interfaces operators already use.

Examples include:

• Receiving validation: Review receipt records, notes, and discrepancies in Synapse, close routine cases, and escalate exceptions.
• Outbound wave creation: Read customer shipping requests from email, apply customer-specific rules, and create outbound waves directly in the WMS.
• Routing: Read a PDF manifest, identify the customer, and submit the pickup or routing request through the customer's portal.
• Appointment scheduling: Validate order, weight, timing, and pickup details, then schedule the appointment directly inside the WMS.

Agents handle repetitive, high-volume work from beginning to end while escalating ambiguous requests, unfamiliar interfaces, or new exceptions to operators. Teams can stay focused on judgment and exception handling instead of moving information between applications.

Remote Desktop is no longer a barrier to AI

For years, applications accessible only through remote desktop environments marked the end of the automation journey.

With Remote Desktop support, Pallet Agents can now complete workflows across APIs, AS/400, Citrix, Microsoft RDP, VMware Horizon, and Windows desktop applications.

See the Remote Desktop support in action today.