View source for Deciding between an unattended or attended robot

Deciding between an unattended or attended robot / ← Unattended vs. Attended robots: Which robot to use?

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in one of the groups: Users, editor, pegaemployee.
• The action you have requested is limited to users in one of the groups: pegaemployee, editor, Administrators.

---

You can view and copy the source of this page.

=== Rethinking work flows to minimize any negative impact to the attended user === Consider the following points to streamline workflows: * Navigate applications to screens that may be needed as the call begins. For example, search for customer in all applications at the beginning of the call, even if you do not know that the application will be needed during the call. * Avoid one monolithic attended automation that takes too long. Separate it into multiple automations that are invoked from various steps within the Pega application. Here is an example: ** Automation 1: Open the application and navigate to the customer information at the start of the call. ** Automation 2: Retrieve the current customer information available for user to see as the Runtime user determines why the customer has called. ** Automation 3: Update the legacy applications with data received from the customer. * If user input is required during the attended automation, it should be entered through a user interface in the Pega application and not through data entry forms created using Robot Studio or the applications being automated. By returning control to the Pega application, the timing for the data entry does not fall under the 60-second maximum.

Return to Unattended vs. Attended robots: Which robot to use?.