Moveworks

I have been using Moveworks for over two months now, and it is not a registered version; it is just a test version that I am using. I am preparing to register officially for it now.

Based on my usage of Moveworks, it functions as a work tool to automate work automations. Work tools such as email replies through Outlook and some other applications found in the workplace can be brought together and synchronized. That is what I have been using it for. I have never explored it very deeply, so that is what I have been using it for currently.

We have tested Moveworks for just a small task, and it is Outlook email replies. That is what we are currently testing it with. The testing is still in progress and we have not finished entirely. I thought if I register for it fully for the demo, I will be able to get the full version usage of it. What I am using it for currently is the automatic email reply, which is my target.

I actually need some support with Moveworks, as I might need support from the configuration part of the automatic email reply. I still want to go further with my Teams and team schedule processes. If I want to schedule a meeting and I already have a meeting scheduled somewhere, maybe from my emails and calendar that is not synchronized with my Teams, I want something that will automatically alert me that a meeting has already been scheduled for that particular period. I need some support or tutoring on this. I believe that by the time I install it fully, I will be able to get all the configuration perfectly. For now, what I have been using it for is majorly Outlook email replies.

As I mentioned, the integration part of Moveworks is still what I am learning more about, but the synchronization with our Outlook has been very great from what I have seen. It is still not perfect enough, but we are working on it to make sure it is very perfect. Working with Outlook currently has been going on. I am thinking of synchronizing every other application, such as my day-to-day applications including Microsoft Teams, Office, and Outlook, and some other applications such as ERP applications I am using. The synchronization that we have done on the Outlook part is going on fine. I think by the time we put everything together, it should be very great. The synchronization of it should be very okay from what I have seen for now.

In terms of the security part of Moveworks, I would not want to give much weight to the security part for something I have never explored much. In terms of governance and security, I believe Moveworks is an AI application which has general governance for every AI around the world. I believe they are following it, and from what I have seen in it, I do not think leaking of information or data has been observed from my own testing. I believe they are following the general rules for the AI capability and data governance found all over the world. For now, I can give them a very good grade on this as I have never seen anything leak.

Moveworks is currently deployed in a public cloud for me. It is still a local testing situation for me only for now. By virtue of my position, until everything is perfected, that is when I can introduce it to my teams. It is still a cloud local base testing for my own use only.

I have never explored every option of Moveworks currently. However, for what I have looked at, the synchronization of all the apps in the workplace is one of the greatest things that everybody is facing in the workplace these days. Forgetting to reply to a certain email or forgetting to reply to a certain message, maybe from WhatsApp or from Teams, is common. Bringing Moveworks into this particular perspective will automate a lot of work and it will make it much more seamless and will make the workplace much more enjoyable and will improve the efficiency of the work. What I would take majorly from this is the synchronization of all workplace applications and making it much more seamless and much more useful to use even when I am not even there. That is one of the features I see in it that is very great.

Moveworks has impacted my organization positively so far, even in this testing phase. One small benefit I can mention is that when I am not even in the office and an email has been sent to me, I have the opportunity of sending a basic reply back to the sender. It makes my work available twenty-four hours. Apart from that, it reduces certain tasks away from me. Tasks that I would have to sit down and do before are now much easier for me to do.

Moveworks has reduced many tasks from us. For example, some emails that I have to reply to can take ten to fifteen minutes to compose. Within two minutes, these things are getting done and sometimes I might not even be there before it is getting replied. These are part of what we are trying to accomplish and it saves a lot of time on this. An average of one to two hours per day is being saved successfully from using this.

The features of Moveworks that I have not fully explored include some features I would actually like. Fully automating the passing of entries and automating entries generation would be valuable. For example, if I have a finance staff that is continuously passing an entry for me, I want a situation whereby it can pass that entry automatically and post it based on the synchronization and command which I have configured. I believe some other bot applications are doing something similar. If all these work tools can be put together to automate this kind of process, it will be very great.

