What is our primary use case?
I work in an automation Center of Excellence in health care, and I utilize it for everything and anything that is appropriate in health care. We have approximately 41,000 hours worth of automation that operates and handles tasks ranging from assisting with HR operations, such as leave of absence, to medication monitoring and much more. Our portfolio is quite expanded.
We are also jumping into the Co-Pilot world because we want to start embedding it into Teams, SailPoint, and some of the other tools.
We are also looking at a unique use case. We have discharges, and there are certain types of prescriptions that are just extremely specialized as part of discharge. We have medication contracts. One of the things that we have going on in our organization is a buddy system and then an official request. The buddy system is essentially prescription denial appeals. We would like to use AI to search our contracts to figure out what is the standard for these medications and what are the denials and appeals that we can have prewritten and ready to go.
How has it helped my organization?
It was a response to COVID that prompted us to dive into scalable tools. We needed scalability and the ability to perform 10,000 or 1,000 or 200 tasks at any moment. No other software that we have had could provide such scalability and is built in a modular way.
It is unique and almost invisible. You do not realize its impact until you discuss it with users who provide positive feedback. We build automation, support it, and deploy it. When we meet with our users later, they have such good feedback about how impactful these things are to their path. For a nurse, not having to repeat a task 10,000 times has made a significant difference. Especially during COVID, it was truly helpful on the front line. Now, I also employ it with other powerful medication tools.
I was personally able to see its benefits as soon as I jumped into software. It was one of the most impactful and amazing tools for my day-to-day life because, at any point in time, I could design something, modularly build it, and deploy it. It can handle such amazing tasks, including things like templates and design and all other materials that we have for communications or activities, and produce them for me automatically. For me, personally, it made a huge impact right from the get-go, but as an organization, we definitely had to learn how to make choices on our use cases.
It has absolutely saved us time and costs. The whole point of the software is to develop something that at least on a use case basis provides value. We have many years of learning how to do our program. Over time, we have also been using it for other things, such as compliance. We have definitely evolved from just saving time or money to using this solution for everything we can use it for.
What is most valuable?
I have just built my first Co-Pilot, and it is significant in how that part functions. I am also exploring the API task tools, which appear to be quite significant, but for the most part, the forms and the capability to integrate data from other software represent the specialty.
What needs improvement?
One thing I learned with Co-Pilot is that it is very static. For instance, when dealing with tables and their headers, I must program them in a form. If my build changes, I have to return to my form and update the table titles. Features like looping are missing from Co-Pilot. If I want to perform a task five times in a row, I have to rerun Co-Pilot five times just to achieve that. This is an aspect I considered as I explored possible changes and improvements. Other than that, it is among the best software tools and organizations I have worked with. I find it challenging to suggest much beyond continuing the good work and expanding on it.
For how long have I used the solution?
I first heard about it back in 2021. This will be my fourth year using it.
What do I think about the stability of the solution?
I had an issue lasting for the better part of three years, and it was quite severe. I never lodged a ticket because whenever we attempted to resolve it internally, the problem temporarily ceased. Each time I ran my Digital Colleagues, I encountered a strange error on my screen, which persisted for a couple of years. However, an update corrected it, and it is no longer an issue.
The only current challenge involves a discrepancy in table columns. In my support session, we could not figure out why my table was off by one column. I had to have a blank column zero for my table to align correctly. These minor issues aside, the tool now functions more stably.
Previously, inconsistent search behavior occurred in the ServiceNow search bar. It was puzzling because it worked differently every single time that we searched in that search bar, but that issue has been resolved.
What do I think about the scalability of the solution?
Scalability is the most remarkable feature of this tool for me. For example, we have a recognition system for automation. I designed a template for various achievements by citizen developers, such as completing a class or build. At first, it was not a big deal to just do it yourself because you are only doing a handful of templates, but the last round had 34. Initially, creating a few templates was manageable. With time, however, it escalated from 5 templates to 34. We are now using this tool multiple times weekly for template generation. Eventually, I aim to release it to the entire automation team so that leaders can readily recognize achievements based on team activities.
Scalability is impressive; whether handling five or a hundred million templates, it remains easy to design and build. The tool's intuitive nature contrasts with other tools, which are less intuitive for building and scaling, explaining my infrequent use of them.
How are customer service and support?
I have contacted their support for technical issues with the software as well as personal build support.
The response is very quick. Within a couple of days, they are communicating and establishing connections to set up solutions. In my case, I meet with my customer relations every Friday. We get prompt responses to any issues I raise. The support is fantastic, even when dealing with complex situations due to the complexity of some of my builds. While not all problems are solved immediately, this is typical for complex tasks.
I very recently had one of the best support help sessions that anyone could have ever asked for. We were doing something really complex in Co-Pilot, and it was something that was completely unique to even our internal development team. They helped me solve that, and they did it in such a great way. It was a ten out of ten for connecting to someone, taking the time, and doing all of the work. However, we have also had some support tickets in the past that have been just okay. It has been a mixed bag on that front. I would rate them an eight out of ten because they do try hard to connect and support us even though we are doing some complex work.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
This predates my time, so I am not fully sure. I do know Microsoft automations were used before transitioning to Automation Anywhere. Selecting a vendor was a part of the process when we started the program, and Automation Anywhere was chosen.
How was the initial setup?
The decision for the software had already been made. I was only involved in meetings to discuss how we were going to deploy programs, design things, and create standards.
I believe it took six months from deciding to go live with the software to deploying automations. It did not exceed six months to get everything up and running, though there might have been a year of planning. Once I was set for launch with everything in place, the transition from purchased to used tenants happened swiftly, possibly in less than six months.
What about the implementation team?
Initially, I used strategic resourcing for implementation. At the time, I had an engineer, a technical lead, a technical developer, and an architect—four individuals in total—who implemented all my environments. Four environments were set up, following designs, standards, and rules. This setup involved comprehensive program design, focusing on transitioning and using different control rooms and establishing standards.
We support the entire tool, and we support the automations which require lots of maintenance and support. That is only due to user design or systems changes or some of the elements that are out there. We have a whole support program that goes along with our automations. As for the tool itself, it is just like any other software tool. It is certainly more stable than something like Microsoft where you constantly have to go back and correct issues or incidents. Our incidents are with bots, not with the software.
What other advice do I have?
My job involves citizen development. I work in the field of helping people connect to this technology and use it. In terms of ease of use, the software is not hard to use, but things are presented to users in a new way than what they are used to. I had to make people start with basic programs and learn how to do a simple process. It is a little bit of an advanced tool. It is easy to understand for me and I love it, but it is definitely a step above entry. Before I instituted an entry course, the learning curve was a little bit steeper. We would have individuals coming to our four-day course and then come through and do lots of support. When we taught them the basics of how the automation software works and then brought them into this advanced tool, it was very quick for them. Our results were much better, and we have those individuals building regularly.
In terms of integration, what was interesting to learn was that everything requires a configuration. For an organization like ours, it involved figuring out how we should branch, how we should grow, and how we should engage other teams to get those configurations implemented so that packages will work as intended. That was an interesting learning curve for us. We had to adjust how we train, talk about packages, and use the software to make sure that we had the right integrations and setups. A great example is ServiceNow. They have the packages for ServiceNow built in. If you have all the access to the information and all the things you need, you are in good shape to have some really awesome automation. If one of those pieces is not in place, you have to think a little bit about how you are going to access that.
Automation Anywhere is a ten out of ten. The company is impressive, especially with its new initiatives like Agentic AI. In five years, it is going to be amazing to witness their advancements, particularly as AI continues to play a significant role.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.