My main use case for Nexthink that we are currently working on is battery replacement and MS Office continuity.

For battery replacement with Nexthink, we check the battery cycles and based on the data we receive from remote action, we target those end users and they decide whether they have to replace the device or not.

For MS Office continuity, Nexthink helps us by having multiple applications associated with MS Office, and I will provide the example of OneDrive. In OneDrive, first of all, it checks the sync to determine whether the sync is working or not. If not, it initiates a restart. If that does not work, then we proceed with a reinstall and then sync again. If it is repaired, then it is resolved. If not, then a ticket is logged.

Nexthink has positively impacted my organization by reducing handle times, reducing ticket volumes, improving employee experience of software, workstation replacements, battery replacements, alerting users about password expiration, any upcoming changes, project changes, targeted campaigns, and more. There are multiple use cases that have benefited from this solution.

Regarding specific numbers, we have reduced around ten to fifteen percent of incoming volume via chats and calls overall, and apart from that, end users are able to help themselves using the chatbot, which accounts for around six percent.

The best features Nexthink offers, as of now, are Campaigns, Workflows which I find useful, and Remote Actions are also beneficial. Recently, we got hands-on with the virtualization module as well. I think all the modules are helpful, but it depends on the use case which we are working on.

Out of those features, I would say I find myself using Remote Actions the most or relying on it most heavily.

I think Nexthink should introduce longer character limits for remote session outputs and a better data repository to collect different files from end-user devices on a centralized storage. Apart from that, in workflow thinklets, there are some issues reported from time to time, so that needs to be addressed.

Customer support is one thing which needs to be improved; support team members are slow to respond, and they take a lot of time to get back to us, even if it is an urgent case. This is the thing which needs to be improved the most, and if the services are improved, then I would have probably given a ten.

I have been using Nexthink for around three and a half to four years.

Nexthink is stable. Everything is currently stable, and I have nothing to add on this matter.

Nexthink's scalability is sufficient; it is scalable enough for wider organizations. There are different towers that we can target with ample use cases in the library and custom ones.

Customer support is one thing which needs to be improved; support team members are slow to respond, and they take a lot of time to get back to us, even if it is an urgent case. This is the thing which needs to be improved the most, and if the services are improved, then I would have probably given a ten.

I have not used any other solution before Nexthink.

Before choosing Nexthink, I did not evaluate other options.

I have seen a return on investment with Nexthink. As I mentioned earlier, we have reduced volume, so that impacted the headcount and relates to money savings.

I have not used any other solution before Nexthink. Before choosing Nexthink, I did not evaluate other options.

To others looking into using Nexthink, I would suggest implementing Nexthink solution in the environment, assess where your environment is, and align use cases as per your requirements. Then you would definitely see an improvement if you are on the right track. My overall rating for this product is eight out of ten.

Main use cases have been campaigns and remote executions, either scheduled or manual, and Nexthink Query Language.

The best features Nexthink offers are the DEX scores and the ability to walk through an application that is on a browser.

The DEX scores help because they give an overview of how well an organization is doing across the industry compared to other organizations.

It helps to see what users are experiencing before they call the service desk.

In the past, when there have been issues that were global, it was easier to tell all users what the impact was and advise them not to call the service desk while we were working on the issue remotely.

The biggest limitation in features is the limited amount of metrics collected to use for Nexthink queries and investigations.

Nexthink can be improved by allowing collection of more metrics. For example, if there is the Print Spooler remote action, it would be helpful if the metric for the print queue was available when doing an NQL query to decide whether or not to run a remote action on a regular basis. Some of the metrics being collected are good, but they seem limited and are not as useful when running queries to decide whether or not to run a remote action.

There is a lot of improvement that can be made on the documentation side, the licensing side, and some of the backend side, including collection of metrics, ease of use to set up workflows, and more documentation on how to build custom remote actions.

I have been using Nexthink for around three and a half years.

There are no stability issues.

There are no scalability issues.

There are no customer service issues.

When Nexthink is implemented in a company, it should not be sold as just an IT tool. The people who support the applications need to be involved more. The tool can be adopted quicker and brought more broadly if the support groups of the applications are involved when it is purchased.

One of the biggest pieces of advice would be to purchase all the licensing needed to get the full functionality of the product. I would rate this review as a nine.

My main use case for Nexthink is improving digital experience for end users.

