Attended automation is the deployment model in which an automation bot runs on a finance team member’s own computer, triggered by the user and operating alongside them, assisting with specific repetitive steps within a process that the human continues to lead. The bot handles the mechanical, rule-based portions — opening applications, extracting data, populating fields, running lookups — while the user applies judgment at the decision points that require contextual understanding. Attended automation is not a lesser form of automation because a human is present; it is the appropriate design choice for processes where human oversight adds genuine value at specific steps and where full automation would either be inappropriate or require automation of exception handling complexity that does not justify the cost.
Why This Matters for Finance Leaders in Egypt and the GCC
Attended automation is well-suited to finance processes in GCC and Egyptian enterprises where regulatory requirements or internal control frameworks mandate human review of specific actions — for example, a payment approval that must be reviewed by a finance manager before the payment is released, or a journal entry that requires a controller’s confirmation before posting. In these cases, attended automation handles the data gathering, population, and system navigation steps, while the human reviewer applies the oversight required by the control framework. The automation increases the speed and accuracy of the steps the human does not need to review, without removing the human from the steps that internal controls or regulatory requirements require them to perform.
What Good Looks Like
Effective attended automation design identifies precisely which steps the bot handles and which the human handles — with a clear handover protocol between the two. The bot should not be doing work that could be done in the background without the user present (that is unattended automation’s role), nor should it be automating steps that the user needs to see and review to perform their oversight function. Good attended automation feels to the user like having an assistant who handles the mechanical steps automatically, freeing them to focus on the judgment-dependent parts of the process. The measure of success is user adoption rate: if the user defaults to doing the manual process rather than triggering the bot, the automation is not providing sufficient value to justify the change in working habit.
What Sponsors Get Wrong
The specific failure that most reliably produces low attended automation adoption is designing the bot around the process as it appears in the procedure manual rather than around the process as the user actually performs it. When the attended automation assumes the user opens applications in a specific sequence, has specific data available at the moment of trigger, and works from a single screen, but the actual user opens applications in a different order, needs to cross-reference several systems before triggering the bot, and works across two monitors — the automation does not fit the user’s real workflow. The user abandons it because it is harder to use than the manual process it was supposed to replace. Attended automation design must be co-designed with the actual users, not designed by process analysts who have observed the process from a meeting room.
How Loop Wise Solutions Approaches This
In attended automation engagements, we conduct working sessions with the actual users who will use the bot before we write a single line of automation — observing the real process, understanding where the friction points are, and designing the bot around the user’s actual workflow rather than the documented workflow. User acceptance of the attended automation design is a go/no-go criterion before development begins. An attended automation that users are not committed to using before it is built will not be used after it is deployed.