Major things I would want Moveworks to do more of - I do not know whether this functionality is already there - I want it to perform the work of bots so I can quickly automate some other applications to it, such as passing some entries. That is one request. Secondly, regarding the integrations of bots of Moveworks with other applications, I would appreciate if there were a step-by-step process for all standardized applications such as WhatsApp, Outlook, Microsoft Office, Microsoft Teams, and some TeamViewer and other applications that are work tools. The step-by-step synchronization and integrations of these things, if it can be posted on the website, would make it much easier for people who want to do the synchronization instead of doing a lot of research before it gets done.

I have been working in my current field for about ten years now.

Moveworks has been dependable in terms of accuracy and reliability of output. Although there is a need for improvement, it has been dependable.

The particular part of Moveworks's scalability has not been noticed by me. I am just working on the workability capability for now, not scalability. Capability is what it can actually achieve for me, not putting much more workload on it now. By the time I put much workload on it, I can actually talk about the scalability, but in terms of capability, which is what I am actually working on for now, I think it is doing fine.

I have not yet reached out to Moveworks customer support and have never contacted them.

I did previously use a different solution for automation of email replies. I can tell you that we have never even switched. This is just a test and I am just testing this now. What we were using before, we are using Meta AI with cloud. That is what we were using it with and this replies our WhatsApp automatically by the time we are not on seat or we are not available at that particular moment. It replies the WhatsApp chat with information which they need based on what we have already programmed it to do. That is what we have been using. It was not even deployed on email; it was on WhatsApp that we actually deployed it. There is another one which is a bot, which I have mentioned in the process of talking to you, which we use for the implementation of little tasks, such as passing entries. We have used that also in a while. By training the model on this, I know what I have to be doing. Training that model for a certain period of time on a certain task, we have been able to achieve certain things with it, but I am not still totally convinced, which is why I am trying to do my demo run from every available application that I have so I can now choose the one that I want later. That is the reason.

I have seen a return on investment so far with Moveworks. Two hours of work are being saved per day. Because there are emails, if for example I am replying to twenty mails in a day and spending maybe twenty minutes on it, we have saved not less than two hours on this small one that we have tested currently. I believe that by the time we go fully into it, we should be able to save more time. Currently, an average of two hours per day is being saved on this.

I have not yet reviewed the pricing, setup cost, and licensing for Moveworks. By the time I review it, I will be able to give updates on this.

I evaluated other options before choosing Moveworks, and I can say Moveworks is stable in my experience so far.

Moveworks serves my organization primarily through its integration with Teams and other platforms like ServiceNow. A specific example of how I have used Moveworks with Teams and ServiceNow is that we created forms to be used in ServiceNow, and with the integration, it pulls those forms into Teams chat, allowing people to fill them out directly without needing to access ServiceNow.

Moveworks has positively impacted our organization by lowering ServiceNow service desk calls by 90%, as users now prefer to ask questions through Moveworks in Teams before calling for help.

This reduction in service desk calls has effectively focused our team's workload on more significant issues that require direct assistance instead of general inquiries that Moveworks can handle.

Moveworks has delivered high return on investment, as many issues are resolved through Teams chat without needing calls, alleviating traffic on our ServiceNow instance.

Moveworks offers several best features, including Teams integration, inbuilt AI assistance, and easy integration with other platforms through plugins.

The feature I rely on the most is the conversational Paths in Moveworks, which allow us to interact with users by pulling details from them to create catalog item requests in ServiceNow.

Additionally, I am using Events in Moveworks for notifications about changes in request statuses, such as when new requests are opened, closed, or comments are made.

Improvements needed for Moveworks include addressing limitations in Paths, such as the inability to utilize more than twenty conversations and the ingestion of forms that have client scripts or dynamic elements.

Regarding Moveworks's AI capabilities, I have not seen any breaches in security, which is positive, but regular audits should be conducted to ensure proper usage.

In terms of accuracy and reliability, I have found Moveworks to be reliable, scoring around eighty to ninety percent, but not one hundred percent, as artificial intelligence is not perfect.

I have been using Moveworks for the last two years since we started in 2024.

Moveworks has been stable, with downtime occurring only two or three times in the last two years.

Moveworks has handled increased usage well, demonstrating significant scalability.

Customer support has been adequate; I would rate it around seven out of ten, as support often forwards cases to developers after collecting details.

We had not used a different solution before Moveworks; it was our first one, although we considered others.

Moveworks was the only platform we were searching for, primarily because of its integration with ServiceNow.