We are using this product to develop automation in the billing section of our website. We are integrating bots so that they can do the basic listing and then our salesperson can take it from there.

The biggest improvement has been in cost. We have been operating it for about eight months for about $8,000. Earlier, it was taking us somewhere around $30,000 to $40,000, so that is a big improvement.

The other part has been accuracy. Before, when we had employees for the same process, there were some minor errors, as well as some time issues. But with this system, I believe the accuracy has been at par, although there are several times when we have had to reframe or do some minor modifications in the AI to make the model work for a new set or variety of clients.

The reduction in human error means we get more leads into the hands of the right salespeople who can work on them. Fewer errors means time savings.

With time, the AI automation has improved. Specifically talking about the kind of business that we do, which is putting things into the right sections so that the right people are taking the right leads, even in some complex cases, we have seen accurate results from automation. AI is doing its job.

AI has also enabled us to automate more processes. Earlier, we had different sets of protocols for differentiating among the different kinds of inbound information we were receiving. Since deploying this automation, we have automated a large chunk of the reception. The accuracy has been maintained and the time has been reduced significantly. We are able to convert the leads in a way that gives us more to work with from the leads we get.

The automation-creation process is quite easy and the accuracy is quite good. That last aspect is critically important because we have used RPA to replace one of our employees and we are taking on a lot of responsibility. The most important thing that we require is accuracy and we have been getting that so far.

The end-to-end coverage is important because each and every part of the input we are receiving from our customers—and they're highly valued customers—is information that goes into our software via automation, and we do not want to miss out on any types of leads.

The UiPath Academy courses have been great at giving an overview of the solution and allowing employees to learn things at their own pace. Other users out there also helped our technical staff, so they have added value. The biggest benefit was that at the time our technical staff was getting used to the product, they felt that there was a scarcity of people who knew about how to execute things. Having this UiPath course was a little helpful because it gave them the initial confidence they needed to start doing things, whether it was right or wrong, and they kept getting feedback and improving.

The only concern is it's a bit tough to understand the first time, and you have to invest in the technical improvement of your team in general.

About 6 Months.

There's no need to worry about the stability.

The only concern is as we move towards scaling it. What happens if the system goes off? Although it's not a big concern, we have been getting reassurance from UiPath that they have a solid backup of everything.

With RPA, scaling is not an issue at all. Once a bot has been trained to do a specific thing using ML, multiple bots can be added for the same automation process, as many times as we want. Scaling is not a concern.

We have not used technical support.

Positive

In terms of our decision to go ahead with this product, although we had received a recommendation that we should be moving forward with it, we were severely concerned about whether doing things over and over would take us the same amount of time, in terms of the technical ability and the workforce, or whether it would be easier. After having a technical call with UiPath, we quickly knew that it would be easier. That was a crucial part of our decision.

The initial setup was easy, but making the AI understand, and using the machine learning algorithms in it, took a long time. It took more than we expected it would take. The UiPath team had us understand that it would be functional after one or two months, but it eventually ended up taking about four months. That was more time than we expected, but the initial setup was easy and straightforward.

We used a consulting firm. There were three meetings over the duration of the two-month contract. The advices we received we about our model selection with regards to pricing and data storage capability.

We have been using it for eight months. For the first four months, I do not believe we were saving time because we had to intervene a lot of times with help from the vendor as well. But from that moment onwards, once the integration was operating smoothly, we started saving time.

We do a regular analysis each month and we have been seeing constant growth. A month is a good amount of time to see the progress of a newly implemented solution.

Previously, we were not using automation operations. I believe we have now reduced costs significantly, which justifies the cost we are paying for the service.

Pricing is good if your venture is looking for growth in 1-10 million size of customer domain.

yeah we got in touch with the IBM team for their automation tool.

Building automation takes some time. The first time, it took us a month, but after that, it was easier. The next time we build an automation, it's a kind of reciprocal of what we did the previous time. The first time involved some help from other resources, but from that time and onwards it has been going well.

The innovation did not happen as fast as we thought it would for the first half. We had to recruit some IT guys to our technical team so that our entire team could become familiar with the process. The innovation potential is there. It helps to get very familiarized with the solution. But for the first few months, the innovation part was delayed. The technical level required to handle it smoothly was not there on our team.