A quick, specific example of how I use Nexthink to improve digital experience for users is that we have a dashboard in place, so we proactively check what are the areas we need to improve upon, be it performance factors, endpoint factors, such as slow login, high boot time, application crashes, system crashes, and any network events where we have noticed latency.

These are the main observations about my main use case. Our objective is to improve our digital experience score, which consists of various factors as I mentioned, such as performance, endpoint scoring, and collaboration tools. We want to make sure that our tools are working seamlessly with minimal user impact, so that is how we track them with the help of Nexthink.

Nexthink has impacted my organization positively by helping us to a great extent, improving the end user experience in terms of enhancing device performance, reducing system crashes, and improving device reliability. Overall it has been good.

There are a variety of features Nexthink offers, starting with the ability to send campaigns to users, enable alerts for any specific application crashes or any network issues, and leverage proactive incident generation by integrating with ServiceNow for alarming issues such as system crashes or devices with low disk space. Another feature is creating remote actions, some of which are manual and reduce the manual effort of our engineers to fix a problem, while others can be automated and scheduled to run on an hourly or weekly basis across all devices. These actions not only capture information but also remediate issues, so if they identify an issue, a remote action will trigger at a scheduled time to fix it, so that the end user does not need to contact us to fix those issues.

The feature I find most helpful day-to-day is the digital experience dashboard, which gives us clarity or a holistic picture of how our devices are operating in our environment and how we can further improve it.

There are features such as remote actions, campaigns, and alerts, which are pretty good to use. Lately, we got Nexthink Assist, which helps us investigate as a layman; you just need to write your query in Assist, and it generates the investigations for you, so it is an AI which is pretty useful.

I think Nexthink can be improved to bring deeper investigations; for example, Nexthink does not give us the exact solution, but it provides what it sees on the device during that time frame. If Nexthink also has the capability to provide us with solutions, such as suggesting to run a disk cleanup or look for a particular folder to remedy a problem, that would be really helpful. If Nexthink Assist can be empowered more to identify and remediate on its own, that would be useful.

Regarding improvements needed for Nexthink, I would like to leverage software licensing reporting, but it requires a lot of manual intervention to feed in all that data, such as determining what kind of license is a perpetual license or what enterprise license. In that context, some improvement is required.

The reason I chose an eight is because there are still areas to improve, and not many people are fully aware of the capabilities of Nexthink. With the recent introduction of Assist, it does give people the ability to use it more easily, but some enhancements can be made to make it more user-friendly.

I have been using Nexthink for four and a half years.

Nexthink is stable.

The tool's scalability works fine; we rarely see any outages with Nexthink, so it performs well and is pretty stable.

Customer support is okay; it is fine and I do not face many challenges with the support, as it is good.

I used ControlUp in my previous organization before using Nexthink.

I definitely see a return on investment with Nexthink as it helps in the reduction of incidents, thus saving manpower. We can also see the reliability in the devices, helping us identify which device will be end of life and which devices can continue to work, leading to potential savings for us.

My advice to others looking into using Nexthink would be that it is a go-to solution if you want a proactive analysis of your infrastructure to ensure the scalability and reliability of your infrastructure; you should choose Nexthink. I would rate this review an eight.

I have not developed a practical use case because my experience with Nexthink was limited to certification training. I worked with some features during my training, but it was planned education rather than practical application.

Nexthink is a complete package where you can dive deep into how applications and IT infrastructure are working. The visual presentation is better than other products I have explored, so I really appreciated using Nexthink.

When I reflect on my experience, I remember that it was more intuitive to work with Nexthink compared to other solutions.

I am unable to provide recommendations on how Nexthink can be improved because I did not engage in any actual practical work with the platform. My experience was limited to certification training.

I used Nexthink approximately two and a half years ago, though it has been about two years since I had any experience with the platform.

I am unable to assess whether Nexthink is stable based on my experience during certification or training.

I cannot recall information about Nexthink's scalability from what I learned during certification or training.

I do not recall how Nexthink's customer support operates based on my training or any experience I may have had interacting with them.

I have worked with several solutions including AppDynamics, though this experience was also limited to certification training.

I did not receive any insights into pricing, setup cost, and licensing during my certification or training.

I did not have an implementation team involved in my experience with Nexthink.

I have not seen a return on investment from Nexthink, as I cannot share any relevant metrics from my training or certification experience.

I did not receive any insights into pricing, setup cost, and licensing during my certification or training.

Nexthink was the only platform evaluated as part of my training, with no other options considered.