What is our primary use case?
AssistEdge was a twofold product consisting of standard RPA and desktop automation. We were using it to develop a custom UI for our contact center with built-in automation to make the reps more efficient. However, it wasn't netting the returns we wanted.
What is most valuable?
AssistEdge made it so that the reps didn't need to maneuver through 10 or 20 different systems. We tied all that together in the background, so the reps had a shared UI, and everything else happened in the background without their knowledge. When they were retrieving data, it was done in the background through automation and pulling up to that generic UI layer
My former company had no shortage of legacy systems. AssistEdge went into those legacy systems, performed those functions, and brought the output back to the rep in a simple UI layer.
What needs improvement?
Implementing new automations could be more seamless. It was challenging to build within, so we were highly dependent on Infosys developers. They had us over a barrel with that.
AssistEdge isn't a simple tool like Blue Prism or other RPA solutions with configurable items that you can drag and drop. This involved a lot of hard coding, which posed two challenges. One, we did not have that skillset, so we depended on Infosys. Two, it's a beast to go back and update or make changes when things are hard coded because you can't just move those configurable items back around.
For how long have I used the solution?
AssistEdge was in place when I started my role at my last company. We used it for about a year and a half before moving to a tool that had applicability and usage beyond one vendor.
What do I think about the stability of the solution?
Stability was not necessarily an issue. I can call it stability, but I don't think that's what it was. We had so many systems and legacy systems that we were touching, and those were constantly being changed. It wasn't the product's stability so much as interdepartmental communication. Other changes to those legacy systems weren't communicated and the automations would suddenly break.
What do I think about the scalability of the solution?
AssistEdge is easily scalable, but the cost at the time was prohibitive because it was a per user license. For instance, we were getting ready to outsource some of our customer service work to a third-party vendor when I left. Infosys and our vendor partner didn't allow us leeway there, so we had to purchase licenses for our onshore reps and source partner reps during the transition, which was not fiscally sound.
How are customer service and support?
I rate EdgeVerve support eight out of 10. Their team was great, but they were hamstrung by the amount of money we were willing to pay them.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
My previous employer was interested in AssistEdge because it was an Infosys product, so they could get it customized how they wanted. At the same time, Blue Prism and UiPath also work like this. In the end, they were limited in their capabilities because AssistEdge wasn't a widely used tool across the industry.
How was the initial setup?
It took almost a year to initially deploy the custom UI we wanted them to build. I inherited that program when they were about eight months into that build. I inherited it because it was taking too long. The cost was ballooning as they were trying to build that out. Finally, they decided there was no way we would ever get ROI we hoped.
What's my experience with pricing, setup cost, and licensing?
It might be affordable or exorbitant, depending on the use case. We were deploying to a contact center with about 8,000 representatives, so ours was extremely expensive because it was a per user license.
What other advice do I have?
I rate EdgeVerve AssistEdge six out of 10. My only advice is to do your research and think about how you plan to use the tool long term. If you want to scale up, pick a tool that can be scaled. You might want to pick a tool that's more configurable rather than a solution that's hard-coded. A large company will require some changes to all those subsystems every day.
When you hard code something, you are setting yourself up to feel that in the long run. You will be constantly chasing your tail with tech debt and trying to update things instead of implementing new automations. We implemented our first set of automations with the rollout and felt like we were constantly playing catch-up to change automations we had already built to work with our systems that were also changing instead of implementing new automations.